Parents (Total: 6)

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

Key	Value
MD5	2DF9969AEE6AFD5F98F2738CB32F99EF
PackageArch	noarch
PackageDescription	Releases is a Python 2+3 compatible `Sphinx <http://sphinx-doc.org>`_ extension designed to help you keep a source control friendly, merge friendly changelog file & turn it into useful, human readable HTML output. Specifically: * The source format (kept in your Sphinx tree as ``changelog.rst``) is a stream-like timeline that plays well with source control & only requires one entry per change (even for changes that exist in multiple release lines). * The output (when you have the extension installed and run your Sphinx build command) is a traditional looking changelog page with a section for every release; multi-release issues are copied automatically into each release. * By default, feature and support issues are only displayed under feature releases, and bugs are only displayed under bugfix releases. This can be overridden on a per-issue basis.
PackageMaintainer	https://bugs.opensuse.org
PackageName	python38-releases
PackageRelease	3.3
PackageVersion	1.6.3
SHA-1	36298C03749E063D17CCA693C462CAEE53083C20
SHA-256	281A5433001D5C9952F598542FC778FD4FCF837C3564F8A715B84A2A78470212

Key	Value
MD5	8C3306DD6C2ABA4F679D624C7C1CF09B
PackageArch	noarch
PackageDescription	Releases is a Python 2+3 compatible `Sphinx <http://sphinx-doc.org>`_ extension designed to help you keep a source control friendly, merge friendly changelog file & turn it into useful, human readable HTML output. Specifically: * The source format (kept in your Sphinx tree as ``changelog.rst``) is a stream-like timeline that plays well with source control & only requires one entry per change (even for changes that exist in multiple release lines). * The output (when you have the extension installed and run your Sphinx build command) is a traditional looking changelog page with a section for every release; multi-release issues are copied automatically into each release. * By default, feature and support issues are only displayed under feature releases, and bugs are only displayed under bugfix releases. This can be overridden on a per-issue basis.
PackageName	python38-releases
PackageRelease	20.4
PackageVersion	1.6.3
SHA-1	DA808773E30C71EC59B3438B207F2ED511BD6D14
SHA-256	D5715A71F6839FA484948806FEC5E399B7C5806D8531620B8EE938D6588C807A

Key	Value
MD5	A0B1CC5A6A881885AA181BA27F91A41F
PackageArch	noarch
PackageDescription	Releases is a Python 2+3 compatible `Sphinx <http://sphinx-doc.org>`_ extension designed to help you keep a source control friendly, merge friendly changelog file & turn it into useful, human readable HTML output. Specifically: * The source format (kept in your Sphinx tree as ``changelog.rst``) is a stream-like timeline that plays well with source control & only requires one entry per change (even for changes that exist in multiple release lines). * The output (when you have the extension installed and run your Sphinx build command) is a traditional looking changelog page with a section for every release; multi-release issues are copied automatically into each release. * By default, feature and support issues are only displayed under feature releases, and bugs are only displayed under bugfix releases. This can be overridden on a per-issue basis.
PackageName	python38-releases
PackageRelease	20.3
PackageVersion	1.6.3
SHA-1	42861455498FC0CE2DCCED73E1AEEB80E9620D9F
SHA-256	6E6844235F4752F43C8029E18ED3807357BD2CFA2F92B0BB2D094505D23DB580

Key	Value
MD5	5781C5B2651C3C498DF801449F76DAFD
PackageArch	noarch
PackageDescription	Releases is a Python 2+3 compatible `Sphinx <http://sphinx-doc.org>`_ extension designed to help you keep a source control friendly, merge friendly changelog file & turn it into useful, human readable HTML output. Specifically: * The source format (kept in your Sphinx tree as ``changelog.rst``) is a stream-like timeline that plays well with source control & only requires one entry per change (even for changes that exist in multiple release lines). * The output (when you have the extension installed and run your Sphinx build command) is a traditional looking changelog page with a section for every release; multi-release issues are copied automatically into each release. * By default, feature and support issues are only displayed under feature releases, and bugs are only displayed under bugfix releases. This can be overridden on a per-issue basis.
PackageName	python38-releases
PackageRelease	20.3
PackageVersion	1.6.3
SHA-1	0CC63D2570D64CB310F3FAE74229E2FB02194355
SHA-256	4E00FD5DEF5F723481EA520CAF109717ED635BC7FC01191FB7F898ACF05F223C

Key	Value
MD5	5BD11D744CDDD1829D589A5A0E3A6C48
PackageArch	noarch
PackageDescription	Releases is a Python 2+3 compatible `Sphinx <http://sphinx-doc.org>`_ extension designed to help you keep a source control friendly, merge friendly changelog file & turn it into useful, human readable HTML output. Specifically: * The source format (kept in your Sphinx tree as ``changelog.rst``) is a stream-like timeline that plays well with source control & only requires one entry per change (even for changes that exist in multiple release lines). * The output (when you have the extension installed and run your Sphinx build command) is a traditional looking changelog page with a section for every release; multi-release issues are copied automatically into each release. * By default, feature and support issues are only displayed under feature releases, and bugs are only displayed under bugfix releases. This can be overridden on a per-issue basis.
PackageName	python38-releases
PackageRelease	18.5
PackageVersion	1.6.3
SHA-1	9E97DCA1C1D47F5F677AF26D5BE4DF8EEFA21E2F
SHA-256	4EA4C788555625878D0C176501D0636404C99D8ED137D1FA737507C0DC0785E8

Key	Value
MD5	4A6688B31EB320D18E7A7816863FE1B8
PackageArch	noarch
PackageDescription	Releases is a Python 2+3 compatible `Sphinx <http://sphinx-doc.org>`_ extension designed to help you keep a source control friendly, merge friendly changelog file & turn it into useful, human readable HTML output. Specifically: * The source format (kept in your Sphinx tree as ``changelog.rst``) is a stream-like timeline that plays well with source control & only requires one entry per change (even for changes that exist in multiple release lines). * The output (when you have the extension installed and run your Sphinx build command) is a traditional looking changelog page with a section for every release; multi-release issues are copied automatically into each release. * By default, feature and support issues are only displayed under feature releases, and bugs are only displayed under bugfix releases. This can be overridden on a per-issue basis.
PackageName	python38-releases
PackageRelease	18.6
PackageVersion	1.6.3
SHA-1	4192716E591379726168D0541937C0ACCE0DDD20
SHA-256	C048647821978E046CFF9DCB65C2B68CA7E5166F03538DE3D42E74C44B48DF06