On Wed, 24 Feb 2010 03:54:47 -0500 (EST), Kamil wrote: > Yay, forget about my previous post, I got it wrong. I had to try it > myself to understand it. Now I get it - not only repoclosure checks > just the newest packages for broken dependencies, also those *dependant > packages* (the targets) must be amongst the newest ones. I wonder if > it is intentional or not. It is intentional, because an ordinary Yum update/install tries to pick the newest packages, too. A broken dep with only the newest packages is still a broken dep. Users may be keeping and running older kernels, but they would not be able to install the newest one, if that one suffered from broken deps. Repoclosure does not and cannot simulate Yum's "installonly_limit" setting for kernel packages. Extras' repoclosure allows old kernel dependencies, but that is old cruft related to various kernel module add-on packages and late/slow rebuilds. As it also ignores kmod related broken deps in its report script since that feature was added, maybe it's time to revisit the kernel dep filter and drop it. > > > > > > > > Should the test case [1] always use --newest since that seems to > > > more > > > closely mirror yum behavior during installation? > > > > Well, yum is able to work around this problem, isn't it? It should just > select an older kernel for installation. I tried to simulate it on my > F12 machine by adding a repo, but I failed to be completely sure. repoclosure -n ought to be the default. At least for Fedora. Allowing for older packages to resolve dependencies is sort of trying to simulate Yum's --skip-broken, which is against the purpose of a depchecker. -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
