Bug#474964: Handling bugs properly (Was: Bug#474964: ...)
- To: 474964@bugs.debian.org
- Cc: Debian Developers <debian-devel@lists.debian.org>
- Subject: Bug#474964: Handling bugs properly (Was: Bug#474964: ...)
- From: Andreas Tille <tillea@rki.de>
- Date: Fri, 18 Apr 2008 21:33:52 +0200 (CEST)
- Message-id: <alpine.DEB.1.10.0804182124250.20238@wr-linux02>
- Reply-to: Andreas Tille <tillea@rki.de>, 474964@bugs.debian.org
- In-reply-to: <20080418183827.GF15974@think.homenet>
- References: <20080409075948.GA25419@stro.at> <20080408080216.11267.94047.reportbug@wr-linux02> <handler.474964.D474964.120772806012626.notifdone@bugs.debian.org> <alpine.DEB.1.10.0804181412130.11061@wr-linux02> <20080418183827.GF15974@think.homenet>
On Fri, 18 Apr 2008, Andrei Popescu wrote:
If anybody would confirm that this problem might belong to module-init-tools
I would volunteer to take over the job of proper reassignment - but I
just don't know exactly and "my experts in questions like this" just
refuse proper communication.
See #407256
Hmmm, this is interesting. The bug report says:
It's a kernel bug which affects module-init-tool
so I think the problem seems to be assigned to the right package.
Moreover it says:
we may work around it in udev since the upstream kernel maintainer
refuses to implement a proper fix
If there is a workaround in udev I think this bug can be closed (or
at least decreased in severity to minor/7wishlist) if there is a proper
documentation (for instance in README.Debian, i wonder if such a problem
qualifies for NEWS.Debian?) of the problem and what to do to circumvent
the problem. Moreover I wonder whether this documentation should be
put into linux-image packages or rather module-init-tools which is finally
affected. What do you think? I'd volunteer to write the things down
but beeing no expert in these kernel internas myself, I would like to
hear your opinion what you regard as the best way to provide the
relevant information to the user.
Kind regards
Andreas.
--
http://fam-tille.de
Reply to: