* Christoph Biedl <debian.a...@manchmal.in-ulm.de> [2023-01-01 18:17]:
> > As I understand it, this is result of how t/fixtures/pyzip/pyzip.in is
> > described by file(1):
> > 
> > - a /usr/bin/python3 script executable (binary data)
> > + Zip archive, with extra data prepended
> 
> Thanks to FC Stegerman, this has been fixed upstream. So this bug now
> belongs into the domain of the file package, and will be fixed in the
> next upload.

Unfortunately, that's not completely correct.  Whilst IMO my patch for
file makes its output "more correct", it's still different from the
output that strip-nondeterminism currently expects:

- a /usr/bin/python3 script executable (binary data)
+ a /usr/bin/python3 script executable (Zip archive)

I've attached a patch for matching both old and new output and opened
a merge request [1] on salsa as well.

- FC

[1] 
https://salsa.debian.org/reproducible-builds/strip-nondeterminism/-/merge_requests/15
diff --git a/lib/File/StripNondeterminism.pm b/lib/File/StripNondeterminism.pm
index fc5451e..338a514 100644
--- a/lib/File/StripNondeterminism.pm
+++ b/lib/File/StripNondeterminism.pm
@@ -111,7 +111,7 @@ sub get_normalizer_for_file($) {
 	}
 
 	# pyzip - check last due to call to file(1)
-	if (_get_file_type($_) =~ m/python3 script executable \(binary data\)/) {
+	if (_get_file_type($_) =~ m/python3 script executable \((Zip archive|binary data)\)/) {
 		my $handler = _handler('pyzip');
 		return $handler
 		  if File::StripNondeterminism::handlers::pyzip::is_pyzip_file($_);

Reply via email to