preventing md5 mismatch errors from compression changes

Toshio Kuratomi a.badger at
Sun Nov 21 19:10:30 UTC 2010

On Sun, Nov 21, 2010 at 05:41:35PM +0000, Andre Robatino wrote:
> The recent change in xz compression settings caused md5 mismatch errors in
> rebuilding RPMs (since applydeltarpm doesn't know the difference between the old
> and new compression). This resulted in significant work for releng. To avoid
> this issue in the future, what about using different names and packages for the
> different compression types (i.e., xz1, xz2, etc.) so they can be installed
> simultaneously and identified properly? The xz packages are small, and using
> separate packages should hopefully mean little to no extra work for the
> maintainer. The same method could be used in the future for any new compression
> type that replaces xz.
This could require different naames for the library too which will get a bit
harder than just the binary name.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
Url : 

More information about the devel mailing list