Parents (Total: 29)

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

Key	Value
MD5	B3ADB8F1144DD51F757CC06A28E591F7
PackageArch	noarch
PackageDescription	Manage dynamic plugins for Python applications
PackageMaintainer	Fedora Project
PackageName	python34-pbr
PackageRelease	1.el6_10
PackageVersion	4.2.0
SHA-1	00EB3BC97AC800E051F198F7850DC449C1148291
SHA-256	38BAA1E3BAF31D2C2DBA9CD364947F7A8023BA6A0A13EDF962FDECC5D455133A

Key	Value
FileSize	56500
MD5	9A3C1005EB45B5FD11175E7D6666B00D
PackageDescription	inject useful and sensible default behaviors into setuptools - Python 2.x 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 support for Python 2.x.
PackageMaintainer	Debian OpenStack <team+openstack@tracker.debian.org>
PackageName	python-pbr
PackageSection	python
PackageVersion	4.2.0-5
SHA-1	0508FF565018EEB9B694738FE0FA497347ECCB13
SHA-256	9BF6886287758834D7C1A9AAC6BDF04D6CFCF73B8E6CA9D095ECB01CAEBDE275

Key	Value
FileSize	56364
MD5	91A76C945E1903C8465450E7C5AABE21
PackageDescription	inject useful and sensible default behaviors into setuptools - Python 2.x 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 support for Python 2.x.
PackageMaintainer	Debian OpenStack <team+openstack@tracker.debian.org>
PackageName	python-pbr
PackageSection	python
PackageVersion	4.2.0-4~bpo9+2
SHA-1	12FE4BA3D1D8AFA64F3038AD8351FF8CF068114E
SHA-256	EF745690710AB190703D9F1187560A3ED3767233039AC74DF1D8980E4A88FA4F

Key	Value
MD5	72DBF8799D1A3DE36500E0C1B2E157C6
PackageArch	noarch
PackageDescription	Manage dynamic plugins for Python applications
PackageName	python3-pbr
PackageRelease	3.37
PackageVersion	4.2.0
SHA-1	1A6400873E53C871B1F8DF0CB22BE083597510CE
SHA-256	60F5CC9F8DA673F3A1B45A261D271D655A1AAB793F9ACE96C2B2B5E928D5C394

Key	Value
FileSize	61820
MD5	AE2727835058BD94B3ECD382ADBFAED4
PackageDescription	inject useful and sensible default behaviors into setuptools - Python 2.x 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 support for Python 2.x.
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	python-pbr
PackageSection	python
PackageVersion	4.2.0-0ubuntu3
SHA-1	1B398D8BA22E43C5C3215999D10D5C61F257CBE9
SHA-256	C7ABC72D949043AD6BAB001465597E85F10D7DB4B427A244FD4FED78520B9671

Key	Value
MD5	C7E66EE637FD4B12B41013F7F10BC5D0
PackageArch	noarch
PackageDescription	Manage dynamic plugins for Python applications
PackageName	python3-pbr
PackageRelease	3.11
PackageVersion	4.2.0
SHA-1	429427BB7C58D1E9F66D5152FE2F509B272AEAD3
SHA-256	3C3177FEE85A565105FDD63F88C62ADC3663AAB311463821D8F19571CC71EDE8

Key	Value
MD5	FC98D5ACF623A6633EDBAF72787E1ADC
PackageArch	noarch
PackageDescription	Manage dynamic plugins for Python applications
PackageMaintainer	Fedora Project
PackageName	python34-pbr
PackageRelease	3.el7
PackageVersion	4.2.0
SHA-1	47DE205BC0BF51438F647B9826BCB19657302F15
SHA-256	4A57C71D49AEDBFF807308D72907675CA2F85FFF5B8DD2865902BA01F9DEFB4D

Key	Value
FileSize	56410
MD5	372FEEACBB663D2C6B30D5844C4C6104
PackageDescription	inject useful and sensible default behaviors into setuptools - Python 3.x 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 support for Python 3.x.
PackageMaintainer	Debian OpenStack <team+openstack@tracker.debian.org>
PackageName	python3-pbr
PackageSection	python
PackageVersion	4.2.0-4~bpo9+2
SHA-1	5046F42C8C5A9F83F19CD5B97F853EF5FCC438A3
SHA-256	B758F716E7ABC822C77D08EC19C7F523E17EF444B8ED82A3EF679DF0183262B2

Key	Value
MD5	438455AA8146DB9F54E22723126D2538
PackageArch	noarch
PackageDescription	Manage dynamic plugins for Python applications
PackageName	python3-pbr
PackageRelease	3.1
PackageVersion	4.2.0
SHA-1	55BD4E38F60A5D02993A8E73431964FA0D26B67D
SHA-256	EDBF960DA37615A02C503E2FC966628A9D1588106CCEF45C97B7332758ED6F59

Key	Value
FileSize	56544
MD5	22D02A6C776BBB71DE6C311DC8D12BDD
PackageDescription	inject useful and sensible default behaviors into setuptools - Python 3.x 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 support for Python 3.x.
PackageMaintainer	Debian OpenStack <team+openstack@tracker.debian.org>
PackageName	python3-pbr
PackageSection	python
PackageVersion	4.2.0-5
SHA-1	5663C095DA5F0BEE333409310B50D28C16450C75
SHA-256	5B694D16C87DE29FCFFF2322CDB2CA52D71C09108150A585AF2A42CE2ECC6DA6