Result for 0A34198D0E4F375CF8262C1BFB13A0FF34E9AEB3

Query result

Key Value
FileName./usr/lib/python2.7/site-packages/dogpile.cache-0.6.8-py2.7.egg-info/PKG-INFO
FileSize4441
MD5A5196AF5AD62C1A42798A8619FFDEC1C
SHA-10A34198D0E4F375CF8262C1BFB13A0FF34E9AEB3
SHA-25637BE91D69B0DE28AE3EB2BF8D16CD11921B94706300238E34B0E18272226FD01
SSDEEP96:Dsjhm03KBZ+UWitkaz+Xzz4h9QZIjM62VQOfbYqO4JTLiBe:l0KB4U9Oaz+jzc7M6LOjzTLD
TLSHT18691732FFB0526710B934A656E6641A2DA3D402F77159085B08E81BC2F5AE3583BFDFC
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
MD5293F0CD8E272B26398D7640A2660B842
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.
PackageMaintainerCBS <cbs@centos.org>
PackageNamepython2-dogpile-cache
PackageRelease1.el7
PackageVersion0.6.8
SHA-1C296078D8FF44079367AF4981E80B0212FA5044D
SHA-2568D682050772191D00E3C7F31F413B093C65D2DC06835485A2223AFBBAE2A3888
Key Value
MD559D4D6749F6418C0AEF3C883C2B5C484
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.
PackageMaintainerCBS <cbs@centos.org>
PackageNamepython2-dogpile-cache
PackageRelease1.el7
PackageVersion0.6.8
SHA-1863F584A306DEA105B8FC12AFD74F71E9C1AE831
SHA-2569D82D46AAA1782DFB94595AD2F9351F5FB1FD5DA7BFC758412B4D2F2AFCFA4D8