On Sat, Mar 31, 2012 at 05:53:59PM -0400, Mike Miller wrote: > On Mon, Mar 5, 2012 at 4:20 PM, Joey Hess <jo...@debian.org> wrote: > > Andreas Henriksson wrote: > >> I've not found any particular options used, but they might be hiding in > >> the details in any of the wrapping layers. > > > > Seems it must be down to the options. It's not unheard of for language > > bindings to compressors to faff around with overriding some of the > > default options. We had a similar problem with perl's gzip library, > > which set a memLevel zlib parameter to a nonstandard value. > > Hi there, I got annoyed by this one today, dug into the python > library, and found the difference. Command-line xz defaults to crc64, > python defaults to crc32. The attached patch works for me running > pristine-xz on a variety of downloaded gnome tar.xz files. > > I just added crc32 for each compression level so it doubles the total > number of checks you run through in the worst case, but "-6 > --check=crc32" is the right one for these python-generated tarballs > and it's only the second one tested. Optimize as desired.
Reposting again with the correct MIME type on the attached patch this time, sorry about that. -- mike
From 27ed91981f877d79d86b6be837ca0cfccbf0ab9a Mon Sep 17 00:00:00 2001
From: Mike Miller <mtmil...@ieee.org>
Date: Sat, 31 Mar 2012 17:50:41 -0400
Subject: [PATCH] Add cases to handle CRC32 files made with PylibLZMA
Signed-off-by: Mike Miller <mtmil...@ieee.org>
---
pristine-xz | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/pristine-xz b/pristine-xz
index 0c2f9d4..87be90a 100755
--- a/pristine-xz
+++ b/pristine-xz
@@ -126,6 +126,7 @@ sub predictxzargs {
my @args;
foreach my $level (@$possible_levels) {
push @args, ["-z", "-$level"];
+ push @args, ["-z", "-$level", "--check=crc32"];
}
return @args;
}
--
1.7.9.1
signature.asc
Description: Digital signature
