On 08/19/2009 07:10 PM, Jesse Keating wrote: > > > On Aug 19, 2009, at 18:36, Toshio Kuratomi <a.badger@xxxxxxxxx> wrote: > >> A data corruption bug was found in the current xz package for certain >> files. The xz package was updated to a snapshot in Fedora and EPEL. >> We'd like to update the builders with the new xz to make sure we aren't >> producing packages with corrupted payloads. >> >> The corruption bug report is here: >> https://bugzilla.redhat.com/show_bug.cgi?id=517806 >> >> which includes confirmation that it fixes the bug and jnovy's >> recommendation to update the buildsystem. >> >> The EPEL-5 update is here: >> >> https://admin.fedoraproject.org/updates/xz-4.999.8-0.10.beta.20090817git.el5 >> >> >> Can I get two +1's for this? >> > > The host xz wouldn't be used to produce any rpms, the rpm inside the > chroot would. Does this come into play when initing the buildroot? > You're right, this wouldn't come into play unless it's a decompression bug. And if that's so it would generate an error from the buildsystem while trying to create the buildroot instead of a corrupted payload in the built rpms. So not as severe. I'm checking to be sure it isn't a decompression bug now. -Toshio
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
