On 08/01/18 08:24 PM, Julian Gilbey wrote:
> However, the lists.alioth.debian.org list is due to be shut down in
> three weeks' time (on 2018-02-01) as announced in
> https://lists.debian.org/debian-devel-announce/2017/09/msg00004.html
> so what email address should I use instead?  And where is the Debian
> Go Packaging Team page going to migrate to?


> so what email address should I use instead?

Raphaël Hertzog has updated tracker.debian.org to support team email
addresses. We can now send mails to team+<team-slug>@tracker.debian.org.
The tracker system will also recognize the email in the maintainer field
and automatically add the packages to the tracker.debian.org team.

In our case, our tracker email would be team+pkg...@tracker.debian.org.

For now, these mails will be discarded and you will have to rely on
other tracker.debian.org features to receive updates about the packages
but more features will be added.

I have created a pkg-go team on tracker.debian.org:
 - https://tracker.debian.org/teams/pkg-go/

To join the team, ask me and I will add you to it (I still don't really
know how it works).

> And where is the Debian Go Packaging Team page going to migrate to?

I have begun testing building our team page with Gitlab Pages[2]. Salsa
is supposed to support it[3]. However, the build is stuck and it does
not work. I suppose this is going to be fixed soon. Our team page would
eventually move to https://pages.debian.net/pkg-go-team/website.

> Also, when the git.debian.org shared pkg-go repository is migrated
> over to salsa (which I understand has to happen manually), will I need
> to migrate my packages over, or will all of the pkg-go packages be
> migrated in bulk?

You can already migrate your packages in the salsa pkg-go team[4]. I
have already migrated more than a hundred.

I suggest that every time you upload a package as part of the team, you
take the time to migrate it manually to salsa, removing it from Alioth.

In a previous discussion on this list, tincho was wondering if it was a
good idea to update the VCS-* links because we can setup redirects with
AliothRewriter[5] to point anonscm.debian.org links to salsa.

However, the AliothRewriter README says:
 > The existance of this list should not mean that VCS control fields
 > shouldn't get updated with the next upload. This map is just a
 > workaround.

This means that when you upload a package, you should use the
opportunity to update the VCS-* links.

I may start working on a bulk transition script (that will also include
AliothRewriter redirects) but this does not mean that you should not
migrate package manually in the meantime, as you upload them.

Cheers,

1. https://lists.debian.org/debian-devel/2018/01/msg00265.html
2. https://salsa.debian.org/aviau/website-test
3. https://wiki.debian.org/Salsa/Doc#Host_project_web_pages
4. https://salsa.debian.org/pkg-go-team
5. https://salsa.debian.org/salsa/AliothRewriter

-- 
Alexandre Viau
av...@debian.org

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

Reply via email to