[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#400408: marked as done (Modules in different udebs depending on the same module == problem)

Your message dated Mon, 27 Nov 2006 14:51:11 -0500
with message-id <20061127195111.GA28291@kitenet.net>
and subject line Bug#400408: Modules in different udebs depending on the same module == problem
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: kernel-wedge
Version: 2.29
Severity: normal

Hi,

I've recently encountered a situation in which both SCSI module and a 
NIC module depend on firmware_class.ko (on sparc). Since they go into 
different udebs, kernel-wedge complains about duplicate modules in 
udebs. Looks like we need something like common-modules udeb for 
situation like this. Or is there some existing workaround?

Best regards,
-- 
Jurij Smakov                                           jurij@wooyd.org
Key: http://www.wooyd.org/pgpkey/                      KeyID: C99E03CC

--- End Message ---
--- Begin Message --- 
Jurij Smakov wrote:
> I've recently encountered a situation in which both SCSI module and a 
> NIC module depend on firmware_class.ko (on sparc). Since they go into 
> different udebs, kernel-wedge complains about duplicate modules in 
> udebs. Looks like we need something like common-modules udeb for 
> situation like this. Or is there some existing workaround?

This is already handled by the firmware-modules udeb, which is defined
by kernel-wedge. You only need to enable it.

In general, the case of modules in 2 different udebs depending on a
common module is indeed a problem, and it's the kind of problem that has
to be solved manually, generally by factoring that module out into a
package like firmware-modules. If kernel-wedge did not check for this,
we'd get kernel modules duplicated in different udebs, which would be at
best ineficient. So I consider this behavior of kernel-wedge to be an
important feature, not a bug.

-- 
see shy jo

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: