Parents (Total: 13)

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

Key	Value
MD5	B487B54C8D53B85971E09F50986200D8
PackageArch	noarch
PackageDescription	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.
PackageName	python3-dogpile.cache
PackageRelease	lp151.69.1
PackageVersion	1.1.1
SHA-1	C9512A807F2898129E05606FD14D47C03CAAB407
SHA-256	857FB8250E5DBAC9B3A8EDAED87009F73952137E0C62C16C87312F15D56A3300

Key	Value
MD5	E2F7D2966929B8383C2E1212D5B1793E
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	python3-dogpile-cache
PackageRelease	1.el8
PackageVersion	1.1.2
SHA-1	4BFE0866F715097B8DC02AD64ADE9ED499A83726
SHA-256	0F2E813599F2716E79DB11A9AA439EAB4755E9F63B9F107D1B4B5ACED786A4E2

Key	Value
MD5	33F26B92A81440B45A5B36FC27DD6300
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	python3-dogpile-cache
PackageRelease	1.1.el8
PackageVersion	1.1.2
SHA-1	524557EFF55EC40F0BDEE75C254CC00B84F607F6
SHA-256	99C77FEA83B5C6AA1170AD06C8517D7A2811D87CFF13C56971CEE1BF14DFEF61

Key	Value
FileSize	39600
MD5	02E81D2ECB866B81B90F14AEB2BBBB32
PackageDescription	caching front-end based on the Dogpile lock - Python 3.x 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 Python 3.x module.
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	python3-dogpile.cache
PackageSection	python
PackageVersion	1.1.2-1
SHA-1	10B392480D6899FB368B406D9BFFE91C796CEDE4
SHA-256	E383F88B56665311F94ECBE06B5E998E8FB3384998547B6A3A5EAF1A0C68A0C6

Key	Value
MD5	B74F6F096F2A93165C7E6FD2E24A1D44
PackageArch	noarch
PackageDescription	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.
PackageName	python3-dogpile.cache
PackageRelease	1.1
PackageVersion	1.1.3
SHA-1	7E7B705F52149AB3644AA6C4DDAA6B9D84E24DD4
SHA-256	17377DCFFE38651F08B4A9373C005AFCD5DC66E96DFE5E7A421915E8672EBDE9

Key	Value
MD5	16FA9A8A6C5D215ECD66DAFBD1D21423
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	python3-dogpile-cache
PackageRelease	1.fc34
PackageVersion	1.1.2
SHA-1	7585C31E97D5ACE9676F80991071111F38F8C7F6
SHA-256	C0016BADDE90A9FDB82AA07352BD9D4EE02E777F869694DD13A308375D281FE7

Key	Value
FileName	http://archlinux.mirror.root.lu//pool//community//python-dogpile.cache-1.1.2-1-any.pkg.tar.zst
MD5	E0E3158BA7FD9F34ADFC88A217A6A91B
SHA-1	8F81AA03639A614DEC623AF49A0465A155B5704C
SHA-256	165C9E962BC6ADEDEC614DD9EC74DC08C89572BF0903860E3BA8D16F818983B2
SSDEEP	1536:jQpSVg5e9e31tljruHKHSObllu9++S6Yd8uqpy65Dpniie8BnCUuyF7:jQYVg5emjrjyWlqe6TpyCdntBnCA
TLSH	T13373126077FAA2EC0815D5BA12C06D9C6767C64ACF155E364614F32B88B2C43AC16ECC

Key	Value
MD5	997CA105A0416E1920C9C14C80968DDE
PackageArch	noarch
PackageDescription	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.
PackageName	python3-dogpile.cache
PackageRelease	69.6
PackageVersion	1.1.1
SHA-1	AC2FA98EF71F2D39FD37359EC4B28C8DAA03192C
SHA-256	BD5BDF580E7B0808ADE744D048B84404F60E70DB1B3EC5996C4D223EC9A4248C

Key	Value
MD5	7CE253B605366EE43A4D83B43701DF10
PackageArch	noarch
PackageDescription	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.
PackageName	python3-dogpile.cache
PackageRelease	lp151.3.1
PackageVersion	1.1.1
SHA-1	166190041DF0B4DE5E8925F6CB37A95E67D37B93
SHA-256	3EAE6F3B8241ADBD5D5BAD405ABE7F91CF4901332F68934226BE8CAA75A873D9

Key	Value
FileName	http://archlinux.mirror.root.lu//pool//community//python-dogpile.cache-1.1.1-1-any.pkg.tar.zst
MD5	B2F6A993D0BE18B41E5E17B66D04EA57
SHA-1	31A5E0327B2E57094FA056D038BCC006E04F48AB
SHA-256	43B072910F93BBBCF5ED9A65F46FE6E3D76028843EAA0BC94DA4B4F17F7E3842
SSDEEP	1536:WmNjUeUTg/qQzLp+7EZyeInErzJ+GHNHpLpjJ:WmNjUMyQJ+QceInEn/HVjJ
TLSH	T15E73126D870264E882D71CBAFCFB66DA8FE4771960768E4FE92595DC0072BEC40128D7

Key	Value
SHA-1	2BF88BD30D3EF684D45CADD2B878C558BF6DF9AB
snap-authority	canonical
snap-filename	wtnUl2mGUjjFg6QI4N7lLQYVmRZSiPDh_34.snap
snap-id	wtnUl2mGUjjFg6QI4N7lLQYVmRZSiPDh_34
snap-name	openstack-hypervisor
snap-publisher-id	canonical
snap-signkey	BWDEoaqyr25nF5SNCvEv2v7QnM9QsfCc0PBMYD_i2NGSQ32EF2d4D0hqUel3m8ul
snap-timestamp	2022-10-25T09:34:36.700100Z
source-url	https://api.snapcraft.io/api/v1/snaps/download/wtnUl2mGUjjFg6QI4N7lLQYVmRZSiPDh_34.snap

Key	Value
MD5	834540F3995EA956E4954955EDFC309C
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	python3-dogpile-cache
PackageRelease	1.el8
PackageVersion	1.1.2
SHA-1	0BBF31217C403B01D3518421C015525801B4C3FC
SHA-256	2C18A4CBF1886C52FA832C84EEBD92285CAFA811FF4C2815D16C904326186FC0

Key	Value
SHA-1	0BC079CD058066A35171CF7F1887249784E94156