diff --git a/dogpile.cache-0.6.7.tar.gz b/dogpile.cache-0.6.7.tar.gz new file mode 100644 index 0000000000000000000000000000000000000000..4baf81772bc9a09b5f6ca4c61e742cbd85d5a4d6 Binary files /dev/null and b/dogpile.cache-0.6.7.tar.gz differ diff --git a/dogpile.cache-1.1.0.tar.gz b/dogpile.cache-1.1.0.tar.gz deleted file mode 100644 index 1f52e1412b41f6125a89104e619c5153913182bd..0000000000000000000000000000000000000000 Binary files a/dogpile.cache-1.1.0.tar.gz and /dev/null differ diff --git a/python-dogpile.cache.spec b/python-dogpile.cache.spec index 4c149ed49e7329eb902487a64051126573abb7fd..8c2682d08417f14da60fa0cf494552beaadd6b9f 100644 --- a/python-dogpile.cache.spec +++ b/python-dogpile.cache.spec @@ -1,81 +1,41 @@ %global _empty_manifest_terminate_build 0 Name: python-dogpile-cache -Version: 1.1.0 +Version: 0.6.7 Release: 1 Summary: A caching front-end based on the Dogpile lock. -License: MIT -URL: https://github.com/sqlalchemy/dogpile.cache -Source0: https://files.pythonhosted.org/packages/3d/2c/88f428ceb69604ea64dc5b84a79784dc410c40cbc8f023210e93028573db/dogpile.cache-1.1.0.tar.gz +License: BSD +URL: http://bitbucket.org/zzzeek/dogpile.cache +Source0: https://files.pythonhosted.org/packages/ee/bd/440da735a11c6087eed7cc8747fc4b995cbac2464168682f8ee1c8e43844/dogpile.cache-0.6.7.tar.gz BuildArch: noarch - - %description -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. +A caching front-end based on the Dogpile lock. + -%package -n python3-dogpile-cache +%package -n python2-dogpile-cache Summary: A caching front-end based on the Dogpile lock. Provides: python-dogpile-cache -BuildRequires: python3-devel -BuildRequires: python3-setuptools -%description -n python3-dogpile-cache -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. +BuildRequires: python2-devel +BuildRequires: python2-setuptools +BuildRequires: python2-pip +%description -n python2-dogpile-cache +A caching front-end based on the Dogpile lock. + %package help Summary: Development documents and examples for dogpile.cache -Provides: python3-dogpile-cache-doc +Provides: python2-dogpile-cache-doc %description help -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. +A caching front-end based on the Dogpile lock. + %prep -%autosetup -n dogpile.cache-1.1.0 +%autosetup -n dogpile.cache-0.6.7 %build -%py3_build +%py2_build %install -%py3_install +%py2_install install -d -m755 %{buildroot}/%{_pkgdocdir} if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi @@ -102,12 +62,12 @@ popd mv %{buildroot}/filelist.lst . mv %{buildroot}/doclist.lst . -%files -n python3-dogpile-cache -f filelist.lst -%dir %{python3_sitelib}/* +%files -n python2-dogpile-cache -f filelist.lst +%dir %{python2_sitelib}/* %files help -f doclist.lst %{_docdir}/* %changelog -* Sat Nov 21 2020 Python_Bot +* Thu Apr 29 2021 openstack-sig - Package Spec generated