Your message dated Thu, 30 Aug 2007 18:20:03 -0400
with message-id <[EMAIL PROTECTED]>
and subject line appears to be fixed in 0.99.8-1
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: quagga
Version: 0.99.4-2
Severity: serious
quagga fails to upgrade:
| Preparing to replace quagga 0.99.3-1 (using .../quagga_0.99.4-2_amd64.deb) ...
| As requested via Debconf, the Quagga daemon will not stop.
| dpkg: warning - old pre-removal script returned error exit status 1
| dpkg - trying script from the new package instead ...
| As requested via Debconf, the Quagga daemon will not stop.
| dpkg: error processing /var/cache/apt/archives/quagga_0.99.4-2_amd64.deb
(--unpack):
| subprocess new pre-removal script returned error exit status 1
| Loading capability module if not yet done.
| Starting Quagga daemons (prio:10):.
| Errors were encountered while processing:
| /var/cache/apt/archives/quagga_0.99.4-2_amd64.deb
| E: Sub-process /usr/bin/dpkg returned an error code (1)
Bastian
--
Humans do claim a great deal for that particular emotion (love).
-- Spock, "The Lights of Zetar", stardate 5725.6
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
It looks like the maintainer rewrote the prerm script (see attached
diff) to fix this bug. I verified that it's possible to upgrade quagga
-- it now displays a high priority debconf question on upgrade if quagga
daemons are running.
--
Robert Edmonds
[EMAIL PROTECTED]
--- quagga-0.99.4/debian/quagga.prerm 2007-08-30 18:05:05.000000000 -0400
+++ quagga-0.99.8/debian/quagga.prerm 2007-08-30 17:44:23.000000000 -0400
@@ -5,15 +5,34 @@
if [ -n "$DEBIAN_SCRIPT_DEBUG" ]; then set -v -x; DEBIAN_SCRIPT_TRACE=1; fi
${DEBIAN_SCRIPT_TRACE:+ echo "#42#DEBUG# RUNNING $0 $*"}
-# Trying to prevents the user from cutting his network connection...
-db_fset quagga/really_stop seen false || true
-db_input medium quagga/really_stop || true
-db_go || true
-db_get quagga/really_stop || true
-if [ "$RET" = "false" ]; then
- db_stop
- echo "As requested via Debconf, the Quagga daemon will not stop." 1>&2
- exit 1
-fi
+# prerm remove
+# old-prerm upgrade new-version
+# new-prerm failed-upgrade old-version
+# conflictor's-prerm remove in-favour package new-version
+# deconfigured's-prerm deconfigure in-favour package-being-installed version removing conflicting-package
+case $1 in
+ remove|upgrade)
+ # Trying to prevents the user from cutting his network connection if
+ # one or more servers seem to be started.
+ if [ -n "`ls /var/run/quagga/*.pid 2>/dev/null`" ]; then
+ db_fset quagga/really_stop seen false || true
+ db_input high quagga/really_stop || true
+ db_go || true
+ db_get quagga/really_stop || true
+ if [ "$RET" = "false" ]; then
+ db_stop
+ echo "*** As requested via Debconf, the Quagga daemon will not stop! ***" 1>&2
+ exit 1
+ fi
+ fi
+ ;;
+
+ failed-upgrade)
+ # If quagga/really_stop was negated then this script exits with return
+ # code 1 and is called again with "failed-upgrade". Well, exit again.
+ exit 1
+ ;;
+
+esac
#DEBHELPER#
signature.asc
Description: Digital signature
--- End Message ---
