There are more than those, some other variants made it into use too:
udd=> SELECT COUNT(*), maintainer_email FROM sources WHERE release='sid' AND maintainer_email LIKE '%python%' GROUP BY maintainer_email;
count | maintainer_email -------+-------------------------------------------------
1 | gst-python1.0@packages.debian.org
1 | pkg-python-debian-maint@lists.alioth.debian.org
[1] https://lintian.debian.org/tags/python-teams-merged
Hi Sandro (2021.08.14_02:25:21_+0000)
[1] https://lintian.debian.org/tags/python-teams-merged
There are more than those, some other variants made it into use too:
udd=> SELECT COUNT(*), maintainer_email FROM sources WHERE release='sid' AND maintainer_email LIKE '%python%' GROUP BY maintainer_email;
count | maintainer_email -------+-------------------------------------------------
1 | gst-python1.0@packages.debian.org
1 | pkg-python-debian-maint@lists.alioth.debian.org
1 | python-apps-team@alioth-lists.debian.net
1 | python-apps-team@lists.alioth.debian.net
62 | python-apps-team@lists.alioth.debian.org
15 | python-modules-team@alioth-lists.debian.net
713 | python-modules-team@lists.alioth.debian.org
9 | team+python-modules@tracker.debian.org
670 | team+python@tracker.debian.org
(9 rows)
Hello,
a long time ago, we decided to stop using Alioth for the team email
address in Maintainer/Uploaders fields, and onovy mass-committed this
change to our repo; several of our packages (736, according to [1])
are still using Alioth.
[1] https://lintian.debian.org/tags/python-teams-merged
Alioth is no longer maintained (or at the very least, our 2 mailing
lists), and the amount of spam received through it is way too high to
be sustainable.
After the upcoming release of bullseye, I plan to start uploading all >packages that currently use Alioth to migrate them to Tracker (along
with the other pending changes in the git repos).
I understand it's possible an upload exists in experimental that fixes
it, so i'll try and check for that; it's also likely that if a package
is still using Alioth, their maintainer is longer interested in the
package, but i dont think now it's the time for a mass purge. I also >understand some of these packages will have the team as Uploaders and, >according to our Policy, i should contact the physical person doing
the upload beforehand, but i think that would slow down this process
and i'm ready to deal with the consequences of not following the
Policy to the letter.
Please let me know if you prefer me to act differently.
Regards,
Hello,
a long time ago, we decided to stop using Alioth for the team email
address in Maintainer/Uploaders fields, and onovy mass-committed this
change to our repo; several of our packages (736, according to [1])
are still using Alioth.
[1] https://lintian.debian.org/tags/python-teams-merged
Alioth is no longer maintained (or at the very least, our 2 mailing
lists), and the amount of spam received through it is way too high to
be sustainable.
After the upcoming release of bullseye, I plan to start uploading all packages that currently use Alioth to migrate them to Tracker (along
with the other pending changes in the git repos).
There are more than those, some other variants made it into use too:
udd=> SELECT COUNT(*), maintainer_email FROM sources WHERE release='sid' AND maintainer_email LIKE '%python%' GROUP BY maintainer_email;
count | maintainer_email -------+-------------------------------------------------
1 | gst-python1.0@packages.debian.org
1 | pkg-python-debian-maint@lists.alioth.debian.org
1 | python-apps-team@alioth-lists.debian.net
1 | python-apps-team@lists.alioth.debian.net
62 | python-apps-team@lists.alioth.debian.org
15 | python-modules-team@alioth-lists.debian.net
713 | python-modules-team@lists.alioth.debian.org
9 | team+python-modules@tracker.debian.org
670 | team+python@tracker.debian.org
(9 rows)
We should fix them all.
After the upcoming release of bullseye, I plan to start uploading all packages that currently use Alioth to migrate them to Tracker (along
with the other pending changes in the git repos).
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 350 |
Nodes: | 16 (2 / 14) |
Uptime: | 08:53:04 |
Calls: | 7,625 |
Files: | 12,793 |
Messages: | 5,686,430 |