Result for 0C8011813B4FC36EE452D1C783D85E5593C777B0

Query result

Key Value
FileName./usr/share/doc/python-stestr-doc/html/_modules/stestr/config_file.html
FileSize27144
MD5E8C4A42138966260C123230BF1ACB112
SHA-10C8011813B4FC36EE452D1C783D85E5593C777B0
SHA-2568F33BD54D21A5E502337B5B59942659D61FF84A120D95A34ED06F34E628E00FC
SSDEEP192:ypoW1LHzXZcdrMMN+3QCdUsT96GAImzyKS3NqI74XSdKvoYqT0a/JC31N49NPClv:y3tHzX1UBMvT0a037PKf3vsgnC
TLSHT195C267D0E6FB9533017BC4C316AE0B6675F1456AE49A0500B3FD8BB80BECD547853DAA
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