After ugprading to yum-3.4.3-102.fc19.noarch Koji builds fail with "DEBUG util.py:264: Existing lock /var/run/yum.pid: another copy is running as pid 6384."
There was only one change in 3.4.3-102, and it involves metadata handling, not locking. Can you double check that this was not caused by yum-utils upgrade instead? Repoquery locking code was added in yum-utils-1.1.31-15.fc19, so this is likely causing this- see BZ 985681.
(In reply to Zdeněk Pavlas from comment #1) > There was only one change in 3.4.3-102, and it involves metadata handling, > not locking. Can you double check that this was not caused by yum-utils > upgrade instead? > > Repoquery locking code was added in yum-utils-1.1.31-15.fc19, so this is > likely causing this- see BZ 985681. Ok, I'll give it a shot, but from my yum.log, I haven't upgraded yum-utils in a while: Feb 27 11:53:43 Updated: yum-utils-1.1.31-10.fc18.noarch After reading BZ 985681, though, it seems like that is the issue. I'm not sure why I haven't seen this until after this mornings updates: Jul 24 08:42:46 Updated: kmod-libs-14-1.fc19.x86_64 Jul 24 08:42:46 Updated: kmod-14-1.fc19.x86_64 Jul 24 08:42:46 Updated: 2:vim-filesystem-7.3.1314-1.fc19.x86_64 Jul 24 08:42:48 Updated: 2:vim-common-7.3.1314-1.fc19.x86_64 Jul 24 08:42:48 Updated: 2:vim-enhanced-7.3.1314-1.fc19.x86_64 Jul 24 08:42:48 Updated: 1:autofs-5.0.7-28.fc19.x86_64 Jul 24 08:42:49 Updated: perl-PathTools-3.40-3.fc19.x86_64 Jul 24 08:42:49 Updated: 2:vim-minimal-7.3.1314-1.fc19.x86_64 Jul 24 08:42:49 Updated: libsoup-2.42.2-2.fc19.x86_64 Jul 24 08:42:49 Updated: ppp-2.4.5-30.fc19.x86_64 Jul 24 08:42:49 Updated: qpdf-libs-5.0.0-1.fc19.x86_64 Jul 24 08:42:49 Updated: wget-1.14-8.fc19.x86_64 Jul 24 08:42:49 Updated: yum-3.4.3-102.fc19.noarch Can you close this one then as related to BZ 985681?
Closing as per comment 2 *** This bug has been marked as a duplicate of bug 985681 ***
> I'm not sure why I haven't seen this until after this mornings updates More than one instance of repoquery must run simulatenously, so it probably needs some time to trigger this.