RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem: When running createrepo --compress-type=xz not all resulting compressed metadata is compressed with xz.


Version-Release number of selected component (if applicable):createrepo-0.9.9-23.el7


How reproducible:100%


Steps to Reproduce:
1.createrepo --compress-type=xz .
2.ls repodata/*.gz
3.files are present

Actual results:
some files are created with gzip compression

Expected results:
xz compression used for all files

Additional info:
__init__.py from createrepo has a 'FIXME' relating to y-m-p in the relevant code

While I was testing bug 874682 I did a note to the test that preserving gz format for primary metadata with --compress-type=xz was intentional but I cannot find the reason for that... 

James or Valentina, 
do you know why? Maybe we thought it could be risky for RHEL-6 since pyliblzma is not present in RHEL6.

http://createrepo.baseurl.org/gitweb?p=createrepo.git;a=blob;f=createrepo/__init__.py;h=517ea04764ebccd351f54bd5432c95b5d2a3f1b6;hb=HEAD#l450

Closest I've got for reasoning, but this doesn't truly clear your needinfo

(In reply to Karel Srot from comment #3)
> do you know why? Maybe we thought it could be risky for RHEL-6 since
> pyliblzma is not present in RHEL6.

It was simpler than that, at the time we passed the downloaded .xml files directly to yum-metadata-parser. And that used gzopen() if the file ended in .gz or open() otherwise.

Between el6 => el7 we changed yum so it decompresses the .xml files itself, and passes the result to yum-metadata-parser, avoiding this problem. So we could fix this in createrepo now.

Acking (fix hinted in comment 5).

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2024