Your message dated Sun, 25 Nov 2012 14:23:01 +0100
with message-id <[email protected]>
and subject line Closed as removal request for ampache/wheezy has been filed.
has caused the Debian Bug report #692122,
regarding unblock: ampache/ampache-3.6-git408e713+dfsg-3.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 [email protected]
immediately.)


-- 
692122: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692122
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: unblock

Please unblock package ampache

Ampache has been NMU'd please unblock

unblock ampache/ampache-3.6-git408e713+dfsg-3.1

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-3-686-pae (SMP w/1 CPU core)
diff -Nru ampache-3.6-git408e713+dfsg/debian/ampache.postrm ampache-3.6-git408e713+dfsg/debian/ampache.postrm
--- ampache-3.6-git408e713+dfsg/debian/ampache.postrm	2012-06-07 00:44:04.000000000 -0500
+++ ampache-3.6-git408e713+dfsg/debian/ampache.postrm	2012-10-14 10:13:27.000000000 -0500
@@ -4,24 +4,6 @@
 
 . /usr/share/debconf/confmodule
 
-rm_log(){
-	if [ -d /var/log/ampache ]; then
-		rm -rf /var/log/ampache
-	fi
-}
-
-rm_logr(){
-	if [ -f /etc/logrotate.d/ampache ]; then
-		rm -f /etc/logrotate.d/ampache
-	fi
-}
-
-rm_cron(){
-	if [ -f /etc/cron.daily/ampache ]; then
-		rm -f /etc/cron.daily/ampache
-	fi
-}
-
 restart_server(){
 	if [ -e /var/run/apache2.pid ]; then
 		service apache2 reload
@@ -32,25 +14,14 @@
 	db_get ampache/restart_webserver || true
 	re_start="$RET"
 	if [ "$re_start" = "false" ]; then
-		rm_log
-		rm_logr
-		rm_cron
+		printf "Please restart the web server manually."
 	elif [ "$re_start" = "true" ]; then
-		rm_log
-		rm_logr
-		rm_cron
 		restart_server
 	else
 		printf "unable to de-configure ampache, please do so manually.\n"
 	fi
 fi
 
-if [ "$1" = "purge" ]; then
-	if [ -d /etc/ampache ]; then
-		rm -rf /etc/ampache
-	fi
-fi
-
 #DEBHELPER#
 
 exit 0
diff -Nru ampache-3.6-git408e713+dfsg/debian/ampache.prerm ampache-3.6-git408e713+dfsg/debian/ampache.prerm
--- ampache-3.6-git408e713+dfsg/debian/ampache.prerm	1969-12-31 18:00:00.000000000 -0600
+++ ampache-3.6-git408e713+dfsg/debian/ampache.prerm	2012-10-14 10:18:01.000000000 -0500
@@ -0,0 +1,8 @@
+#!/bin/sh -e
+
+# This link is created on postinst, so must be removed explicitly.
+rm -f /etc/ampache/ampache.conf
+
+#DEBHELPER#
+
+exit 0
diff -Nru ampache-3.6-git408e713+dfsg/debian/changelog ampache-3.6-git408e713+dfsg/debian/changelog
--- ampache-3.6-git408e713+dfsg/debian/changelog	2012-06-07 01:01:21.000000000 -0500
+++ ampache-3.6-git408e713+dfsg/debian/changelog	2012-10-14 10:15:09.000000000 -0500
@@ -1,3 +1,17 @@
+ampache (3.6-git408e713+dfsg-3.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Remove generated link in prerm.  Closes: #688436
+
+ -- Bas Wijnen <[email protected]>  Sun, 14 Oct 2012 16:31:58 +0200
+
+ampache (3.6-git408e713+dfsg-3) unstable; urgency=low
+
+  * Remove statements in debian/ampache.postrm that manually remove conffiles,
+    log files on remove and purge.  Closes: #688436
+
+ -- Charlie Smotherman <[email protected]>  Sat, 22 Sep 2012 14:24:41 -0500
+
 ampache (3.6-git408e713+dfsg-2) unstable; urgency=low
 
   * Added functions to ampache.postrm so it is formated similar to 

--- End Message ---
--- Begin Message ---
Removal of package ampache from wheezy has been requested in #694318.

Please also thwap Enrico Zini if this was wrong, he told me to do it, and I trusted him. ;-)

Kind Regards,
Stefan Baur (part of the Debian Bug Squashing Party taking place at the Linuxhotel, Essen, Germany this weekend)
--- End Message ---

Reply via email to