Result for 115778B890A57A27D8CDDF2F276E94FD27460455

Query result

Key Value
FileName./usr/share/doc/python-pbr-doc/html/testing.html
FileSize7594
MD5E1F846441ABF5A8FABE3BA7678C5572E
SHA-1115778B890A57A27D8CDDF2F276E94FD27460455
SHA-256094001B798B8E5371068E8496FC733EBC5023265EBA018E72DD276E3C7540263
SSDEEP192:x3ocvFTHbEqhQ2uKuy/IuqHdFl6+lnLQ6:9dvlbE45rK3dFlRnLt
TLSHT12BF1626A64F28533117385D3EAEA9B39B9E3C11FC2810804F1ED436C5F86E94762769F
hashlookup:parent-total2
hashlookup:trust60

Network graph view

Parents (Total: 2)

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

Key Value
FileSize51176
MD59E33749AEBE0FA3461EEE73197364F6C
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.
PackageMaintainerPKG OpenStack <openstack-devel@lists.alioth.debian.org>
PackageNamepython-pbr-doc
PackageSectiondoc
PackageVersion1.10.0-1
SHA-1E8C0880976300B6E879D94CE118C603D253DFF30
SHA-25613B29525E5A586F6260532C29F6701EC74615340C6D99728CF1B1D3314C0D862
Key Value
FileSize50122
MD5B09451FCEB57AD64906895822FC18E7D
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 `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.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNamepython-pbr-doc
PackageSectiondoc
PackageVersion1.10.0-0ubuntu3
SHA-1145F9D246ADA24B7862B540AE149B767DB9EBB28
SHA-2568496636CF5BE62F5748946F65748BEE27DFE3E5F1952B363F255C0A392732A02