On Thu, 2006-01-12 at 08:16 +0100, Thorsten Leemhuis wrote: > Am Mittwoch, den 11.01.2006, 13:59 -0500 schrieb Jack Neely: > > > The newer userland-package probably won't work with the old > > > kernel-version anyway. But the question is correct: how do we solve > > > this? IMHO the plugin should uninstall older kernel-modules. Or should a > > > package "kmod-foo-1.2-1.2.6.14-1.1776_FC4" simply have a > > > Obsolets: kmod-foo < 1.2 > > > Would yum in this case uninstall the older versions during update > > > (normally kmod-packages are installed and not updated, but in this case > > > we want it to update)? > > > In practice I have the kernel module require the userland package but > > not a specific version. > > > > Requires: openafs > > > > The justification is that there will not be multiple copies of the > > userland tools installed and that package will require the kmod of a > > specific version: > > > > Requires: kmod-openafs = 1.4.0 > > Okay. Welcome to our Theater. Main actor: User foo. .. > User foo looks frustrated and begins to debug [...] Now, the main character might want improvise on "inaccessible filesystems", "non-bootable systems" or "garbled X" ;) > End of scene 1. > > Don't know if the part "openafs won't work, because the older openafs > userland package doesn't work with the new version of the kmod" is true > for openafs, but it is for a lot of kernel-modules I know. So no, this > doesn't work afaics. I realize, the scripts' author has understood the scenario - Congrats! Ralf -- fedora-extras-list mailing list fedora-extras-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-extras-list
