createrepo_c doesn't seem to cover this scenario well too. It even sometimes hangs forever; strace output is: futex(0xdb5fb0, FUTEX_WAKE_PRIVATE, 1C_CREATEREPOLIB: Warning: read_header: Fopen of ./<nvr>.x86_64.rpm failed No such file or directory Warning: Cannot read package: ./<nvr>.x86_64.rpm ) = 1 write(1, "Pool started (with 5 workers)\n", 30Pool started (with 5 workers) ) = 30 futex(0xdb6024, FUTEX_WAIT_PRIVATE, 1, NULL) = 0 futex(0xdb5fb0, FUTEX_WAKE_PRIVATE, 1) = 0 futex(0xdb6024, FUTEX_WAIT_PRIVATE, 3, NULL +++ This bug was initially created as a clone of Bug #1022001 +++ Package version: createrepo-0.10-1.fc21.noarch How to reproduce: 1) create a file list with existing packages 2) append a line with package that does not exist 3) run $ createrepo -i <package-list> . zegrep '<package |packages=' repodata/*primary*xml* <metadata xmlns="http://linux.duke.edu/metadata/common" xmlns:rpm="http://linux.duke.edu/metadata/rpm" packages="3"> <package type="rpm"> <package type="rpm"> Header says 3 packages while there are just 2 of them in metadata.
Fixing this is not going to be simple, as we write the package count to XML header first, then append <package> elements. And it's gz-compressed, so back-patching the right number is not possible. To fix this, we need to add a 2nd pass (probably conditional, run on failures only). Pretty ugly IMO, but it should fix this, and not make createrepo much slower in the common case where the package count does not change.
Note about the hang: I've tried to reproduce the issue with no success. After Dan had updated its createrepo_c to the 0.2.1 version, the problem disappeared. So the "hang part" of this bug is considered as solved.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.