On Sat, Jan 29, 2005 at 05:08:42PM -0500, Trey Sizemore wrote: > On Sat, 2005-01-29 at 22:58 +0100, Axel Thimm wrote: > > On Sat, Jan 29, 2005 at 04:49:48PM -0500, Trey Sizemore wrote: > > > I have the following repositories setup for yum, and I'm getting package > > > conflicts during updates due to version mismatches: > > > > > > atrpms > > > atrpms-bleeding > > > atrpms-testing > > > dag > > > dries > > > flash > > > freshrpms > > > jpackage-fedora > > > jpackage-generic > > > kde-redhat > > > kde-redhat-all > > > newrpms > > > > > > Are there repositories listed above which are known to conflict? > > > > No, the repos should be fine (but you are living a bit dangerously > > activating testing and bleeding repos). > > > > But there is a bug in yum that is triggered by some of the repos most > > notably ATrpms: > > > > https://www.redhat.com/archives/fedora-list/2005-January/msg01826.html > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=144376 > > http://bugzilla.atrpms.net/show_bug.cgi?id=289 > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=140832 > > > > The bugs seems to have been fixed in yum's CVS, but there hasn't been > > as yum release since. You can either use a CVS yum package from ATrpms: > > > > http://atrpms.net/name/yum-bleeding/ > > > > or use anyother resolver like apt or smart: > > > > http://atrpms.net/name/apt/ > > http://atrpms.net/name/smart/ > > Thanks. As an example when attempting to update gtk2 and gtk2-devel, a > number of dependencies are listed for me, among them: > > qt.i386 1:3.3.3-16.3.3.kde > qt.i386 1:3.3.3-16_5.rhfc3.at > > which will cause a conflict. So it's the atrpms conflicting with either > kde-redhat or kde-redhat-all it seems in this case. No, it's the bug above. yum <= 2.1.12 collects multiple packages during calculation of dependencies, including old ones. -- Axel.Thimm at ATrpms.net
Attachment:
pgpxxlu5nB9pM.pgp
Description: PGP signature
