Result for 04021AF4E194F54F018989D8946AC3E0EE6E02EA

Query result

Key Value
FileName./usr/bin/python3-pbr
FileSize152
MD513A9EC278B0772917B50555281C14B0B
RDS:package_id293685
SHA-104021AF4E194F54F018989D8946AC3E0EE6E02EA
SHA-25685C020AAA991D4305DFC0514AE797AFF0E323CC956737135395E7DA15772480B
SSDEEP3:TFKL9neMS1nJ25XK4+NoFMIKy3v3y8L42XBcefLhAjpAEnL4MG/vn:J0telOT+iFJKyf3y8Lxx1FAjpAEkT/v
TLSHT1CEC08C45488AD2701DF192CE3040D420636229479E00A52021A84AAB76E02800C68A9D
insert-timestamp1678963846.9717073
sourceRDS.db
hashlookup:parent-total16
hashlookup:trust100

Network graph view

Parents (Total: 16)

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

Key Value
FileSize33440
MD5DDDA72E7695A045F9408E30AE6C07670
PackageDescriptioninject 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 `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 support for Python 3.x.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNamepython3-pbr
PackageSectionpython
PackageVersion1.8.0-4ubuntu1
SHA-101E0738937AEE7A234F24B17E3D9869F1C3146AE
SHA-256F04B68CCE9AFC56D69B3DC9D39B1F35EA33EFFA74BAF6B6C00CE110ECDACE824
Key Value
FileSize64608
MD52BDA297F87ED8FCBDCE3AF5C2AE840F6
PackageDescriptioninject 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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNamepython3-pbr
PackageSectionpython
PackageVersion5.6.0-0ubuntu1
SHA-110844941358B08FEC25132D0AE19908C8A641DB1
SHA-256434FCFC5115C91D216F2AEBCBFCB19849D75FF33A7F2576BD60C02DD93AE1213
Key Value
FileSize34994
MD591DFB31F18E17A0E408A58B8B6F60420
PackageDescriptioninject 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 `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 support for Python 3.x.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNamepython3-pbr
PackageSectionpython
PackageVersion1.10.0-0ubuntu3
SHA-11E1C61DEDA7FCF9214CA045C3B9FCA536664A2A8
SHA-256FA26A17DBA7F4B0AD54153209999AE43FD07F2E175848C6E8BD40540E241F557
Key Value
FileSize35096
MD5C963FDDD19889E534BEB149422699D12
PackageDescriptioninject 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 `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 support for Python 3.x.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNamepython3-pbr
PackageSectionpython
PackageVersion1.10.0-0ubuntu6
SHA-12C884B82091C4F9EFC8B1EC070C5AFA9EA553D12
SHA-256B3B9D8B26188C3CB2C5838634F26DC2A516C3A6D88782A9F77AA9F091553E6AD
Key Value
FileSize52504
MD569A217C7736ECB413484E3114E843C7B
PackageDescriptioninject 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.
PackageMaintainerPKG OpenStack <openstack-devel@lists.alioth.debian.org>
PackageNamepython3-pbr
PackageSectionpython
PackageVersion1.10.0-1
SHA-130062EE6D287AAA31D074D7B469D1BC35CB2A009
SHA-25674FF0459A9ABA845A7015F411EF7CA7150CD34F3A838423C96133D9F2E8A60A9
Key Value
FileSize56410
MD5372FEEACBB663D2C6B30D5844C4C6104
PackageDescriptioninject 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.
PackageMaintainerDebian OpenStack <team+openstack@tracker.debian.org>
PackageNamepython3-pbr
PackageSectionpython
PackageVersion4.2.0-4~bpo9+2
SHA-15046F42C8C5A9F83F19CD5B97F853EF5FCC438A3
SHA-256B758F716E7ABC822C77D08EC19C7F523E17EF444B8ED82A3EF679DF0183262B2
Key Value
FileSize56544
MD522D02A6C776BBB71DE6C311DC8D12BDD
PackageDescriptioninject 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.
PackageMaintainerDebian OpenStack <team+openstack@tracker.debian.org>
PackageNamepython3-pbr
PackageSectionpython
PackageVersion4.2.0-5
SHA-15663C095DA5F0BEE333409310B50D28C16450C75
SHA-2565B694D16C87DE29FCFFF2322CDB2CA52D71C09108150A585AF2A42CE2ECC6DA6
Key Value
FileSize61056
MD52FEB6125156EF765B24D99BDAF9EEEB8
PackageDescriptioninject 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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNamepython3-pbr
PackageSectionpython
PackageVersion5.1.1-0ubuntu2
SHA-1685459446226DF5D001F0914ACE643E8D729C7DD
SHA-2563CBE997C0AA67382D14E15CF5417AA7A95029296DE6A5A9B74B49338461C22EC
Key Value
FileSize61920
MD53392B39B04196945872916D40D77F1D4
PackageDescriptioninject 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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNamepython3-pbr
PackageSectionpython
PackageVersion4.2.0-0ubuntu3
SHA-17035192EC6E1C2229FFD6B8123F8345C306B1FCB
SHA-256B1C43354CA991F6F3BD35BB4AAE0E34FF77A060AFA6CC474CD1DB009D4BF51BF
Key Value
FileSize60364
MD5CC9808B3E8FF19B02344A241C48DA596
PackageDescriptioninject 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.
PackageMaintainerDebian OpenStack <team+openstack@tracker.debian.org>
PackageNamepython3-pbr
PackageSectionpython
PackageVersion5.5.0-2
SHA-17217F052D5DF40BEEFAB96B47714CF233EF82C61
SHA-25624801E512057D93A150661ACB651B9EDC1A8BCDEFDF69CF5B84884A7868D8276