On Tue, 22 Feb 2005, Tom 'spot' Callaway wrote:
On Tue, 2005-02-22 at 08:34 +0100, Thorsten Leemhuis wrote:
Case 4.1: What if kernel-module-unionfs-2.6.10_4_FC3-1 is released one/two days behind kernel-2.6.10-3_FC3? This can happen due to build errors that first need to get fixed. Or the build system or all that have access are sleeping. Or simply due due mirroring "problems" when core/updates/ is already mirrored, but extras/ not yet.
That's a valid point, since the kernel package doesn't depend on kernel-module-*. Anyone have any idea how to work around this in a sane manner?
The current apt implementation of the kernel-module handling prints out warnings if you have kernel modules installed which are not available for the new kernel you're about to install by doing some "fun" calculations with provides and versions. Alternatively it could hold back from installing the new kernel until all the modules are available for the new kernel as well.
So, it's possible (at least in the current uname-in-package-name scheme) but fun it is not.
- Panu -
