Bug#271751: diagnosis and severity upgrade for this bug

Joey Hess Joey Hess <joeyh@debian.org>, 271751@bugs.debian.org
Thu, 23 Sep 2004 16:54:54 +0200


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

I've upgraded the severity of this bug to serious because I don't think
we want to release sarge with a desktop task that includes 7 mb of
errors spewed to the screen (and logged). Of course the release managers
have the last word on what is RC.

I figured out the cause of this bug. During a fresh install of the sarge
desktop task, apt happens to configure some packages before
scrollkeeper; scrollkeeper and docbook-xml are unpacked but not
configured at this point, so they have not registered their XML catalogs
yet. When scrollkeeper-update is run by the postinst of some other
package, it defaults to not fetching these from the network (good),
can't find them and thus all the errors. Once scrollkeeper and its
dependencies are configured, the errors stop.

One way to fix this might be to make scrollkeeper-update not be
available in the path (or not do anything) until scrollkeeper is fully
configured.

--=20
see shy jo

--tKW2IUtsqtDRztdT
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)

iD8DBQFBUuO+d8HHehbQuO8RAtQKAKCxTLrPxDvRvCW4WElPbO8gJEBdIQCfY0cn
5Ep4DA+Nw/ZDeJ1R0BXb/uE=
=r3rC
-----END PGP SIGNATURE-----

--tKW2IUtsqtDRztdT--