Result for 02E0BA21D8F4D151ADDFDFD2268D508FCDF814D9

Query result

Key Value
FileName./usr/share/doc/python-stestr-doc/html/developer_guidelines.html
FileSize5987
MD5CB26CEA32298F302700A565BB14D6801
SHA-102E0BA21D8F4D151ADDFDFD2268D508FCDF814D9
SHA-25685FC4D3538952DDCD360F6B9075339D43CC329BE75312AA39729C182D09D2A70
SSDEEP96:ykWIDmS9SQ2D9CVn3zsYeYpjZ9Ac1AjvLe4r2Dv7nTzsYA:yQ3+In3DeYpjZKZ7LXrMnTDA
TLSHT18AC1442258F29D37C55342E9E6E16B2AB996C11BC3051804F9FC47AD1FC2E849A3B74F
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
FileSize39116
MD5373F2737A15D4F9964261CB72F4F9001
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
SHA-13BA0500A044674F1F046B0901A0407A12A86711B
SHA-25608B0AD3529C620140C8E621021047CF820B121A632AE300EDA38D329D9BB66CF