Result for 2778D9029CDC61D2597D7E02446F9AAEE1B3C74D

Query result

Key Value
FileName./usr/share/doc/python-dogpile.cache-doc/html/objects.inv
FileSize1654
MD5AD34026267AE29E35F009EA42C46E15A
SHA-12778D9029CDC61D2597D7E02446F9AAEE1B3C74D
SHA-256B2BBAD1983B42795B40591F5EB01EE1C5FBA78C5AF59417F9B5ADFA6C1A05656
SSDEEP48:1mUP85vvEGEuTSqBXJG+SEYCSxQrsXCik5UQ:1J8psGE6BXBS4ICi2UQ
TLSHT17731F89A2581854B1116EF23222D706EC9D1C383AEB1072C7FF19879164A26818EEC9B
hashlookup:parent-total3
hashlookup:trust65

Network graph view

Parents (Total: 3)

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

Key Value
FileSize64172
MD5224A525F15BDC243C186A3AEFC00E67F
PackageDescriptioncaching front-end based on the Dogpile lock - doc A caching API built around the concept of a "dogpile lock", which allows continued access to an expiring data value while a single thread generates a new value. . dogpile.cache builds on the dogpile.core locking system (see http://pypi.python.org/pypi/dogpile.core), which implements the idea of "allow one creator to write while others read" in the abstract. Overall, dogpile.cache is intended as a replacement to the Beaker (see http://beaker.groovie.org) caching system, the internals of which are written by the same author. All the ideas of Beaker which "work" are re-implemented in dogpile.cache in a more efficient and succinct manner, and all the cruft (Beaker's internals were first written in 2005) relegated to the trash heap. . This package provides the documentation.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNamepython-dogpile.cache-doc
PackageSectiondoc
PackageVersion0.6.2-0ubuntu1
SHA-13069F1F016A424456E5548B740FDC748B106AB19
SHA-2561E5215375A87A48C74EBFD53B3E6659555B1405629231C7266915B8AFD97CB81
Key Value
FileSize62068
MD5332CEB04FB9C98F3F880B037B958621F
PackageDescriptioncaching front-end based on the Dogpile lock - doc A caching API built around the concept of a "dogpile lock", which allows continued access to an expiring data value while a single thread generates a new value. . dogpile.cache builds on the dogpile.core locking system (see http://pypi.python.org/pypi/dogpile.core), which implements the idea of "allow one creator to write while others read" in the abstract. Overall, dogpile.cache is intended as a replacement to the Beaker (see http://beaker.groovie.org) caching system, the internals of which are written by the same author. All the ideas of Beaker which "work" are re-implemented in dogpile.cache in a more efficient and succinct manner, and all the cruft (Beaker's internals were first written in 2005) relegated to the trash heap. . This package provides the documentation.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNamepython-dogpile.cache-doc
PackageSectiondoc
PackageVersion0.6.2-5
SHA-1AFA986C995EC7529EA1C56F58E1203BEA7757850
SHA-2562847AFB1D2EEA4302D15BB3563A3ECAE462A75DADCD5453218DC24C735C54A83
Key Value
FileSize82412
MD5E0F005E2753DA5B31EA81E8C377B0A86
PackageDescriptioncaching front-end based on the Dogpile lock - doc A caching API built around the concept of a "dogpile lock", which allows continued access to an expiring data value while a single thread generates a new value. . dogpile.cache builds on the dogpile.core locking system (see http://pypi.python.org/pypi/dogpile.core), which implements the idea of "allow one creator to write while others read" in the abstract. Overall, dogpile.cache is intended as a replacement to the Beaker (see http://beaker.groovie.org) caching system, the internals of which are written by the same author. All the ideas of Beaker which "work" are re-implemented in dogpile.cache in a more efficient and succinct manner, and all the cruft (Beaker's internals were first written in 2005) relegated to the trash heap. . This package provides the documentation.
PackageMaintainerPKG OpenStack <openstack-devel@lists.alioth.debian.org>
PackageNamepython-dogpile.cache-doc
PackageSectiondoc
PackageVersion0.6.2-5
SHA-112D4D2DD5ED762F60FDEB05C5D828A3F9749C3BB
SHA-256F27C33F9ECB47464A0B61C891A2489970B0B900804F78FF8D273ECC4664DCE6D