!8 update version to 1.1.2

From: @zhangy1317
Reviewed-by: @shinwell_hu
Signed-off-by: @shinwell_hu

python-dogpile.cache.spec

@@ -1,30 +1,15 @@
 %global _empty_manifest_terminate_build 0
 Name:		python-dogpile-cache
-Version:	1.1.0
+Version:	1.1.2
 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
+Source0:	https://files.pythonhosted.org/packages/55/51/24484f0f713f3499da44f5b4483cf0e5b5284572980530065b97b3d41c83/dogpile.cache-1.1.2.tar.gz
 BuildArch:	noarch
-
-
 %description
-Dogpile consists of two subsystems, one building on top of the other.
+A caching front-end based on the Dogpile lock.
-``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
-<https://pypi.org/project/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.
 
 %package -n python3-dogpile-cache
 Summary:	A caching front-end based on the Dogpile lock.
@@ -32,44 +17,18 @@ 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.
+A caching front-end based on the Dogpile lock.
-``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
-<https://pypi.org/project/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.
 
 %package help
 Summary:	Development documents and examples for dogpile.cache
 Provides:	python3-dogpile-cache-doc
 %description help
-Dogpile consists of two subsystems, one building on top of the other.
+A caching front-end based on the Dogpile lock.
-``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
-<https://pypi.org/project/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.
 
 %prep
-%autosetup -n dogpile.cache-1.1.0
+%autosetup -n dogpile.cache-1.1.2
 
 %build
 %py3_build
@@ -102,6 +61,9 @@ popd
 mv %{buildroot}/filelist.lst .
 mv %{buildroot}/doclist.lst .
 
+%check
+%{__python3} -m pytest || true
+
 %files -n python3-dogpile-cache -f filelist.lst
 %dir %{python3_sitelib}/*
 
@@ -109,5 +71,8 @@ mv %{buildroot}/doclist.lst .
 %{_docdir}/*
 
 %changelog
+* Fri Jul 09 2021 openstack-sig <openstack@openeuler.org>
+- Package Spec generated
+
 * Sat Nov 21 2020 Python_Bot <Python_Bot@openeuler.org>
 - Package Spec generated