Hello community,

here is the log from the commit of package python-semver for openSUSE:Factory 
checked in at 2020-05-19 14:58:26
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-semver (Old)
 and      /work/SRC/openSUSE:Factory/.python-semver.new.2738 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "python-semver"

Tue May 19 14:58:26 2020 rev:12 rq:807288 version:2.10.0

Changes:
--------
--- /work/SRC/openSUSE:Factory/python-semver/python-semver.changes      
2020-05-11 13:37:35.880645196 +0200
+++ /work/SRC/openSUSE:Factory/.python-semver.new.2738/python-semver.changes    
2020-05-19 14:58:39.457423749 +0200
@@ -1,0 +2,5 @@
+Tue May 19 09:27:55 UTC 2020 - Petr Gajdos <pgaj...@suse.com>
+
+- %python3_only -> %python_alternative
+
+-------------------------------------------------------------------

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ python-semver.spec ++++++
--- /var/tmp/diff_new_pack.4mnRCl/_old  2020-05-19 14:58:41.733428796 +0200
+++ /var/tmp/diff_new_pack.4mnRCl/_new  2020-05-19 14:58:41.737428805 +0200
@@ -31,6 +31,8 @@
 BuildRequires:  %{python_module setuptools}
 BuildRequires:  fdupes
 BuildRequires:  python-rpm-macros
+Requires(post): update-alternatives
+Requires(postun): update-alternatives
 # See https://github.com/k-bx/python-semver/issues/67 for why conflicts is 
needed
 Conflicts:      python-node-semver
 BuildArch:      noarch
@@ -48,16 +50,23 @@
 
 %install
 %python_install
+%python_clone -a %{buildroot}%{_bindir}/pysemver
 
 %python_expand %fdupes %{buildroot}%{$python_sitelib}
 
 %check
 %pytest
 
+%post
+%python_install_alternative pysemver
+
+%postun
+%python_uninstall_alternative pysemver
+
 %files %{python_files}
 %doc README.rst
 %{python_sitelib}/semver*
 %pycache_only %{python_sitelib}/__pycache__/semver*
-%python3_only %{_bindir}/pysemver
+%python_alternative %{_bindir}/pysemver
 
 %changelog


Reply via email to