[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#689140: unblock: bitlbee/3.0.5-1.2



Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock

Please unblock package bitlbee

It fixes a serious mess of the “directory replaced by symlink”-kind.

unblock bitlbee/3.0.5-1.2

Thanks in advance, regards.

David

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.5-trunk-amd64 (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -u bitlbee-3.0.5/debian/changelog bitlbee-3.0.5/debian/changelog
--- bitlbee-3.0.5/debian/changelog
+++ bitlbee-3.0.5/debian/changelog
@@ -1,3 +1,11 @@
+bitlbee (3.0.5-1.2) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * debian/bitlbee{,-dev}.postinst: Fix directory to symlink upgrade in
+    postinst. (Closes: #687865)
+
+ -- David Prévot <taffit@debian.org>  Wed, 26 Sep 2012 23:20:41 -0400
+
 bitlbee (3.0.5-1.1) unstable; urgency=low
 
   * Non-maintainer upload.
only in patch2:
unchanged:
--- bitlbee-3.0.5.orig/debian/bitlbee.postinst
+++ bitlbee-3.0.5/debian/bitlbee.postinst
@@ -0,0 +1,14 @@
+#!/bin/sh
+set -e
+
+# Replace documentation directory with symlink
+docdir="/usr/share/doc/bitlbee"
+if [ -d $docdir ] && [ ! -L $docdir ]; then
+    if rmdir $docdir 2>/dev/null; then
+        ln -sf bitlbee-common $docdir
+    fi
+fi
+
+#DEBHELPER#
+
+exit 0
only in patch2:
unchanged:
--- bitlbee-3.0.5.orig/debian/bitlbee-dev.postinst
+++ bitlbee-3.0.5/debian/bitlbee-dev.postinst
@@ -0,0 +1,14 @@
+#!/bin/sh
+set -e
+
+# Replace documentation directory with symlink
+docdir="/usr/share/doc/bitlbee-dev"
+if [ -d $docdir ] && [ ! -L $docdir ]; then
+    if rmdir $docdir 2>/dev/null; then
+        ln -sf bitlbee-common $docdir
+    fi
+fi
+
+#DEBHELPER#
+
+exit 0

Reply to: