On Thu, 2008-09-11 at 14:38 -0400, C. Scott Ananian wrote: > From laptop.org bug: http://dev.laptop.org/ticket/8395 > > The OLPC yum configuration uses an excludes= line with a large number > (400 or so) of packages named. (We maintain a stable repository of > packages shipped in our image, but let end-users install packages we > don't ship using the f-9 repository; we exclude the packages we ship > from the f-9 repo to ensure that users don't inadvertently pick up an > incompatible update from f-9.) > > In yum-3.2.17-2.fc9.noarch this worked fine. We recently picked up > yum 3.2.19-3.fc9 as part of the fedora key transition. In 3.2.19, yum > appears to hang. > > Debugging, I found that it works fine if you remove the excludes= > line, but you can reproduce the hang by creating an excludes line of > (say) 1000 entries -- it doesn't matter what they are, I used > 'abcd-1', 'abcd-2', etc since that was easy to generate by script. > > This seems to be a significant performance regression in 3.2.19. > > What in 3.2.19 was actually required for the fedora key transition? > I'd like to fall back to 3.2.17, at least until this regression is > fixed, but it's not clear to me if this will break yum for us due to > GPG key issues. > Can you file a bug on this w/the config/repo files in question? thanks -sv _______________________________________________ Yum mailing list Yum@xxxxxxxxxxxxxxxxxxxx https://lists.dulug.duke.edu/mailman/listinfo/yum
