Result for 0B5BBD7BF3F4F405B59D0EFF2A09260FC6B6A4F5

Query result

Key Value
FileName./usr/lib/python2.7/site-packages/dogpile/util/langhelpers.pyo
FileSize5196
MD54271B6660AE69531DDC4F373FC1DE855
SHA-10B5BBD7BF3F4F405B59D0EFF2A09260FC6B6A4F5
SHA-256E61752DEFA5448BB031ABFE80DF6F683D2C0CB9BF1B28CE2B5FEAF2D2E3B9A41
SSDEEP96:DhX8dxiItNTrTO1gjmf/T+Tn8oTYpNzfibJmjXoLOtIKtQ:lsdYIbT/egnTn8yYpNmbojcqIL
TLSHT1ACB1DF90F3F80867D6A554B195B0012F96B5F1B752067B5223ACD83B28F839EC97BBC1
hashlookup:parent-total2
hashlookup:trust60

Network graph view

Parents (Total: 2)

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

Key Value
MD560E7E993DD90F33D7103E6B7EF2E8294
PackageArchnoarch
PackageDescriptionDogpile consists of two subsystems, one building on top of the other. dogpile provides the concept of a "dogpile lock", a control structure which allows a single thread of execution to be selected as the "creator" of some resource, while allowing other threads of execution to refer to the previous version of this resource as the creation proceeds; if there is no previous version, then those threads block until the object is available. dogpile.cache is a caching API which provides a generic interface to caching backends of any variety, and additionally provides API hooks which integrate these cache backends with the locking mechanism of dogpile. Overall, dogpile.cache is intended as a replacement to the Beaker 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.
PackageMaintainerpterjan <pterjan>
PackageNamepython2-dogpile-cache
PackageRelease1.mga7
PackageVersion0.6.8
SHA-11ECBA2CB82059A2DC27F9CE9EDC77C5F98889E8D
SHA-256796F729DD28FBC2DF7A020B9368835594661989959E8C561F61BB2AF9282A4B8
Key Value
MD5DDB083C4B36120D71576F16C6F76F55E
PackageArchnoarch
PackageDescriptionDogpile consists of two subsystems, one building on top of the other. dogpile provides the concept of a "dogpile lock", a control structure which allows a single thread of execution to be selected as the "creator" of some resource, while allowing other threads of execution to refer to the previous version of this resource as the creation proceeds; if there is no previous version, then those threads block until the object is available. dogpile.cache is a caching API which provides a generic interface to caching backends of any variety, and additionally provides API hooks which integrate these cache backends with the locking mechanism of dogpile. Overall, dogpile.cache is intended as a replacement to the Beaker 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.
PackageMaintainerFedora Project
PackageNamepython2-dogpile-cache
PackageRelease1.el8.1
PackageVersion0.6.8
SHA-10F7652B9674CF2F2C593B40DAD17D7FB7C0623CB
SHA-2565043A90EBE9CB7DFEDC7D354DC347A2845081C6BC9A81DD9ECAAB673CCAB9904