Le vendredi 31 mai 2024 à 12:43 +0200, Emilio Pozuelo Monfort a écrit : > On 31/05/2024 12:19, Sébastien Villemot wrote: > > Le vendredi 31 mai 2024 à 09:31 +0200, Emilio Pozuelo Monfort a écrit : > > > On 24/05/2024 19:34, Emilio Pozuelo Monfort wrote: > > > > On 22/05/2024 14:49, Sébastien Villemot wrote: > > > > > Package: release.debian.org > > > > > Severity: normal > > > > > X-Debbugs-Cc: libma...@packages.debian.org > > > > > Control: affects -1 + src:libmatio > > > > > User: release.debian....@packages.debian.org > > > > > Usertags: transition > > > > > Control: forwarded -1 > > > > > https://release.debian.org/transitions/html/auto-libmatio.html > > > > > > > > > > Dear Release Team, > > > > > > > > > > Please schedule a transition for libmatio. > > > > > > > > > > I’ve successfully rebuilt all reverse dependencies against the new > > > > > version > > > > > (currently in experimental), except gnss-sdr and labplot which are > > > > > currently > > > > > unbuildable due to the qt5 transition. > > > > > > > > Let's wait for the Qt 5 transition then. > > > > > > The Qt 5 transition is over now, so assuming those two packages build > > > against > > > libmatio13, then go ahead with this. > > > > It turns out that labplot FTBFS against the new libmatio. I opened a > > bug and submitted a patch that fixes the issue. > > > > Should I upload libmatio to unstable now and then NMU labplot, or > > should I give some time to the labplot maintainer to react? > > Either way is fine. You can start the transition now as I believe libmatio > can > be smooth-updated, so we don't really have to block on labplot. Of course > fixing > it later if the maintainer doesn't would be good in order to complete the > transition.
Thanks. I just uploaded the new libmatio to unstable. -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄⠀⠀⠀⠀ https://www.debian.org
signature.asc
Description: This is a digitally signed message part
