Hi Lucas, On 30/03/25 1:35 pm, Lucas Nussbaum wrote: > 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
This is due to compilation failure of c++ source > healpy_1.18.0-1_unstable.log FTBFS due to patches being improperly applied (local changes detected) > pandas_2.2.3+dfsg-8_unstable.log Known failure, fix pushed to unstable > python-csb43_0.10.1+dfsg-1_unstable.log FTBFS due to patches being improperly applied (local changes detected) > python-maggma_0.70.0-3_unstable.log Failure due to missing dependencies (pyproject_hooks._impl.BackendUnavailable: Cannot import 'setuptools.build_meta') > python-mne_1.9.0-1_unstable.log Same failure as in #1100273 (reported march 12) > pytroll-schedule_0.7.2-2_unstable.log Skimming through the code, it does not look related to matplotlib but would be nice if someone can double-check. > sphinx-copybutton_0.5.2-2_unstable.log Dependency issue [Extension error (pydata_sphinx_theme)] > xarray-sentinel_0.9.5+ds-3_unstable.log I don't see any build/runtime dep on matplotlib and even grepping through the code, it is not used. > (those are not necessarily caused by matplotlib changes) It seems all failures are unrelated to matplotlib. > You can find the relevant logs at http://qa-logs.debian.net/2025/03/27/ Thank you very very very much for helping with this! :) > Best, > > Lucas Best, Nilesh
