On Sat, Aug 23, 2003 at 01:23:09PM +0300, Axel Thimm wrote: > On Sat, Aug 23, 2003 at 11:01:03AM +0200, Ragnar Kj?rstad wrote: > > This caused yum to just give up: > > Resolving dependencies > > ..package alsa-kmdl-2.4.20-19.23.rh9.at needs /boot/vmlinux-2.4.20-19.23.rh9.at (not provided) > > package nvidia-graphics-kmdl-2.4.20-19.23.rh9.at needs /boot/vmlinux-2.4.20-19.23.rh9.at (not provided) > > It looks like you have at-testing, but not at-stable in your yum.conf. > > The at-* stability series are cumulative and disjunct, i.e. if you use > at-testing, you need at-good and at-stable as well. That's why yum > cannot resolve the dependencies. I have both at-good and at-stable in my yum-configuration-file: [at-stable] name=Red Hat Linux 9 ATrpms stable baseurl=http://apt.physik.fu-berlin.de/redhat/9/en/i386/at-stable [at-good] name=Red Hat Linux 9 ATrpms good baseurl=http://apt.physik.fu-berlin.de/redhat/9/en/i386/at-good [at-testing] name=Red Hat Linux 9 ATrpms testing baseurl=http://apt.physik.fu-berlin.de/redhat/9/en/i386/at-testing > One of these days I will make lower stability classes include all > higher ones (e.g. at-testing will already include at-stable and > at-good) so that one doesn't need to define multiple repos in yum for > atrpms. The reason these exist is historic, because under apt these > were (are) sections and can be written in one line. Personally I find the current setup to be just fine. Also, a typical installation will still have multiple repositories, e.g. one for OS, one for local packages and perhaps some for application- specific repositories. In other words, a repository may very well have dependencies on packages outside it's repository. > I don't mind yum giving up when it discovers flaws in the repos or > their setup, otherwise one would never find bugs like this one. I don't know exactly what this bug is; except that it yum upgrade still fails, and yum list *kernel* doesn't list any packages from your repositories. Now, that aside, it's certainly nice to have your security-updates even if one of your low priority repositories happen to be "broken". (Not sure that a repository with packages with unmet dependencies are neccessarily broken, but that's another question). I agree it's important to catch errors in the repositories though. Possible ways to do this would be to issue a warning instead of a fatal error, having an option to do partial upgrade on such errors, or to try and catch the problem when building the repository (but then I guess yum-arch would need to know what repositories (if any) this one builds on top of). -- Ragnar Kj?rstad
