Nick <oinksocket@xxxxxxxxxxxxxxx> writes: > Hello, > > I'm a relatively new user of CentOS 5.5. The CentOS wiki advises the use of yum > priorities if you use more than the base repositories, specifically with RPMForge: > > http://wiki.centos.org/AdditionalResources/Repositories/RPMForge > > (I have yum-3.2.22-26.el5.centos and yum-priorities-1.1.16-14.el5.centos.1) > > As I gather has been stated before on the centos list [1], it also implies that > yum-priorities isn't a great solution (quoting Seth Vidal), but stops > short of outlining what exactly is wrong with yum-priorities (YP) and why it's > still recommended. In fact it goes on to say: > >> as of yet, no real world problems have been reported with regard to the >> 'yum-priorities' plugin > > So, I experienced a real-world problem (more details in [2]): > > - set CentOS base with priority 1 > - set RPMForge with priority 2 > - yum check-update was ok > - yum update seemed ok, prompted to proceed, then aborted half way. > > It aborted because of an unresolvable dependency from an RPMForge package, where > the package which satisfies it hidden by an older version in the base repo. Personally I recommend not using rpmforge, and instead just using repositories that don't require yum-priorities to make sure your system isn't corrupted by accident. > Firtly, the fact that yum+YP hides packages so completely they don't seem to be > present can be confusing, and it'd be nice if that could be fixed so that > --showduplicates will report the presence of packages which won't be installed > because of YP. We noticed this was a problem (excludes can't be seen), and one solution we came up with is to show something is being excluded in "repolist". Eg. % yum repolist | fgrep chrom fedora-chromium Chromium web browser and deps 6 % yum repolist -x v8 | fgrep chrom fedora-chromium Chromium web browser and deps 5+1 ...the idea being that whenever people had dep. install problems we always asked to see their repolist. If you want to play with a newer yum, you can try: http://repos.fedorapeople.org/repos/james/yum-rawhide/ ...but somehow dripping all excludes when --showduplicates is set would be pretty weird, and it's non-trivial to get the package names after they've been excluded (which is another reason repolist was done, as finding out how many things are excluded is much easier). > However, the bigger problem is that yum does *not* seem to be able to detect the > kind of unresolvable dependency problem I experienced. Therefore it happily > starts the update process, only to abort with an error half way through, leaving > my system essentially broken. Neither does yum check-update warn me about this > risk. I'm pretty sure this isn't true, there are roughly 6 stages for an install/update: 1. Processing the argument. 2. Internally resolving dependencies. 3. Show what will happen to the user, and asking for confirmation. 4. Asking rpm to check that everything is fine (test transaction). 5. Asking rpm to run the transaction. 6. Running post transaction stuff. ...I'm pretty sure yum is stopping at #2 for you, which is fine. -- James Antill -- james@xxxxxxxxxxxxxxxxx http://yum.baseurl.org/wiki/releases http://yum.baseurl.org/wiki/whatsnew/3.2.28 http://yum.baseurl.org/wiki/YumMultipleMachineCaching _______________________________________________ Yum mailing list Yum@xxxxxxxxxxxxxxxxx http://lists.baseurl.org/mailman/listinfo/yum
