Result for 01076FB03E8CC9D4B00B43023BEE38F008A5CC04

Query result

Key Value
FileName./usr/share/doc/python-stestr-doc/html/api/commands/__init__.html
FileSize4570
MD5F3BE83C4F8390994C750E7542F6CD1D8
SHA-101076FB03E8CC9D4B00B43023BEE38F008A5CC04
SHA-256E3A0B8EB5B987EC21C4CD8161A3FFFB03BB7722BBA74468957D5EFAD1FFD7B1D
SSDEEP96:7k+DDmQ9eQsD9YFnFtsYTDX/LQursDVLnJtsYOQ:7froQnF13PLvr+nJ15
TLSHT1B391F0130CF0AD67401382EAA5E4AB157E82C257E2092D08B4FC5A6D4F83F45996BB4D
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
FileSize39340
MD510026E6E56A6DDE4EA17210C8F63D7B9
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
PackageVersion2.1.0-2~bpo9+1
SHA-13065B01EB660708BDA97E6C15FF67E79F49C8A6A
SHA-256330A99BBD4B023C7AB47BCB242CD2183564EFC4E6BAF122C681A6F914B336F11