Description of problem: When I try to add an already compressed metadata file, the file decompressed firstly, and then added, but the compression suffix persist, so it is super confusing. --no-compress option doesn't help. Version-Release number of selected component (if applicable): Name : createrepo Version : 0.9.9 Release : 21.fc19 How reproducible: always Steps to Reproduce: modifyrepo --no-compress foobar.xml.gz rpms_sss/repodata Actual results: Decompressed foobar.xml is added with the original filename foobar.xml.gz Expected results: Something more sane. E.g. File is only copied and keeps its original name foobar.xml.gz (no decompression is done).
Yep, modifyrepo is pretty buggy.. Fixed this also with other bugs: - when the input file was compressed, it was transparently decompressed, but then the selected compression was not applied at all. - open-size and open-checksum were calculated from the original compressed file.
createrepo-0.9.9-23.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/createrepo-0.9.9-23.fc19
Package createrepo-0.9.9-23.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing createrepo-0.9.9-23.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-18128/createrepo-0.9.9-23.fc19 then log in and leave karma (feedback).
createrepo-0.10-0.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/createrepo-0.10-0.fc19
createrepo-0.10-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/createrepo-0.10-1.fc19
createrepo-0.10-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.