Result for 1BAE9F53F011B85CCBBD3201A1C35B175C207733

Query result

Key Value
FileName./usr/share/doc/python-stestr-doc/html/objects.inv
FileSize2796
MD593FD8A028E1512720259718ABF0C5FF0
SHA-11BAE9F53F011B85CCBBD3201A1C35B175C207733
SHA-2569C3539E060896A4E95638EFCEAA14441ABD9951A290A33213B5C365ACAA0A17F
SSDEEP48:6QTfL16//cqaWIDTbmuf/E+wsCLD15Jg3LBbVKXcZNyFzgaOiitXbJhUpCPz:6c16//cqabDTa8/E1zzJWVVqcZNy1Oiq
TLSHT102515C91300CC16BC0679108EB193E81A3D7DBA31C4B54BC01AF06DB471594C8A7456F
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

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

Key Value
FileSize101188
MD57DF497AF7CFA8E1EBD8221A7206984EC
PackageDescriptiontest runner similar to testrepository - doc Stestr stands for Slim/Super Test Repository. It is a fork of the testrepository that concentrates on being a dedicated test runner for Python projects. The generic abstraction layers which enabled testr to work with any subunit emitting runner are gone. Stestr hard codes python-subunit-isms into how it works. The code base is also designed to try and be explicit, and to provide a Python API that is documented and has examples. . While stestr was originally forked from testrepository it is not 100% backwards compatible with testrepository. At a high level the basic concepts of operation are shared between the 2 projects but the actual usage between the 2 is not exactly the same. . This package contains the documentation.
PackageMaintainerDebian OpenStack <team+openstack@tracker.debian.org>
PackageNamepython-stestr-doc
PackageSectiondoc
PackageVersion3.1.0-2
SHA-1508FCBC9561B201A4E370A2B19722A99FE1F359C
SHA-2569FF6D6F6D675CA66A6B5D3A1043B269ADDE5A483C7056B2E65602ACB6EF71F1B