tags 331391 = confirmed thanks On Thu, Oct 13, 2005 at 12:57:49PM +0200, Sven Luther wrote: > Iti s an sarge -> etch upgrade problem if anything, let's remove them for now, > and once we sorted out the module build issues, we can always readd them fori > etch if really needed.
It'd be convenient if the module building system were to be designed in a way that modules that are not built with the current 'latest' kernel package were to advertise that fact in a very obvious way -- for example, that their dependencies and/or build-dependencies are broken if they are for 2.6.12 while 2.6.13 is in the archive, for example. This would greatly help in detecting what kernel modules in the archive are not uptodate in an automated fashion using pre-existing tools (like debcheck and britney). On Fri, Oct 14, 2005 at 02:56:03PM +0900, Horms wrote: > Jeroen, can you please go and remove the packages as originally > requested? Ok, going ahead now. --Jeroen -- Jeroen van Wolffelaar [EMAIL PROTECTED] http://jeroen.A-Eskwadraat.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
