Hi, On 18/03/25 at 10:11 +0530, Nilesh Patra wrote: > On 18 March 2025 5:43:41 am IST, Alexandre Detiste > <alexandre.deti...@gmail.com> wrote: > >Le lun. 17 mars 2025 à 03:56, Nilesh Patra <nil...@riseup.net> a écrit : > >> I will check the pseudo-excuses on britney in around week. Hopefully, this > >> upload should solve majority of issues. > > > >Only five autopkgtest failing and already two packages fixed ! > > > >Can we ask $someone to rebuild everything from unstable that > >depends on matplotlib against this new version ? > >(to see what fails) > > Since there is no as such ABI for this, which other modules use, so it won't > be a transition per se as far as I understand. > > Otherwise it won't be possible to do right now since we are in toolchain > freeze. > > But it does make sense to test the reverse build depends at least at the this > (pre-release) stage, to avoid FTBFS bugs as much as possible. > > >I might remember there was a free-service instance available > >somewhere but wouldn't mind some hand-holding. > > I do not have such resources to do massive rebuilds like these. > > I am adding Lucas to the thread. Lucas, do you think you could help us here?
Sorry for not replying earlier. I see that you uploaded matplotlib 3.10 to unstable in the meantime. I did a rebuild of unstable two days ago, and did not notice anything specific related to matplotlib. The build failures involving matplotlib are: graph-tool_2.91+ds-4_unstable.log healpy_1.18.0-1_unstable.log pandas_2.2.3+dfsg-8_unstable.log python-csb43_0.10.1+dfsg-1_unstable.log python-maggma_0.70.0-3_unstable.log python-mne_1.9.0-1_unstable.log pytroll-schedule_0.7.2-2_unstable.log sphinx-copybutton_0.5.2-2_unstable.log xarray-sentinel_0.9.5+ds-3_unstable.log (those are not necessarily caused by matplotlib changes) You can find the relevant logs at http://qa-logs.debian.net/2025/03/27/ Best, Lucas
