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

Bug#926989: marked as done (unblock: nagzilla/2.0-1.1)

Your message dated Sun, 14 Apr 2019 11:06:12 +0000
with message-id <E1hFcxg-00020w-7b@respighi.debian.org>
and subject line unblock nagzilla
has caused the Debian Bug report #926989,
regarding unblock: nagzilla/2.0-1.1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
926989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926989
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock

Please unblock package nagzilla

This NMU fixes a logrotate problem after package removal discovered by
piuparts.
No longer delete the user and group after package removal since it is
still referenced in the config file. Also keep the user/group after
purge which is the nowadays generally recommended way of handling system
users. I verified that the package reinstalls without problems after it
has been purged, but the user/group remained.

unblock nagzilla/2.0-1.1


Thanks for considering,

Andreas

diff -Nru nagzilla-2.0/debian/changelog nagzilla-2.0/debian/changelog
--- nagzilla-2.0/debian/changelog	2016-01-20 00:14:45.000000000 +0100
+++ nagzilla-2.0/debian/changelog	2019-04-02 20:16:12.000000000 +0200
@@ -1,3 +1,11 @@
+nagzilla (2.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Do not delete the nagzilla user and group after package removal.
+    (Closes: #915662)
+
+ -- Andreas Beckmann <anbe@debian.org>  Tue, 02 Apr 2019 20:16:12 +0200
+
 nagzilla (2.0-1) unstable; urgency=medium
 
   * New upstream release, obsoleting patch 05_fix-logrotate-file and
diff -Nru nagzilla-2.0/debian/postrm nagzilla-2.0/debian/postrm
--- nagzilla-2.0/debian/postrm	2016-01-18 21:35:54.000000000 +0100
+++ nagzilla-2.0/debian/postrm	1970-01-01 01:00:00.000000000 +0100
@@ -1,39 +0,0 @@
-#!/bin/sh
-# postrm script for nagzilla
-#
-# see: dh_installdeb(1)
-
-set -e
-
-# summary of how this script can be called:
-#        * <postrm> `remove'
-#        * <postrm> `purge'
-#        * <old-postrm> `upgrade' <new-version>
-#        * <new-postrm> `failed-upgrade' <old-version>
-#        * <new-postrm> `abort-install'
-#        * <new-postrm> `abort-install' <old-version>
-#        * <new-postrm> `abort-upgrade' <old-version>
-#        * <disappearer's-postrm> `disappear' <overwriter>
-#          <overwriter-version>
-# for details, see http://www.debian.org/doc/debian-policy/ or
-# the debian-policy package
-
-
-case "$1" in
-    purge|remove|upgrade|failed-upgrade|abort-install|abort-upgrade|disappear)
-        deluser --quiet --system nagzilla > /dev/null || true
-        delgroup --quiet --system nagzilla > /dev/null || true
-    ;;
-
-    *)
-        echo "postrm called with unknown argument \`$1'" >&2
-        exit 1
-    ;;
-esac
-
-# dh_installdeb will replace this with shell code automatically
-# generated by other debhelper scripts.
-
-#DEBHELPER#
-
-exit 0

--- End Message ---
--- Begin Message --- 
Unblocked nagzilla.

--- End Message ---
Reply to: