reprotest is marked for autoremoval from testing

2024-04-15 Thread Debian testing autoremoval watch
reprotest 0.7.27 is marked for autoremoval from testing on 2024-05-14

It (build-)depends on packages with these RC bugs:
1064676: android-platform-tools-apksig: FTBFS: dh_auto_test: error: gradle 
--info --console plain --offline --stacktrace --no-daemon 
--refresh-dependencies --gradle-user-home .gradle -Duser.home=. 
-Duser.name=debian -Ddebian.package=android-platform-tools-apksig 
-Dfile.encoding=UTF-8 --parallel --max-workers=8 test returned exit code 1
 https://bugs.debian.org/1064676
1064708: pygame: FTBFS: AssertionError: "No video mode" does not match 
"Parameter 'surface' is invalid"
 https://bugs.debian.org/1064708



This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl

Autoremoval data is generated by:
https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl

___
Reproducible-builds mailing list
Reproducible-builds@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/reproducible-builds


Bug#1068705: diffoscope crashes on libscout 2.3.2-3 build on unstable but not bullseye

2024-04-15 Thread Fay Stegerman
* Holger Levsen  [2024-04-15 12:13]:
> I've got two remaining questions about libscout (and diffoscope)
>
> On Thu, Apr 11, 2024 at 01:48:18AM +0200, Fay Stegerman wrote:
> > unzip does seem to extract all the files, though it errors out.  Not sure 
> > what
> > diffoscope should do here.  This is definitely a broken ZIP file.  That bug
> > should probably be reported against libscout or whatever tooling it used to
> > create that JAR.
>
> you filed https://github.com/python/cpython/issues/117779
> (thanks again!), am I correct to assume that thus there's no need
> to file a seperate bug against libscout?

It's generating a broken ZIP file with duplicate entries.  It really shouldn't
be doing that, regardless of whether we can extract the files nonetheless.
That's still a bug that should be reported and fixed.

> and 2nd, 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/diffoscope-results/libscout.html
> now as expected displays:
>
> './usr/share/java/libscout.jar' has 35 duplicate entries
> './usr/share/java/libscout.jar' has 35 duplicate entries
>
> (which is nice, though maybe could only been shown once?)

Ah.  It correctly shows that twice as there could be differences between the two
files being compared wrt whether they have duplicate entries (and if so how
many).

And if you run 'diffoscope foo.zip bar.zip' it'll show those two different file
names.  But in this case we have nested archives and the path (and in this case
also the number of duplicate entries) is identical for both, so maybe we can
tweak the output to show which top-level file it belongs to?

> but 
> https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/arm64/diffoscope-results/libscout.html
> shows this:
>
> Command `'zipdetails --redact --scan --utc {}'` failed with exit code 255. 
> Standard output:
[...]
> though this later is done using diffoscope from unstable while the
> rest of the userland is bullseye, so this might be expected as well?

Ah.  Looks like zipdetails(1) on bullseye doesn't support the --redact, --scan,
and --utc options yet.

- Fay

___
Reproducible-builds mailing list
Reproducible-builds@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/reproducible-builds


Bug#1068705: diffoscope crashes on libscout 2.3.2-3 build on unstable but not bullseye

2024-04-15 Thread Holger Levsen
Hi again,

I've got two remaining questions about libscout (and diffoscope)

On Thu, Apr 11, 2024 at 01:48:18AM +0200, Fay Stegerman wrote:
> unzip does seem to extract all the files, though it errors out.  Not sure what
> diffoscope should do here.  This is definitely a broken ZIP file.  That bug
> should probably be reported against libscout or whatever tooling it used to
> create that JAR.

you filed https://github.com/python/cpython/issues/117779
(thanks again!), am I correct to assume that thus there's no need
to file a seperate bug against libscout?

and 2nd, 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/diffoscope-results/libscout.html
now as expected displays:

'./usr/share/java/libscout.jar' has 35 duplicate entries
'./usr/share/java/libscout.jar' has 35 duplicate entries

(which is nice, though maybe could only been shown once?)

but 
https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/arm64/diffoscope-results/libscout.html
shows this:

Command `'zipdetails --redact --scan --utc {}'` failed with exit code 255. 
Standard output:
zipdetails [OPTIONS] file

Display details about the internal structure of a Zip file.

This is zipdetails version 1.11

OPTIONS
 -h display help
 -v Verbose - output more stuff
[...]
Archive contents identical but files differ, possibly due to different 
compression levels. Falling back to binary comparison.
'./usr/share/java/libscout.jar' has 35 duplicate entries
'./usr/share/java/libscout.jar' has 35 duplicate entries


though this later is done using diffoscope from unstable while the
rest of the userland is bullseye, so this might be expected as well?


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

:wq


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/reproducible-builds