Result for 42AD6B5493F1ADB014511147C770DBD518FD0281

Query result

Key Value
CRC324E22761E
FileName./usr/bin/python2-pbr
FileSize154
MD52FE2F744B62526C3B116079AD1782B34
OpSystemCode{'MfgCode': '1006', 'OpSystemCode': '362', 'OpSystemName': 'TBD', 'OpSystemVersion': 'none'}
ProductCode{'ApplicationType': 'Operating System', 'Language': 'English', 'MfgCode': '534', 'OpSystemCode': '599', 'ProductCode': '163573', 'ProductName': 'Netrunner', 'ProductVersion': '17.01'}
SHA-142AD6B5493F1ADB014511147C770DBD518FD0281
SHA-25634DFEE889C558D47FD579C2D3A61D22765A0FD5E0E50158CB83AE0957D215893
SSDEEP3:TKQWaHMne3cGn3525XK4YFMIKy3v3y8L42XBcefLhAjpAEnL4MG/vn:HWaHwe3ETYFJKyf3y8Lxx1FAjpAEkT/v
SpecialCode
TLSHT158C08C494886E6B01DF292CE3040D020A262390B9E00A62060A84B9B66E03801C6869E
dbnsrl_modern_rds
insert-timestamp1647003195.302595
sourceNSRL
hashlookup:parent-total8
hashlookup:trust90

Network graph view

Parents (Total: 8)

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

Key Value
FileSize64004
MD575D0795153177AB1548CF8AB47086EF5
PackageDescriptioninject 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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNamepython-pbr
PackageSectionpython
PackageVersion5.5.1-0ubuntu1
SHA-1E26C962FD063B279D4C2A1F0C006D9F379EADF53
SHA-25669DD35311ED3E2C6E9887943C45F97E5EBEEF871D0B56A1CB6897BED014FD258
Key Value
FileSize53688
MD5F6F58CED268ECE4AE3979D90640EF885
PackageDescriptioninject 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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNamepython-pbr
PackageSectionpython
PackageVersion3.1.1-3ubuntu3
SHA-162F74C71FAEB16DD8F846DD26D3E6C80B535D88D
SHA-256B27FF88A88D71FF21FEF0432E2461E538E15CCD67199A7FDB81624A6D884A832
Key Value
FileSize56364
MD591A76C945E1903C8465450E7C5AABE21
PackageDescriptioninject 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.
PackageMaintainerDebian OpenStack <team+openstack@tracker.debian.org>
PackageNamepython-pbr
PackageSectionpython
PackageVersion4.2.0-4~bpo9+2
SHA-112FE4BA3D1D8AFA64F3038AD8351FF8CF068114E
SHA-256EF745690710AB190703D9F1187560A3ED3767233039AC74DF1D8980E4A88FA4F
Key Value
FileSize56500
MD59A3C1005EB45B5FD11175E7D6666B00D
PackageDescriptioninject 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.
PackageMaintainerDebian OpenStack <team+openstack@tracker.debian.org>
PackageNamepython-pbr
PackageSectionpython
PackageVersion4.2.0-5
SHA-10508FF565018EEB9B694738FE0FA497347ECCB13
SHA-2569BF6886287758834D7C1A9AAC6BDF04D6CFCF73B8E6CA9D095ECB01CAEBDE275
Key Value
FileSize60992
MD578DC49E753051511915B929952A29F43
PackageDescriptioninject 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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNamepython-pbr
PackageSectionpython
PackageVersion5.1.1-0ubuntu2
SHA-18E01F300B6390478B35E7CC6DCF0E293A5140E0A
SHA-2566C77059319575276F3FDAF0D1B4889D79688B9AB5B08433F8D81030B331BA116
Key Value
FileSize52408
MD5EA799098227E2A993E0AF831B13ED926
PackageDescriptioninject 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.
PackageMaintainerPKG OpenStack <openstack-devel@lists.alioth.debian.org>
PackageNamepython-pbr
PackageSectionpython
PackageVersion1.10.0-1
SHA-1D1058E1C66F7CDB77C02D289497A0FE38DB254B7
SHA-25697E6974B68EB98F91FF0F920E7F27B047C3E6856BD5B014A57E8917D35FB1904
Key Value
FileSize63924
MD58635D626EF03661C601C9B1E00A29A52
PackageDescriptioninject 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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNamepython-pbr
PackageSectionpython
PackageVersion5.4.5-0ubuntu1
SHA-144C5547AD223A6BAE3CB6534E735364498DC4C2F
SHA-2568C5E97B7AFC1D90D1CDF7A5C1964677603B548A2E8265367523B32DB60F87E75
Key Value
FileSize61820
MD5AE2727835058BD94B3ECD382ADBFAED4
PackageDescriptioninject 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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNamepython-pbr
PackageSectionpython
PackageVersion4.2.0-0ubuntu3
SHA-11B398D8BA22E43C5C3215999D10D5C61F257CBE9
SHA-256C7ABC72D949043AD6BAB001465597E85F10D7DB4B427A244FD4FED78520B9671