Parents (Total: 3)

The searched file hash is included in 3 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
FileSize	47722
MD5	B2A3C4E3D8CA093C5FDDCA9577A4B6F4
PackageDescription	inject useful and sensible default behaviors into setuptools - doc PBR (Python Build Reasonableness) is a library that injects some useful and sensible default behaviors into your setuptools run. PBR can: * Manage version number based on git revisions and tags (Version file). * Generate AUTHORS file from git log * Generate ChangeLog from git log * Generate Sphinx autodoc stub files for your whole module * Store your dependencies in a pip requirements file * Use your README file as a long_description * Smartly find packages under your root package . PBR is only mildly configurable. The basic idea is that there's a decent way to run things and if you do, you should reap the rewards, because then it's simple and repeatable. If you want to do things differently, cool! But you've already got the power of Python at your fingertips, so you don't really need PBR. . PBR builds on top of `d2to1` to provide for declarative configuration. It then filters the `setup.cfg` data through a setup hook to fill in default values and provide more sensible behaviors. . This package provides the documentation.
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	python-pbr-doc
PackageSection	doc
PackageVersion	1.10.0-0ubuntu6
SHA-1	72FD840F3862B063A5CD917BE49B5A9A5B073B9E
SHA-256	4939A87CAA975217258CB892DDAAB73381AC2C248F035DA64B5B894177A19C7B

Key	Value
FileSize	50122
MD5	B09451FCEB57AD64906895822FC18E7D
PackageDescription	inject useful and sensible default behaviors into setuptools - doc PBR (Python Build Reasonableness) is a library that injects some useful and sensible default behaviors into your setuptools run. PBR can: * Manage version number based on git revisions and tags (Version file). * Generate AUTHORS file from git log * Generate ChangeLog from git log * Generate Sphinx autodoc stub files for your whole module * Store your dependencies in a pip requirements file * Use your README file as a long_description * Smartly find packages under your root package . PBR is only mildly configurable. The basic idea is that there's a decent way to run things and if you do, you should reap the rewards, because then it's simple and repeatable. If you want to do things differently, cool! But you've already got the power of Python at your fingertips, so you don't really need PBR. . PBR builds on top of `d2to1` to provide for declarative configuration. It then filters the `setup.cfg` data through a setup hook to fill in default values and provide more sensible behaviors. . This package provides the documentation.
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	python-pbr-doc
PackageSection	doc
PackageVersion	1.10.0-0ubuntu3
SHA-1	145F9D246ADA24B7862B540AE149B767DB9EBB28
SHA-256	8496636CF5BE62F5748946F65748BEE27DFE3E5F1952B363F255C0A392732A02

Key	Value
FileSize	51176
MD5	9E33749AEBE0FA3461EEE73197364F6C
PackageDescription	inject useful and sensible default behaviors into setuptools - doc PBR (Python Build Reasonableness) is a library that injects some useful and sensible default behaviors into your setuptools run. PBR can: * Manage version number based on git revisions and tags (Version file). * Generate AUTHORS file from git log * Generate ChangeLog from git log * Generate Sphinx autodoc stub files for your whole module * Store your dependencies in a pip requirements file * Use your README file as a long_description * Smartly find packages under your root package . PBR is only mildly configurable. The basic idea is that there's a decent way to run things and if you do, you should reap the rewards, because then it's simple and repeatable. If you want to do things differently, cool! But you've already got the power of Python at your fingertips, so you don't really need PBR. . PBR builds on top of the work that d2to1 started to provide for declarative configuration. d2to1 is itself an implementation of the ideas behind distutils2. Although distutils2 is now abandoned in favor of work towards PEP 426 and Metadata 2.0, declarative config is still a great idea and specifically important in trying to distribute setup code as a library when that library itself will alter how the setup is processed. As Metadata 2.0 and other modern Python packaging PEPs come out, PBR aims to support them as quickly as possible. . This package provides the documentation.
PackageMaintainer	PKG OpenStack <openstack-devel@lists.alioth.debian.org>
PackageName	python-pbr-doc
PackageSection	doc
PackageVersion	1.10.0-1
SHA-1	E8C0880976300B6E879D94CE118C603D253DFF30
SHA-256	13B29525E5A586F6260532C29F6701EC74615340C6D99728CF1B1D3314C0D862