tags 579312 + patch
tags 579312 + pending
thanks

Dear maintainer,

I've prepared an NMU for canna (versioned as 3.7p3-6.5) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u canna-3.7p3/debian/changelog canna-3.7p3/debian/changelog
--- canna-3.7p3/debian/changelog
+++ canna-3.7p3/debian/changelog
@@ -1,3 +1,15 @@
+canna (3.7p3-6.5) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Urgency high due to RC bug fix
+  * Fix problem when trying to delete user twice on purge (postrm purge
+    might be indeed called twice; see http://lists.debian.org/debian-devel/2002/10/msg00345.html
+    for details) (Closes: #579312)
+  * Also fix lintian error on weak library dependency for libcanna1g-dev
+    on libcanna1g by version the dependency with (= ${binary:Version})
+
+ -- Alexander Reichle-Schmehl <toli...@debian.org>  Wed, 24 Nov 2010 11:31:07 +0100
+
 canna (3.7p3-6.4) unstable; urgency=low
 
   * Non-maintainer upload.
diff -u canna-3.7p3/debian/postrm canna-3.7p3/debian/postrm
--- canna-3.7p3/debian/postrm
+++ canna-3.7p3/debian/postrm
@@ -5,7 +5,12 @@
 case "$1" in
     purge)
     rm -rf /var/log/canna
-    deluser --remove-home canna
+    # see http://lists.debian.org/debian-devel/2002/10/msg00345.html
+    # debhelper might cause this script to be called twice on purge
+    # therefore test, if the user exists before trying to remove it
+    if getent passwd canna >/dev/null ;  then
+      deluser --remove-home canna
+    fi
     rm -f /etc/default/canna
     rm -f /etc/hosts.canna
     rm -rf /var/lib/canna/dic/group
diff -u canna-3.7p3/debian/control canna-3.7p3/debian/control
--- canna-3.7p3/debian/control
+++ canna-3.7p3/debian/control
@@ -53,7 +53,7 @@
 Package: libcanna1g-dev
 Section: libdevel
 Architecture: any
-Depends: ${misc:Depends}, libcanna1g
+Depends: ${misc:Depends}, libcanna1g (= ${binary:Version})
 Conflicts: canna-dev, libcanna1-dev, canna (<= 3.5b2-23)
 Replaces: canna-dev
 Description: input system for Japanese - development files

Reply via email to