Hello community, here is the log from the commit of package python-coverage for openSUSE:Factory checked in at 2013-05-16 16:15:40 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/python-coverage (Old) and /work/SRC/openSUSE:Factory/.python-coverage.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-coverage" Changes: -------- --- /work/SRC/openSUSE:Factory/python-coverage/python-coverage.changes 2013-05-03 13:44:19.000000000 +0200 +++ /work/SRC/openSUSE:Factory/.python-coverage.new/python-coverage.changes 2013-05-16 16:15:41.000000000 +0200 @@ -1,0 +2,5 @@ +Wed May 15 14:50:46 UTC 2013 - [email protected] + +- Fix update-alternatives and support upgrade from previous versions + +------------------------------------------------------------------- --- /work/SRC/openSUSE:Factory/python-coverage/python3-coverage.changes 2013-05-03 13:44:19.000000000 +0200 +++ /work/SRC/openSUSE:Factory/.python-coverage.new/python3-coverage.changes 2013-05-16 16:15:41.000000000 +0200 @@ -1,0 +2,5 @@ +Wed May 15 14:51:01 UTC 2013 - [email protected] + +- Fix update-alternatives and support upgrade from previous versions + +------------------------------------------------------------------- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ python-coverage.spec ++++++ --- /var/tmp/diff_new_pack.bSsWGl/_old 2013-05-16 16:15:41.000000000 +0200 +++ /var/tmp/diff_new_pack.bSsWGl/_new 2013-05-16 16:15:41.000000000 +0200 @@ -51,6 +51,8 @@ %install python setup.py install --prefix=%{_prefix} --root=%{buildroot} +rm %{buildroot}%{_bindir}/coverage +ln -s %{_bindir}/coverage-%{py_ver} %{buildroot}/%{_bindir}/coverage #NOTE(saschpe): The following seems to mess with the install dir, which is odd: #%%check @@ -61,11 +63,17 @@ #python setup.py --quiet build_ext --inplace #python igor.py test_with_tracer c +%pre +# Since /usr/bin/coverage became ghosted to be used with update-alternatives, we have +# to get rid of the old binary resulting from the non-update-alternativies-ified package: +[[ ! -L %{_bindir}/coverage ]] && rm -f %{_bindir}/coverage +exit 0 + %post update-alternatives \ - --install %{_bindir}/coverage coverage %{_bindir}/coverage-%{py_ver} 10 + --install %{_bindir}/coverage coverage %{_bindir}/coverage-%{py_ver} 20 -%postun +%preun if [ $1 -eq 0 ] ; then update-alternatives --remove coverage %{_bindir}/coverage-%{py_ver} fi @@ -73,7 +81,7 @@ %files %defattr(-,root,root,-) %doc AUTHORS.txt CHANGES.txt README.txt -%ghost %attr(0755,root,root) %{_bindir}/coverage +%ghost %{_bindir}/coverage %{_bindir}/coverage2 %{_bindir}/coverage-%{py_ver} %{python_sitearch}/coverage/ ++++++ python3-coverage.spec ++++++ --- /var/tmp/diff_new_pack.bSsWGl/_old 2013-05-16 16:15:41.000000000 +0200 +++ /var/tmp/diff_new_pack.bSsWGl/_new 2013-05-16 16:15:41.000000000 +0200 @@ -45,12 +45,20 @@ %install python3 setup.py install --prefix=%{_prefix} --root=%{buildroot} +rm %{buildroot}%{_bindir}/coverage +ln -s %{_bindir}/coverage-%{py3_ver} %{buildroot}/%{_bindir}/coverage + +%pre +# Since /usr/bin/coverage became ghosted to be used with update-alternatives, we have +# to get rid of the old binary resulting from the non-update-alternativies-ified package: +[[ ! -L %{_bindir}/coverage ]] && rm -f %{_bindir}/coverage +exit 0 %post update-alternatives \ - --install %{_bindir}/coverage coverage %{_bindir}/coverage-%{py3_ver} 10 + --install %{_bindir}/coverage coverage %{_bindir}/coverage-%{py3_ver} 30 -%postun +%preun if [ $1 -eq 0 ] ; then update-alternatives --remove coverage %{_bindir}/coverage-%{py3_ver} fi @@ -58,7 +66,7 @@ %files %defattr(-,root,root,-) %doc AUTHORS.txt CHANGES.txt README.txt -%ghost %attr(0755,root,root) %{_bindir}/coverage +%ghost %{_bindir}/coverage %{_bindir}/coverage3 %{_bindir}/coverage-%{py3_ver} %{python3_sitearch}/coverage -- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
