Hello community,

here is the log from the commit of package python3-pylint for openSUSE:Factory 
checked in at 2014-11-18 22:45:32
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python3-pylint (Old)
 and      /work/SRC/openSUSE:Factory/.python3-pylint.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "python3-pylint"

Changes:
--------
--- /work/SRC/openSUSE:Factory/python3-pylint/python3-pylint.changes    
2014-07-11 06:46:53.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.python3-pylint.new/python3-pylint.changes       
2014-11-18 22:46:10.000000000 +0100
@@ -1,0 +2,5 @@
+Sat Nov 08 21:37:00 UTC 2014 - Led <[email protected]>
+
+- fix bashisms in pre script
+
+-------------------------------------------------------------------

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

Other differences:
------------------
++++++ python3-pylint.spec ++++++
--- /var/tmp/diff_new_pack.sltKt4/_old  2014-11-18 22:46:11.000000000 +0100
+++ /var/tmp/diff_new_pack.sltKt4/_new  2014-11-18 22:46:11.000000000 +0100
@@ -78,12 +78,11 @@
 %pre
 # Since /usr/bin/pylint, etc. 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}/pylint ]] && rm -f %{_bindir}/pylint
-[[ ! -L %{_bindir}/epylint ]] && rm -f %{_bindir}/epylint
-[[ ! -L %{_bindir}/pylint-gui ]] && rm -f %{_bindir}/pylint-gui
-[[ ! -L %{_bindir}/pyreverse ]] && rm -f %{_bindir}/pyreverse
-[[ ! -L %{_bindir}/symilar ]] && rm -f %{_bindir}/symilar
-exit 0
+[ -h %{_bindir}/pylint ] || rm -f %{_bindir}/pylint
+[ -h %{_bindir}/epylint ] || rm -f %{_bindir}/epylint
+[ -h %{_bindir}/pylint-gui ] || rm -f %{_bindir}/pylint-gui
+[ -h %{_bindir}/pyreverse ] || rm -f %{_bindir}/pyreverse
+[ -h %{_bindir}/symilar ] || rm -f %{_bindir}/symilar
 
 %post
 update-alternatives \

-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to