Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #13468 > unrolled thread

Plan to upload all packages still using Alioth in Maintainer/Uploaders

Back to article view | Back to linux.debian.maint.python

Contents

  Plan to upload all packages still using Alioth in Maintainer/Uploaders Sandro Tosi <morph@debian.org> - 2021-08-14 04:30 +0200
    Re: Plan to upload all packages still using Alioth in  Maintainer/Uploaders Stefano Rivera <stefanor@debian.org> - 2021-08-14 15:50 +0200
      Re: Plan to upload all packages still using Alioth in  Maintainer/Uploaders stefanor@debian.org - 2021-08-14 15:50 +0200
      Re: Plan to upload all packages still using Alioth in  Maintainer/Uploaders Louis-Philippe Véronneau <pollo@debian.org> - 2021-08-14 22:00 +0200
    Re: Plan to upload all packages still using Alioth in  Maintainer/Uploaders Brian Thompson <brian@hashvault.io> - 2021-08-15 00:40 +0200
    Re: Plan to upload all packages still using Alioth in  Maintainer/Uploaders Dmitry Shachnev <mitya57@debian.org> - 2021-08-15 20:20 +0200
    Re: Plan to upload all packages still using Alioth in Maintainer/Uploaders Sandro Tosi <morph@debian.org> - 2021-08-24 06:20 +0200

#13468 — Plan to upload all packages still using Alioth in Maintainer/Uploaders

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,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

[toc] | [next] | [standalone]

#13469 — Re: Plan to upload all packages still using Alioth in Maintainer/Uploaders

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)

We should fix them all.

Generally +1 to your proposal.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

[toc] | [prev] | [next] | [standalone]

#13470 — Re: Plan to upload all packages still using Alioth in Maintainer/Uploaders

Hi debian-python (2021.08.14_13:30:00_+0000)
> 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

For clarity, I don't mean hijack the things that are obviously other
teams :)

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

[toc] | [prev] | [next] | [standalone]

#13471 — Re: Plan to upload all packages still using Alioth in Maintainer/Uploaders

[Multipart message — attachments visible in raw view] — view raw

On 2021-08-14 09 h 30, Stefano Rivera wrote:
> 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)

Good catch. FWIW, I've opened a feature request on Lintian to try to
catch those kind of errors [1].

[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991955

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   pollo@debian.org / veronneau.org
  ⠈⠳⣄

[toc] | [prev] | [next] | [standalone]

#13473 — Re: Plan to upload all packages still using Alioth in Maintainer/Uploaders

[Multipart message — attachments visible in raw view] — view raw

On 0813, Sandro Tosi wrote:
>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,

I think this is a good idea and a rather thankless job. Maintenance
things like this always need to be done. Thank you!

-- 
Best regards,

Brian T

[toc] | [prev] | [next] | [standalone]

#13474 — Re: Plan to upload all packages still using Alioth in Maintainer/Uploaders

[Multipart message — attachments visible in raw view] — view raw

Hi all,

On Fri, Aug 13, 2021 at 10:25:21PM -0400, Sandro Tosi wrote:
> 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).

Just please don’t upload everything at once, following the release team’s
recommendation [1] (in order to manage load on the buildds etc.)

Also there may be packages which have large WIP changes in git, which are
not yet ready for upload. I am not sure how to detect them, but maybe exclude
packages which have a new upstream release in git (compared to unstable)?

[1]: https://lists.debian.org/debian-devel-announce/2021/08/msg00001.html

On Sat, Aug 14, 2021 at 01:30:00PM +0000, Stefano Rivera wrote:
> 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.

Except the first two (which are valid addresses not related to our team).

--
Dmitry Shachnev

[toc] | [prev] | [next] | [standalone]

#13482

> 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).

progress for this work is now tracked at
https://github.com/sandrotosi/debian-python-team-tracker

Regards,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web