Comment 9 for bug 11746

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Thu, 30 Dec 2004 20:51:41 -0500
From: Eric Dorland <email address hidden>
To: Alexandre <email address hidden>, <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#287355: mozilla-firefox-gnome-support: fails to uninstall

--rJ8inJ6ig7iY3YX9
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

tags 287355 important
thanks

* Alexandre (<email address hidden>) wrote:
> On Mon, Dec 27, 2004 at 04:36:01PM -0500, Eric Dorland wrote:
> > * Alexandre Fayolle (<email address hidden>) wrote:
> > > Package: mozilla-firefox-gnome-support
> > > Version: 1.0+dfsg.1-1
> > > Severity: serious
> > > Justification: fails to uninstall properly
> >=20
> > Hmm, are uninstallation bugs considered serious?=20
>=20
> Not sure about that. Please change the severity if you feel I set it too
> high. It certainly did bug me when I could not uninstall the package and
> it prevented me from installing other packages. Maybe I overreacted.=20

I think important would be better.

> > =20
> > >=20
> > > Hi,
> > >=20
> > > I cannot uninstall mozilla-firefox-gnome-support:
> > >=20
> > > Removing mozilla-firefox-gnome-support ...
> > > Updating mozilla-firefox chrome registry...E:
> > > /usr/lib/mozilla-firefox/extensions/installed-extensions.txt still
> > > present. Registration might have gone wrong.
> > > mv: cannot stat `/usr/lib/mozilla-firefox/defaults.ini': No such file=
 or
> > > directory
> > > dpkg: error processing mozilla-firefox-gnome-support (--remove):
> > > subprocess post-removal script returned error exit status 1
> > > Errors were encountered while processing:
> > > mozilla-firefox-gnome-support
> > > E: Sub-process /usr/bin/dpkg returned an error code (1)
> >=20
> > Did mozilla-firefox install cleanly?=20
>=20
> I'm not sure about that. I upgraded firefox to the latest
> release a couple of hours ago, and can no longer reproduce the bug.
> Maybe this was caused by some version difference due to autobuilder lag
> (it happened on an alpha box).=20
>=20
> Well... I'm sorry I can't bring more help. Maybe the best course of
> action would be closing the bug report, if you think the maintainer
> scripts for mozilla-firefox-gnome-support are correctly handling the
> case where /usr/lib/mozilla-firefox/defaults.ini is not there.=20
>=20
> Thanks for your patience. And I hope you'll have a nice new year's eve
> celebration. :-)

Well, actually I think the postrm scripts shouldn't die if
update-mozilla-firefox-chrome fails, so I will fix that in the next
release. Thanks.

--=20
Eric Dorland <email address hidden>
ICQ: #61138586, Jabber: <email address hidden>
1024D/16D970C6 097C 4861 9934 27A0 8E1C 2B0A 61E9 8ECF 16D9 70C6

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d- s++: a-- C+++ UL+++ P++ L++ E++ W++ N+ o K- w+=20
O? M++ V-- PS+ PE Y+ PGP++ t++ 5++ X+ R tv++ b+++ DI+ D+=20
G e h! r- y+=20
------END GEEK CODE BLOCK------

--rJ8inJ6ig7iY3YX9
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFB1LCtYemOzxbZcMYRAgxSAKCEJn80yp7lloX3J2auyBTiAeZzYQCgjfmQ
5FrfA2m7MPm+nZLv1osFxEQ=
=DGqd
-----END PGP SIGNATURE-----

--rJ8inJ6ig7iY3YX9--