On 26/10/2019 22:50, Matthias Klose wrote:
Ubuntu already dropped python-pandas, I wasn't involved with that.
This seems to have been done by the "let things break" approach that
isn't allowed in Debian, e.g. they can no longer build python-matplotlib:
https://bugs.debian.org/cgi-bin/bugreport.
On 26.10.19 22:09, Rebecca N. Palmer wrote:
What should be done with modules where Python 3.8 compatibility requires moving
to a new upstream release that doesn't support Python 2, but the Python 2
package still has dependencies (so can't be removed yet under existing rules)?
- Split them into
What should be done with modules where Python 3.8 compatibility requires
moving to a new upstream release that doesn't support Python 2, but the
Python 2 package still has dependencies (so can't be removed yet under
existing rules)?
- Split them into two source packages with different upstream
Hi,
so 26. 10. 2019 v 21:33 odesílatel Jeremy Bicha napsal:
> Please add me to https://salsa.debian.org/python-team/modules
>
done, welcome. :)
> I expect to help out a bit with the Python2 removals
thanks a lot!
--
Best regards
Ondřej Nový
Hi,
Please add me to https://salsa.debian.org/python-team/modules
My Salsa username is jbicha
I am already a member of PAPT.
I expect to help out a bit with the Python2 removals and being able to
update Salsa is helpful for that. I have experience in removing
libgnome from Debian, a major proje
This had a bug: packages with source name = binary name don't have a
Source: field in the binary Packages file, which makes grep-dctrl skip
them when asked to output the Source field.
Fixed version:
grep-dctrl -w -F Pre-Depends,Depends,Recommends -s Package
"python-$module"
/var/lib/apt/list
6 matches
Mail list logo
