Hi,
Yese there will be a 3.10.1+dfsg1-3.
1.
I think we should keep for now a pristine /etc/matplotlibrc
and tell somehow it's depreciation.
And then remove it in Forky.
Or maybe convince upstream to look for /etc/matplotlibrc if it's there.
(disclaimer: I do use these optional /etc/matplotlib
> /etc/matplotlibrc.
We have another example:
pip reads /etc/pip.conf and it's really useful to document there
what the company proxy is named.
So reverting the old patched /etc/matplotlibrc to upstream
pristine config was a first step in right direction;
I agree it should be removed later.
I
> > > I'm worried that a lot of ___undeclared___ dependencies on
"undeclared" is the important word here.
The code does "import pkg_resources" but the library is gone :-(
The lintian check that was used to detect the dead batteries
& later lead to a MBF could be extended to pkg_resources too;
then
Hi, welcome
Every single of your emails ends up in the spam folder,
so recinting in full to get others a chance to read it.
> packaging recommendations.
I cannot even find such slight divergens from rules...
everything looks fine
Greetings
Le ven. 27 juin 2025 à 20:07, Antoine Le Gonidec a éc
101 - 104 of 104 matches
Mail list logo