Result for 17834FA05FED20EDFD7109017DE4F91CDE373EDF

Query result

Key Value
FileName./usr/share/doc/python-pbr-doc/html/user/compatibility.html
FileSize17621
MD570D7A803D2F01670597C26F9B3734001
SHA-117834FA05FED20EDFD7109017DE4F91CDE373EDF
SHA-2569325B0C160A9739F69A990C6BA76FDDA9928134C9A31E08571E3A4F3738B1A65
SSDEEP192:D/BZBAyThs1P9wTyi00CzfeEqKc8bPDwSQ3+QO5xENMwC:yyTqNeT/0dz/bPDwS8+ND/
TLSHT1BF82B822ACD01437515386C9AEE16B39B9C7C25FC65A4C0275BC4A8D6FA1EA59E0F30F
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

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

Key Value
FileSize946556
MD5954AF11960526A4E7B45649577F34058
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
PackageVersion4.2.0-5
SHA-1F69D639D5C1563DB0BB8906F26121E1AB49F9A1F
SHA-256DC03C32E2243D48B15B967F96E964B420C083204D1DFF2130F203115B3445C74