Key | Value |
---|---|
FileName | ./usr/lib/python3.6/site-packages/releases/__pycache__/models.cpython-36.opt-1.pyc |
FileSize | 6080 |
MD5 | 3C3D977205CD7B3162134DC65A3F4257 |
SHA-1 | 07A4F205E3273F08A2D4A52BAC3DCFE2260F37E7 |
SHA-256 | A5F707E3F8AF10BAE2D646EC5EED2430F988CBDDBA0543A03DD628193292C8E8 |
SSDEEP | 96:bzHJBG4f1vJXCoQXTDTu48S1vroyMPy9/V7Rr1bU1Lyi2RRCrNQsg2Kbn4PzhjQI:vH+IxkTu8oDa/NbU32RRCxpg2CnWdUF4 |
TLSH | T13DC161C86A855EEDFE70F2BA96D22341AB25857F4B48B35A361D506B3F072C46C3258C |
hashlookup:parent-total | 7 |
hashlookup:trust | 85 |
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 |
---|---|
MD5 | A35E5C1EF417E73F101575F5D56A9009 |
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 | python3-releases |
PackageRelease | 1.4 |
PackageVersion | 1.6.1 |
SHA-1 | 6358829954065B8489702EA69C315C1FB3BFC9AE |
SHA-256 | 04DF6EE600BCE049C0E8D8502AC84EBFA2C98684B9F6A8E8237CCF707C14BF21 |
Key | Value |
---|---|
MD5 | 823EB69034040182C3C1B71759131881 |
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 | python3-releases |
PackageRelease | lp152.1.1 |
PackageVersion | 1.6.1 |
SHA-1 | FCC3B8749609A3F1B27CF7C2D085D2BEDEF45D70 |
SHA-256 | 7F019CDB0256B946EF290BBC6AF3191A7FC6E6B39C10B24A44C2BA1ECE76CBA0 |
Key | Value |
---|---|
MD5 | D623156AF013D9D855BE64E210D6D91B |
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 | python3-releases |
PackageRelease | lp150.4.2 |
PackageVersion | 1.6.1 |
SHA-1 | B09CEBEDF77421EEBCA7E0B77C597BB4A3284F3D |
SHA-256 | D88FAC1D1631DF0FAB1420EA9B8CB0A6A351541057B0D31111B359E27E516391 |
Key | Value |
---|---|
MD5 | 4B6BE5E3BF18DA79497E3CDC640F2B45 |
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 | python3-releases |
PackageRelease | bp154.1.30 |
PackageVersion | 1.6.1 |
SHA-1 | EFA2C0A01C3BA6EC5A4BF7F243AE28A53B3A0BE1 |
SHA-256 | 82A8BC19AD72BCA14DA760410E72418D681A5BF3790768DEE9C9D098F8A82299 |
Key | Value |
---|---|
MD5 | 8C55013E5E613AF4B25E96EA9718D5A4 |
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 | python3-releases |
PackageRelease | lp152.1.1 |
PackageVersion | 1.6.1 |
SHA-1 | C88823002BE03B406F08985E1B140CFCDD5249B6 |
SHA-256 | 459A0BB581CC518A15BB943B3318016E71E6B8EE0DA45AFC8C41283194F4EE4A |
Key | Value |
---|---|
MD5 | 21F6036D2A491585C01C9915476DDFB4 |
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 | python3-releases |
PackageRelease | bp155.2.11 |
PackageVersion | 1.6.1 |
SHA-1 | 264EBF73480B4DED9D3F02138F4D1441968D2ABD |
SHA-256 | 9B54CA88944AB5D31EFEF4379A2F16D327FC0B54CFA55DEA66EAD2389CFA89ED |
Key | Value |
---|---|
MD5 | FFDA308A7FA454A239FF892FAC75BB28 |
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 | python3-releases |
PackageRelease | bp153.1.15 |
PackageVersion | 1.6.1 |
SHA-1 | CB7ABA88B840B39172AAF31FBBB86A1F70323C2A |
SHA-256 | B6BC0021BAE05EFCEA3BC764E589A5D19A1CC91A42B5820E52B428ED82A513F2 |