Key | Value |
---|---|
FileName | ./usr/lib/python2.7/site-packages/releases/line_manager.pyo |
FileSize | 3064 |
MD5 | B5D9412ADDB9E9A554260C3C767A3CFE |
SHA-1 | 7663C8ECA74A43E8CA91CD1154E28D0906B9C03D |
SHA-256 | A2AFBDF221B23FE3B20984DA0ACD6817BEA40C425470AB78EC1C5C5C5A1BA38F |
SSDEEP | 48:hEx3KOIWwN1JlG1Jg9btARzPQqo1JDKa81JsuD3Gi81JyAoeK1JxoCqG1Jq91JCO:tOD6HifHiuD3ZgCw3 |
TLSH | T15D5112C0B3E9456FD6F96877E4B123267569D0F31343A7A1317CA83A1B8E1E5C13B580 |
hashlookup:parent-total | 2 |
hashlookup:trust | 60 |
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 |
---|---|
MD5 | F114F75EFF5930C7E2CBFCE1F22B7B92 |
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 | python2-releases |
PackageRelease | lp151.16.2 |
PackageVersion | 1.6.3 |
SHA-1 | 43F98A5997242287E884748737F00471AAA2CEF3 |
SHA-256 | FA98CD516BA28A1BD06894B12A1F24476BD06AE15B115E0C77E2262A66EDDC85 |
Key | Value |
---|---|
MD5 | 8E0990C768FCAB92CE075B41EADDF67C |
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 | python2-releases |
PackageRelease | lp150.4.2 |
PackageVersion | 1.6.1 |
SHA-1 | EEF19417DBD7C12242CEF4424545A659151AF125 |
SHA-256 | 7A035358E08BE74FA303FB6B5EA10EDE301382DE09CAE56AE3747038A7E90CC3 |