Result for 41A85DE711A652240C938D11EB9F7F138EA994E1

Query result

Key Value
FileName./usr/share/doc/python-pbr-doc/html/search.html
FileSize4084
MD53B37D6A9B516829B4A273B63303F7E69
SHA-141A85DE711A652240C938D11EB9F7F138EA994E1
SHA-256E3B817392321200F0BE9C57E1E7260BE17DD8988E3E27A103EA71FCD083F3200
SSDEEP48:GmnpUkffnTx09Jk/hEZ/oR/Qb/85/uZ/18cqdc/olbF6JLLq0kW6Zv+djUrPq5xD:akffN09glvF+CnW6Za8C2D9WU6
TLSHT107814019ACE1D413A06299D6FDF2EA299DC3D14B83049C0471CC496D6FC2F984E4B78F
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