Am Sonntag, 10. Februar 2008 schrieb James Antill: > On Sun, 2008-02-10 at 00:16 +0100, Hans-Peter Jansen wrote: > > Am Samstag, 9. Februar 2008 schrieb James Antill: > > > On Sat, 2008-02-09 at 11:04 +0100, Hans-Peter Jansen wrote: > > > > Excluding > > > > kernel-source-2.6.18.8-0.8.i586 5191 > > > > 7aabedcf89d99680cc7d53de0efa1f549d91e050 0x93d0fec> > > > > > > [...] > > > > > > > PKG kernel-source-2.6.18.8-0.8.i586 5198 > > > > 7aabedcf89d99680cc7d53de0efa1f549d91e050 0x93de0ec > > > > > > Ok, you have two pkgKey's, with the same pkgId, of > > > kernel-source-2.6.18.8-0.8.i586 package[1]. > > > > You mean 0x93d0fec and 0x93de0ec? > > No, the pkgKey's are 5191 for the excluded one and 5198 for the second > one. The pkgId's are the same (the big hex number). > > > Hmm, I do recreate the repodata locally, because my home baked repo > > sync excludes packages in some fancy ways in order to not waste my > > pretty limited bandwidth. Consequently I need to recreate the metadata. > > [...] > > > There's the fastest yum waiting around the corner, and I cannot make > > real use of it :-(. > > So I can recreate your problem by having the same rpm in two different > directories, and then "createrepo .". Excludes only removes one of them > from that point. So my guess is that you also have two copies of the > kernel rpms (say in i586 and x86_64 directories)?
Yep, that's the culprit. For whatever reason, SUSE creates symlinks for every updated package out there (since ages). I'm able to exclude these symlinks from my local repos, but this will probably fail with the official repos (and it's a bit unintuitive, that excludes may fail under these conditions..). Generally ignoring symlinks in createrepo (by option) isn't that brilliant either, since I do use them also myself in a few places (with low propability to interfere with exclude items, though). The whole issue is complicated by SUSE's delta.rpm packages, which, if forgotten to exclude them on the createrepo run, adds another source of similar packages, and further contribute to the problem (as happened here with my tests.. :-(). > If so the short term solution would be to just delete one of them. If > there's another reason they are being listed twice, we'll probably have > a fix you can try soon. Good to know. Since the repos are created in such a way since a long time, I think, it's better to fix this problem in yum itself, but as it stands, your right, createrepo should better have handled this case properly. Pete _______________________________________________ Yum-devel mailing list [email protected] https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
