Hi Andreas!
I do agree, sounds a good idea to me, so feel free to ahead and move
both python-nmea2 and python-pygal packages to Python team with my
blessing.
Do you need to do something from my end?
Cheers,
\d
On 5/9/26 10:47 AM, Andreas Tille wrote:
Hi Dererk,
I would be interested in helping to move python-nmea2 to the Debian
Python team. Since following the Package Salvaging procedure outlined
in the Developers Reference[1] is the wrong procedure for this package
due to the absence of QA issues I'm simply opening this wishlist bug,
I believe the package would be a great addition to the Python team, and
I took the liberty to create the Salsa repository here[2]. So I hope
you agree that Salsa can be a great advantage and take over from here
(or give me permission to do a team upload).
What do you think?
Kind regards
Andreas.
PS: I'd similarly happy about migrating python-pygal.
[1]https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging
[2]https://salsa.debian.org/python-team/packages/python-nmea2
-- System Information:
Debian Release: forky/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (50, 'buildd-unstable'),
(1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.19.14+deb14-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
