On Fri, 2008-02-08 at 21:15 +0100, Hans-Peter Jansen wrote: > Hi Seth, > > Am Freitag, 8. Februar 2008 schrieb seth vidal: > > On Fri, 2008-02-08 at 10:42 +0100, Hans-Peter Jansen wrote: > > > With pleasure from my side, but probably not from yours, since they're > > > a mess... Attached. > > > > okay, I see the exclude containing kernel-* in update.repo. > > > > Can you try a couple of things for me: > > With pleasure. > > > 1. make the line that was the exclude read: > > exclude=opal* pwlib* wine python-qt* samba-vscan kernel* > > > > so that is removing the - following kernel > > I should have mentioned, that I had it like this primary, similar to the > other ex. The version containing the dash was the second try already. > Tried it again, with no behavioral changes. > > > 2. if that doesn't work - take off the *. I want to figure out which > > piece is failing in the matching routine. > > Now I made it read like this: > exclude=opal* pwlib* wine python-qt* samba-vscan kernel-bigsmp kernel-source > kernel-syms > > I.e. with the exact matches, but again, no behavioral change. > > Now I excluded a package ready to update from a different repo, that > matched as expected, even with wildcards. > > Looks like one of the exactarchlist, installonlypkgs or kernelpkgnames > options is responsible for this issue. > > While my SUSE package contains a patch from Christoph Thiel, I reverted > it temporarily to be sure, it's not the culprit:
rpm shouldn't have anything to do with this. rpm's pattern matching isn't at play when we are excluding packages. We exclude from the available repos, not from the rpmdb. I just tested this on 3.2.11 with excludes of: exclude=kernel* in my updates and fedora repo files - no problem on either. could you post a yum -d 5 output of this: yum -d 5 list available kern\* thanks -sv _______________________________________________ Yum-devel mailing list [email protected] https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
