Your message dated Wed, 07 Mar 2007 23:47:03 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#405672: fixed in firestarter 1.0.3-2
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: firestarter
Version: 1.0.3-1.1
Hello. This is a bug initially reported at http://launchpad.net/bugs/38755.
"It seems desirable for firestarter to upgrade in a more atomic manner.
To illustrate, here is an excerpt of a recent upgrade run on dapper:
===snip===
Preparing to replace firestarter 1.0.3-1.1ubuntu1 (using
.../firestarter_1.0.3-1.1ubuntu2_i386.deb) ...
Stopping the Firestarter firewall:done.
Unpacking replacement firestarter ...
Preparing to replace gcc-4.0-doc 4.0.3-1ubuntu3 (using
.../gcc-4.0-doc_4.0.3-1ubuntu4_all.deb) ...
Unpacking replacement gcc-4.0-doc ...
Preparing to replace gnome-app-install 0.1.23 (using
.../gnome-app-install_0.1.26_all.deb) ...
Unpacking replacement gnome-app-install ...
Setting up libmudflap0 (4.0.3-1ubuntu4) ...
Setting up cpp-4.0 (4.0.3-1ubuntu4) ...
Setting up gcc-4.0 (4.0.3-1ubuntu4) ...
Setting up libmudflap0-dev (4.0.3-1ubuntu4) ...
Setting up app-install-data (0.1.26) ...
Setting up cpp-4.0-doc (4.0.3-1ubuntu4) ...
Setting up firestarter (1.0.3-1.1ubuntu2) ...
Starting the Firestarter firewall: done.
===snip===
As you can see, the stopping of the firewall (in the pre-rm?) can be separated
from the starting
of the firewall (in the post-inst?) by a significant delay, if there are a
number of packages to
be upgraded.
The above was during a relatively-frequent dapper upgrade, but I'm thinking
more of the
much-longer upgrades, such as the breezy=>dapper dist-upgrade, for example.
Is there a plausible manner to change "invoke-rc.d firestarter stop" to
"invoke-rc.d firestarter
restart" or something similar, and still accomplish what you need during
upgrade? I've seen that
some packages appear to issue two "restart"s rather than a "stop" and
subsequent "start", but
never questioned the rationale (or mechanism).
The goal of course would be to limit the users' exposure to running without an
active firewall,
especially on machines where the admin doing the upgrade is not the sole active
user. (ie, remote
upgrades)"
It would be great if you took a look into this issue!
Thanks for your time,
Vassilis Pandis
Send instant messages to your online friends http://uk.messenger.yahoo.com
--- End Message ---
--- Begin Message ---
Source: firestarter
Source-Version: 1.0.3-2
We believe that the bug you reported is fixed in the latest version of
firestarter, which is due to be installed in the Debian FTP archive:
firestarter_1.0.3-2.diff.gz
to pool/main/f/firestarter/firestarter_1.0.3-2.diff.gz
firestarter_1.0.3-2.dsc
to pool/main/f/firestarter/firestarter_1.0.3-2.dsc
firestarter_1.0.3-2_i386.deb
to pool/main/f/firestarter/firestarter_1.0.3-2_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Yann Verley <[EMAIL PROTECTED]> (supplier of updated firestarter package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Tue, 13 Feb 2007 23:30:42 +0100
Source: firestarter
Binary: firestarter
Architecture: source i386
Version: 1.0.3-2
Distribution: unstable
Urgency: low
Maintainer: [EMAIL PROTECTED]
Changed-By: Yann Verley <[EMAIL PROTECTED]>
Description:
firestarter - gtk program for managing and observing your firewall
Closes: 254971 286666 295336 300143 303973 314286 338550 375189 384447 399752
405672 405674 407331
Changes:
firestarter (1.0.3-2) unstable; urgency=low
.
* Fix postrm script on purge (closes: #303973, #338550, #375189)
* Fix preinst script (closes: #300143, #314286)
* Update non-routables file (closes: #407331)
* Update swedish translation. Thanks Daniel Nylander (closes: #384447)
* Apply transparent icon patch from Ubuntu (closes: #295336)
* Add a suggest on dhcp3-server and apply patches for dhcp from Ubuntu
(closes: #399752, #405674)
* Use dh_installinit --no-start instead of dh_installinit and fix postinst
script in order to have "an atomic upgrade" (closes: #286666, #405672)
* Don't fail on upgrade when firewalled interface has changed (closes:
#254971)
Files:
1a01204b8dda1829ace6dadcd2cf5aac 732 admin optional firestarter_1.0.3-2.dsc
6a42ddb73a39a6eab33a6a98b371d25f 52714 admin optional
firestarter_1.0.3-2.diff.gz
02f5f5f6e06e9a35333dfa5c8a04360e 405082 admin optional
firestarter_1.0.3-2_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iEYEARECAAYFAkXvSs4ACgkQIzuKV+SHX/mB5wCeNUwEx9cXoiz7UVbEDDoJ5zZZ
5/EAniK7byT3VvmRq4u3c9tb12BKfB8z
=PWSk
-----END PGP SIGNATURE-----
--- End Message ---
