Result for 1E070E83F67469C4B1B5DD02BEAAB1EA61D4BA8B

Query result

Key Value
FileName./usr/share/doc/python-pbr-doc/html/_sources/reference/api/pbr.hooks.rst.txt
FileSize870
MD5A2B0A510DF7E5C8DBA831425F1740503
SHA-11E070E83F67469C4B1B5DD02BEAAB1EA61D4BA8B
SHA-25625C8ED4CCB3F326C6F9CD85D0AA4418579AF2145A3157F4DBF3E3B0BD7434F96
SSDEEP12:sa1UL+sEF8yC3FsL8yCpmJs+8yCMmtqsAS8yCM4JsHb8yCosU8yCv:iCuyCdyCpJyC1IyCM+yC/yCv
TLSHT1CF11ED1BDD353C03B97CCD32AA997DA5EFD2AB516810A37A140D099B09973182DDE6B0
hashlookup:parent-total9
hashlookup:trust95

Network graph view

Parents (Total: 9)

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

Key Value
FileSize962184
MD5F708ACDD0AAB664B0B56D9B5E6BC9748
PackageDescriptioninject 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.
PackageMaintainerDebian OpenStack <team+openstack@tracker.debian.org>
PackageNamepython-pbr-doc
PackageSectiondoc
PackageVersion5.5.0-2
SHA-18C79F171CE10770C083C959CBF1EA2AC6B62D615
SHA-2565C20DC720FA195C2F1082EBE8986B53A32489DDB426CF73E63523027C2FDFF47
Key Value
FileSize939736
MD5F99B5C638BA41BB73148C0238227B25E
PackageDescriptioninject 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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNamepython-pbr-doc
PackageSectiondoc
PackageVersion5.5.1-0ubuntu1
SHA-196BC9E5D0A83E98D612CA31A132909BB13C8D37D
SHA-256880C4D18A7CF2DAA2FCEFFBBAA288195F18C1D1641F82972A9D23634806D8466
Key Value
FileSize963024
MD51207D345B7E0A9807ED5FFAEB11538E5
PackageDescriptioninject 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.
PackageMaintainerDebian OpenStack <team+openstack@tracker.debian.org>
PackageNamepython-pbr-doc
PackageSectiondoc
PackageVersion5.6.0-2
SHA-1BBE2EB7BE26296954617BE730727C11E616D548E
SHA-256A46DDDBD2B49105760EB0185716229879F8E3FFD36CA91BBF1394EB68B8E6A4A
Key Value
MD5D713BFD91CB787B195F6E7D599EF4C3F
PackageArchnoarch
PackageDescriptionDocumentation for the PBR, a library that injects some useful and sensible default behaviors into your setuptools run.
PackageNamepython-pbr-doc
PackageRelease1.88
PackageVersion5.6.0
SHA-1A13EF3A5C9A1DF2C49940E5C3EA677AEFA916EA2
SHA-256B4F1A613B70919F79907C7EF7457FDD127A9EE8285E5A173FB7E27CC6D1C12E0
Key Value
MD5AFB82C131FC1AC72A9567FDBF6BB17E7
PackageArchnoarch
PackageDescriptionDocumentation for the PBR, a library that injects some useful and sensible default behaviors into your setuptools run.
PackageNamepython-pbr-doc
PackageReleaselp152.3.1
PackageVersion5.5.0
SHA-1BBA933F43C6BB00C253B41080354F15649DB3817
SHA-256764A937FB21D72CBA763A4C06AE281723C0704B07A98054A9875FC1614E9E7E7
Key Value
MD5AFB40BDC37205AAD12A6C6E54121C3E9
PackageArchnoarch
PackageDescriptionDocumentation for the PBR, a library that injects some useful and sensible default behaviors into your setuptools run.
PackageNamepython-pbr-doc
PackageReleaselp152.1.83
PackageVersion5.6.0
SHA-1B6A6CDC5E11149929DA8A8AB293FE3381CD4DA70
SHA-256F9662848F30180B674F089822DD561891EB6536C85C62D670539D18BD1CF5E63
Key Value
FileSize940540
MD58337D1BDCA98813E3E053993B11EDBA2
PackageDescriptioninject 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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNamepython-pbr-doc
PackageSectiondoc
PackageVersion5.6.0-0ubuntu1
SHA-1EB19851A04DDB25EA909911A6BF26583AEC2E3A5
SHA-25629CA7C488288C34584160CB100FA654CB55BE2268CA07E97E279569AAADCF65A
Key Value
MD55891C7843C40DB2C7D16DA3036F2D841
PackageArchnoarch
PackageDescriptionDocumentation for the PBR, a library that injects some useful and sensible default behaviors into your setuptools run.
PackageNamepython-pbr-doc
PackageRelease3.2
PackageVersion5.5.0
SHA-192AAE4F5C65721CD483E8B3D144C604DDADD5AB0
SHA-256AF9589104916F117D36C1B0CE06C048A042A952ED05C95E6E30BAF5693398431
Key Value
MD5B721DB0D61707CACFA361D5D12961B4C
PackageArchnoarch
PackageDescriptionManage dynamic plugins for Python applications
PackageMaintainerFedora Project
PackageNamepython3-pbr
PackageRelease2.fc34
PackageVersion5.5.1
SHA-1E3E69683D1276C0BEA134765D46B4A3D7FBC6EC5
SHA-25680B41EC09475310E83F8EA5679C2B3F6D51F95154FA2D6FE076480B9B6F64938