Parents (Total: 4)

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

Key	Value
MD5	293F0CD8E272B26398D7640A2660B842
PackageArch	noarch
PackageDescription	Dogpile 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.
PackageMaintainer	CBS <cbs@centos.org>
PackageName	python2-dogpile-cache
PackageRelease	1.el7
PackageVersion	0.6.8
SHA-1	C296078D8FF44079367AF4981E80B0212FA5044D
SHA-256	8D682050772191D00E3C7F31F413B093C65D2DC06835485A2223AFBBAE2A3888

Key	Value
MD5	60E7E993DD90F33D7103E6B7EF2E8294
PackageArch	noarch
PackageDescription	Dogpile 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.
PackageMaintainer	pterjan <pterjan>
PackageName	python2-dogpile-cache
PackageRelease	1.mga7
PackageVersion	0.6.8
SHA-1	1ECBA2CB82059A2DC27F9CE9EDC77C5F98889E8D
SHA-256	796F729DD28FBC2DF7A020B9368835594661989959E8C561F61BB2AF9282A4B8

Key	Value
MD5	DDB083C4B36120D71576F16C6F76F55E
PackageArch	noarch
PackageDescription	Dogpile 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.
PackageMaintainer	Fedora Project
PackageName	python2-dogpile-cache
PackageRelease	1.el8.1
PackageVersion	0.6.8
SHA-1	0F7652B9674CF2F2C593B40DAD17D7FB7C0623CB
SHA-256	5043A90EBE9CB7DFEDC7D354DC347A2845081C6BC9A81DD9ECAAB673CCAB9904

Key	Value
MD5	59D4D6749F6418C0AEF3C883C2B5C484
PackageArch	noarch
PackageDescription	Dogpile 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.
PackageMaintainer	CBS <cbs@centos.org>
PackageName	python2-dogpile-cache
PackageRelease	1.el7
PackageVersion	0.6.8
SHA-1	863F584A306DEA105B8FC12AFD74F71E9C1AE831
SHA-256	9D82D46AAA1782DFB94595AD2F9351F5FB1FD5DA7BFC758412B4D2F2AFCFA4D8