Control: reassign libapache-poi-java 4.0.1-4 Le mardi 07 juin 2022 à 16:45 +0200, Sébastien Villemot a écrit : > Le samedi 28 mai 2022 à 21:28 +0200, Paul Gevers a écrit : > > Source: libapache-poi-java, octave-io > > Control: found -1 libapache-poi-java/4.0.1-4 > > Control: found -1 octave-io/2.6.4-1 > > Severity: serious > > Tags: sid bookworm > > User: debian...@lists.debian.org > > Usertags: breaks needs-update > > > With a recent upload of libapache-poi-java the autopkgtest of octave-io > > fails in testing when that autopkgtest is run with the binary packages > > of libapache-poi-java from unstable. It passes when run with only > > packages from testing. > > First note that the only change between libapache-poi-java 4.0.1-3 and > 4.0.1-4 is the upgrade to xmlbeans 4.0.0. > > Attached is a minimal test case that reproduces what octave-io does in > its autopkgtest.
I’m reassigning this issue to libapache-poi-java. octave-io’s upstream thinks that the problem comes from an incorrect combination of versions between libapache-poi-java and xmlbeans. That seems confirmed by the minimal test case that I attached to my previous email (which used to work but no longer does, without any indication that the API used therein is deprecated). -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄⠀⠀⠀⠀ https://www.debian.org
signature.asc
Description: This is a digitally signed message part