Comment 14 for bug 11923

Message-ID: <email address hidden>
Date: Sun, 2 Jan 2005 21:01:27 +0100
From: Bernhard Reiter <email address hidden>
To: Thomas Hood <email address hidden>, <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#287499: [Pkg-alsa-devel] Bug#287499: alsa-base: causing confusion on systems with
 oss

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

On Thu, Dec 30, 2004 at 10:01:45PM +0100, Thomas Hood wrote:
> I am rating this "minor" because it's a documentation issue, not
> necessarily because I think it's a minor documentation issue. :)

Because it leads to modules not being loaded
and a hard to diagnose situation in other modulues only be upgrading,=20
I would say it is more then "minor" or documentation only:
It breaks real installations and eats up system administrator's time.

> On Tue, 2004-12-28 at 11:27 +0100, Bernhard Reiter wrote:
> > While blacklisting the oss modules in several ways seems to be the right
> > thing to do to avoid strange situations, I suggest that you bring
> > up a warning for system administrators when you install or upgrade alsa=
-base
> > with this blacklisting in place so that they are warned and know what
> > do to (undo the blacklisting in discover, modutils or hotplug)
> > before they start looking into modutils or other packages which they
> > suspect to be broken.
>=20
>=20
> The package description already mentions this issue. I could discuss it
> further in README.Debian I suppose.

On a regular upgrade, people will not inspect README.Debian
or the packages description of a package, this does not ease the problem.

 Bernhard

--ZoaI/ZTpAVc4A5k6
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFB2FMXh9ag3dpKERYRAoNKAJ9xOTsleUZ22sA5wVOr9BHfZ0R0tgCgoMoI
FV56/wzVlp+XQHDIH0AW7sA=
=TAxR
-----END PGP SIGNATURE-----

--ZoaI/ZTpAVc4A5k6--