Description of problem: As of Linux 2.6.30, the kernel can be compressed with a few different compression methods. One of them is LZMA, which gives very good compression ratios. Unfortunately, the RHEL-5 distribution lacks an LZMA library, so RHEL-5 cannot decompress these kernels. This is important because the RHEL-5 Xen tools need to be able to decompress these kernels to boot paravirtualized guests. See also BZ 517049. To satisfy this request, we should pull the xz package from EPEL into RHEL-5.5.
*** Bug 522532 has been marked as a duplicate of this bug. ***
Adding Jindrich Novy as the RHEL5 owner
Please provide QA ack. XZ is ready to be built.
xz-4.999.9-0.1.beta.20091007git is now imported in the newly created RHEL5 branch.
Excellent, thanks! Now we just need to get it into a tree compose, and we should be good to go for Xen. Thanks again, Chris Lalancette
It is needed to add xz to approved components. Otherwise I'm unable to file erratum.
Errata tool still claims: Idsfixed Component xz for 519122 is not on the approved components list. even though xz is now listed in: http://intranet.corp.redhat.com/ic/intranet/RHEL5U5ApprovedPackages.html Something is really broken here.
Note, the xz package is currently in EPEL-5 at NVR, xz-4.999.9-0.1.beta.20091007git.el5 . If you want to make sure that the RHEL-5 package replaces that, please bump the release ( for instance, to xz-4.999.9-0.2.beta.20091007git.el5 ). Also, when you know the package is going in, please let the el-5 maintainer (that's me) or the epel mailing list (http://www.redhat.com/mailman/listinfo/epel-devel-list) know so we can block the package from further updates there. Thanks!
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2010-0189.html
This bug was closed during 5.5 development and it's being removed from the internal tracking bugs (which are now for 5.6).