Result for 326433EC5A8956C9F9207090D8C4D14177A374A0

Query result

Key Value
FileName./usr/share/doc/python36-pbr-4.2.0/html/_sources/user/packagers.txt
FileSize3937
MD5CC6DA614D453548CD82BC866E74871E7
SHA-1326433EC5A8956C9F9207090D8C4D14177A374A0
SHA-2561423B97CD3BC20D466C661C847505F4BBDD3C2AB65E5DF105F2BBF940154D401
SSDEEP96:AZr+bc7oVsMaXW1Ca/65XWRKuvuM33sI38Y8XxN:Ur+QosMauCa/cXmWM33sI3f8Xb
TLSHT12A81A67FBE045B370A80D378B51C50D0EF29A17C2371E5FA9C668219A643B9A07BF8D5
hashlookup:parent-total7
hashlookup:trust85

Network graph view

Parents (Total: 7)

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

Key Value
MD5B3ADB8F1144DD51F757CC06A28E591F7
PackageArchnoarch
PackageDescriptionManage dynamic plugins for Python applications
PackageMaintainerFedora Project
PackageNamepython34-pbr
PackageRelease1.el6_10
PackageVersion4.2.0
SHA-100EB3BC97AC800E051F198F7850DC449C1148291
SHA-25638BAA1E3BAF31D2C2DBA9CD364947F7A8023BA6A0A13EDF962FDECC5D455133A
Key Value
MD5FC98D5ACF623A6633EDBAF72787E1ADC
PackageArchnoarch
PackageDescriptionManage dynamic plugins for Python applications
PackageMaintainerFedora Project
PackageNamepython34-pbr
PackageRelease3.el7
PackageVersion4.2.0
SHA-147DE205BC0BF51438F647B9826BCB19657302F15
SHA-2564A57C71D49AEDBFF807308D72907675CA2F85FFF5B8DD2865902BA01F9DEFB4D
Key Value
MD501BAF3D19C5A7CDA0BEF9C73F67D3CDE
PackageArchnoarch
PackageDescriptionManage dynamic plugins for Python applications
PackageMaintainerFedora Project
PackageNamepython2-pbr
PackageRelease3.el7
PackageVersion4.2.0
SHA-1AE152C06C17025C648C251C41E0DD6A1090A9895
SHA-25696CAEE8F3430648B50FF30613D7BC9EA27C5F06C3D4B17EF6E7E8FA4E7BEFC7A
Key Value
MD58356A9B7BB06B8635118B1D606A2EAA3
PackageArchnoarch
PackageDescriptionManage dynamic plugins for Python applications
PackageMaintainerFedora Project
PackageNamepython36-pbr
PackageRelease3.el7
PackageVersion4.2.0
SHA-1B2A9299DCDBA0300C2361AE3EF842FB844E992E3
SHA-256B9F77FBE0767271E30626744B7B206C02EEBDBF50110E052630A6E884B79323C
Key Value
FileSize945992
MD59AB9746A4DD0BE9FEEC4E97C365C5FED
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-4~bpo9+2
SHA-1D4701C03B01819D05536E5509972C75B7B6B6EA1
SHA-256C51DB770664013CDCC494956379A30DEE22629EBFD8F5014921043A1EB8E71DD
Key Value
FileSize62128
MD5D33BD71282A2F5BC39B286B901A1E454
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
PackageVersion4.2.0-0ubuntu3
SHA-11265004068EC218251F523C649DA5FB1C3ABFE07
SHA-256DA9416F63BF55705A669608DC745C43C3309A43E93F23C083801736B74CA3D43
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