Parents (Total: 4)

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

Key	Value
SHA-1	7DA0BF96A0EBB2D83C7B53A393A71C7D03CDCC17
snap-authority	canonical
snap-filename	Wt6mrVKN9c7FfPM1Ji7oS9SastvRys3Y_1.snap
snap-id	Wt6mrVKN9c7FfPM1Ji7oS9SastvRys3Y_1
snap-name	dosage-johnblood378
snap-publisher-id	l3584QTFRQiYoXZfTFzwYcvCQXMt2pPg
snap-signkey	BWDEoaqyr25nF5SNCvEv2v7QnM9QsfCc0PBMYD_i2NGSQ32EF2d4D0hqUel3m8ul
snap-timestamp	2018-12-07T03:33:58.588030Z
source-url	https://api.snapcraft.io/api/v1/snaps/download/Wt6mrVKN9c7FfPM1Ji7oS9SastvRys3Y_1.snap

Key	Value
FileSize	60992
MD5	78DC49E753051511915B929952A29F43
PackageDescription	inject useful and sensible default behaviors into setuptools - Python 2.x 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 support for Python 2.x.
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	python-pbr
PackageSection	python
PackageVersion	5.1.1-0ubuntu2
SHA-1	8E01F300B6390478B35E7CC6DCF0E293A5140E0A
SHA-256	6C77059319575276F3FDAF0D1B4889D79688B9AB5B08433F8D81030B331BA116

Key	Value
FileSize	61056
MD5	2FEB6125156EF765B24D99BDAF9EEEB8
PackageDescription	inject useful and sensible default behaviors into setuptools - Python 3.x 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 support for Python 3.x.
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	python3-pbr
PackageSection	python
PackageVersion	5.1.1-0ubuntu2
SHA-1	685459446226DF5D001F0914ACE643E8D729C7DD
SHA-256	3CBE997C0AA67382D14E15CF5417AA7A95029296DE6A5A9B74B49338461C22EC

Key	Value
FileSize	61148
MD5	58AE7B742C2B1E7B4E05CC38DAB81B2D
PackageDescription	inject useful and sensible default behaviors into setuptools - Python 3.x 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 support for Python 3.x.
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	python3-pbr
PackageSection	python
PackageVersion	5.1.1-0ubuntu3
SHA-1	F2E9719291558C3FB242650B173A86A618D1F6E3
SHA-256	284654005D2CD9DAD6ABD47E8DC8A59D400E0B93E3C5AFDCDD7E26F1AB24B406