Description of problem: This happens only on certain repos.. so I guess there is something in one of the packages requires that causes this like an empty string? I think skvidal already has a patch for this CreateRepoError: Worker 0: Traceback (most recent call last): Worker 0: File "/usr/share/createrepo/worker.py", line 101, in <module> Worker 0: main(sys.argv[1:]) Worker 0: File "/usr/share/createrepo/worker.py", line 84, in main Worker 0: pri.write(pkg.xml_dump_primary_metadata()) Worker 0: File "/usr/lib/python2.7/site-packages/yum/packages.py", line 1208, in xml_dump_primary_metadata Worker 0: msg += misc.to_unicode(self._dump_format_items()) Worker 0: File "/usr/lib/python2.7/site-packages/yum/packages.py", line 1076, in _dump_format_items Worker 0: msg += self._dump_requires() Worker 0: File "/usr/lib/python2.7/site-packages/yum/packages.py", line 1145, in _dump_requires Worker 0: best = rest.pop() Worker 0: IndexError: pop from empty list Worker exited with non-zero value: 1. Fatal. Worker exited with non-zero value: 1. Fatal. Spawning worker 0 with 3381 pkgs Version-Release number of selected component (if applicable): 0.9.9-3
yeh, it's the libc consolidate code ... it's fixed upstream.
*** Bug 715105 has been marked as a duplicate of this bug. ***
createrepo still crashes: Spawning worker 0 with 1576 pkgs Worker 0: Traceback (most recent call last): Worker 0: File "/usr/share/createrepo/worker.py", line 101, in <module> Worker 0: main(sys.argv[1:]) Worker 0: File "/usr/share/createrepo/worker.py", line 84, in main Worker 0: pri.write(pkg.xml_dump_primary_metadata()) Worker 0: File "/usr/lib/python2.7/site-packages/yum/packages.py", line 1208, in xml_dump_primary_metadata Worker 0: msg += misc.to_unicode(self._dump_format_items()) Worker 0: File "/usr/lib/python2.7/site-packages/yum/packages.py", line 1076, in _dump_format_items Worker 0: msg += self._dump_requires() Worker 0: File "/usr/lib/python2.7/site-packages/yum/packages.py", line 1145, in _dump_requires Worker 0: best = rest.pop() Worker 0: IndexError: pop from empty list Worker exited with non-zero value: 1. Fatal. Traceback (most recent call last): File "/usr/bin/pungi", line 214, in <module> main() File "/usr/bin/pungi", line 116, in main mypungi.doCreaterepo() File "/usr/lib/python2.7/site-packages/pypungi/__init__.py", line 759, in doCreaterepo self._makeMetadata(self.topdir, cachedir, compsfile, repoview=True, repoviewtitle=repoviewtitle) File "/usr/lib/python2.7/site-packages/pypungi/__init__.py", line 716, in _makeMetadata repomatic.doPkgMetadata() File "/usr/lib/python2.7/site-packages/createrepo/__init__.py", line 395, in doPkgMetadata self.writeMetadataDocs(packages) File "/usr/lib/python2.7/site-packages/createrepo/__init__.py", line 667, in writeMetadataDocs raise MDError, msg createrepo.utils.MDError: Worker exited with non-zero value: 1. Fatal.
This should be fixed in the latest yum for Fed-15. *** This bug has been marked as a duplicate of bug 701744 ***
the bug occurs with latest yum 3.2.29-6, occurrence/being able to reproduce depends entirely on packages in the repo. this bug still exists and is not fixed. 100% reproducible
*** Bug 720495 has been marked as a duplicate of this bug. ***
Sorry, I thought this was the same as the other bug ... but it's a little different.
This should fix it: http://koji.fedoraproject.org/koji/taskinfo?taskID=3191578
yum-3.2.29-7.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/yum-3.2.29-7.fc15
Package yum-3.2.29-7.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing yum-3.2.29-7.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/yum-3.2.29-7.fc15 then log in and leave karma (feedback).
the issue was resolved in yum-3.2.29-7.fc15.noarch.rpm, thank you
yum-3.2.29-7.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 709698 has been marked as a duplicate of this bug. ***