Followup-For: Bug #668443
Control: tag -1 patch

Hi,

sessioninstaller has misnamed the prerm script as "prerem" and a wrong
path it it, causing alternative removal to fail. A patch is attached.


Andreas
diffstat for sessioninstaller-0.20 sessioninstaller-0.20

 changelog |    8 ++++++++
 prerem    |   15 ---------------
 prerm     |   15 +++++++++++++++
 3 files changed, 23 insertions(+), 15 deletions(-)

diff -Nru sessioninstaller-0.20/debian/changelog sessioninstaller-0.20/debian/changelog
--- sessioninstaller-0.20/debian/changelog	2010-07-12 14:11:50.000000000 +0200
+++ sessioninstaller-0.20/debian/changelog	2013-01-16 01:28:03.000000000 +0100
@@ -1,3 +1,11 @@
+sessioninstaller (0.20-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Rename debian/prerem => debian/prerm to activate the prerm script and
+    cleanup the gstreamer-codec-install alternative.  (Closes: #668443)
+
+ -- Andreas Beckmann <[email protected]>  Wed, 16 Jan 2013 01:28:03 +0100
+
 sessioninstaller (0.20-1) unstable; urgency=low
 
   * New upstream release.
diff -Nru sessioninstaller-0.20/debian/prerem sessioninstaller-0.20/debian/prerem
--- sessioninstaller-0.20/debian/prerem	2010-07-12 14:11:50.000000000 +0200
+++ sessioninstaller-0.20/debian/prerem	1970-01-01 01:00:00.000000000 +0100
@@ -1,15 +0,0 @@
-#!/bin/sh
-# prerm script for sessioninstaller
-
-set -e
-
-if [ "$1" = "remove" ] || [ "$1" = "deconfigure" ] ; then
-	update-alternatives --remove gstreamer-codec-install \
-			    /usr/bin/gst-installer || true
-
-fi
-
-#DEBHELPER#
-
-exit 0
-
diff -Nru sessioninstaller-0.20/debian/prerm sessioninstaller-0.20/debian/prerm
--- sessioninstaller-0.20/debian/prerm	1970-01-01 01:00:00.000000000 +0100
+++ sessioninstaller-0.20/debian/prerm	2013-01-16 02:47:08.000000000 +0100
@@ -0,0 +1,15 @@
+#!/bin/sh
+# prerm script for sessioninstaller
+
+set -e
+
+if [ "$1" = "remove" ] || [ "$1" = "deconfigure" ] ; then
+	update-alternatives --remove gstreamer-codec-install \
+			    /usr/bin/gst-install || true
+
+fi
+
+#DEBHELPER#
+
+exit 0
+

Reply via email to