[Pkg-javascript-devel] alioth is down: what to do with those 119 packages ?

[Paolo Greppi]

Il 02/06/2018 00:21, Mattia Rizzolo ha scritto:
> ...
> 1) we could have redirects added to https://salsa.debian.org/salsa/AliothRewriter/
>    And there already is a long list (1150 lines) for pkg-js' packages.

Yes I know because I'm the one who did it, see:
https://alioth-lists.debian.net/pipermail/pkg-javascript-devel/2018-April/025850.html

>    If any are missing they could/should be added.  This would amke the
>    Vcs-* fields still perfectly valid.  The very goal of that thing is
>    to avoid having to do thousands of uploads only changing Vcs-*.

That's also a possibility.

I had interpreted in a strict way the remark "The existance of this list should
not mean that VCS control fields shouldn't get updated with the next upload"
found in the first paragraph here:
https://salsa.debian.org/salsa/AliothRewriter/blob/master/README.md
Since these pending uploads haven't been accepted yet, one may argue that they
count as "next upload".
For this reason when I had migrated the repos from alioth to salsa I had not
done the redirects ad for the 1082 already updated 

Anyway I have just created a MR for that purpose, let's see if formorer merges
it: https://salsa.debian.org/salsa/AliothRewriter/merge_requests/316

The merge request covers 114 packages of the 117 currently listed by Debian NEW
Packages fancy view as being in this situation (it was 119 yesterday...)

For these 3 I cannot create a redirect because there's no salsa repo:
- node-insert-module-globals
- node-mimelib
- rainloop
I have just written to the ITPs requesting the owners to create the repos on
salsa and reupload.

> 2) if really wanted, the packages could be updated while still being in
>    NEW: just upload a newever version, then they will both be accepted
>    at the same time whenever they will be processed.

Where it only for updating the Vcs-* fields, I have done that already:
https://alioth-lists.debian.net/pipermail/pkg-javascript-devel/2018-May/026261.html

But I assume that in preparing a newer version one would want to check if upstream
had moved on, updating std-version, making it lintian clean...
That effort is tracked in this kanboard:
https://salsa.debian.org/js-team/current_itps/boards
just filter by label_name == NEW-alioth

I have done it for node-ansicolors and node-classnames, but I have not RFS
because noone else from the team had done any move in this direction and this
matter can only be addressed by the team, not by a single individual.

But is the js-team a team ?

Paolo