Re: [pkg-go] moving to salsa.debian.org

[Resending from the email which is registered to the pkg-go list ;-) ] On Sat, Mar 10, 2018 at 04:20:39PM -0500, Alexandre Viau wrote: > [...] > Just to be clear: > - Packages that use the git:// scheme in their vcs-git urls, and that > have uploaded modifications or upstream versions, will be le

Re: [pkg-go] moving to salsa.debian.org

On Sat, Mar 10, 2018 at 04:20:39PM -0500, Alexandre Viau wrote: > [...] > Just to be clear: > - Packages that use the git:// scheme in their vcs-git urls, and that > have uploaded modifications or upstream versions, will be left behind. > > I will produce a list of what was left behind, and the r

Re: [pkg-go] moving to salsa.debian.org

Thanks from me too! On 12 March 2018 at 21:59, Michael Stapelberg wrote: > Sounds good. Thank you for your work on this! > > On Sat, Mar 10, 2018 at 10:20 PM, Alexandre Viau wrote: > >> On 2018-03-01 11:16 AM, Alexandre Viau wrote: >> > On 2018-03-01 11:04 AM, Michael Stapelberg wrote: >> >> We

Re: [pkg-go] moving to salsa.debian.org

Sounds good. Thank you for your work on this! On Sat, Mar 10, 2018 at 10:20 PM, Alexandre Viau wrote: > On 2018-03-01 11:16 AM, Alexandre Viau wrote: > > On 2018-03-01 11:04 AM, Michael Stapelberg wrote: > >> We still have 208 packages which don’t use a secure Vcs-* uri (but > >> rather git://).

Re: [pkg-go] moving to salsa.debian.org

On 2018-03-01 11:16 AM, Alexandre Viau wrote: > On 2018-03-01 11:04 AM, Michael Stapelberg wrote: >> We still have 208 packages which don’t use a secure Vcs-* uri (but >> rather git://). Will redirects work for them, too, or will we need to >> upload a new version? > > I had not noticed this.The r

Re: [pkg-go] moving to salsa.debian.org

On 2018-03-01 11:04 AM, Michael Stapelberg wrote: > We still have 208 packages which don’t use a secure Vcs-* uri (but > rather git://). Will redirects work for them, too, or will we need to > upload a new version? I had not noticed this.The redirect won't work for these packages. I can selective

Re: [pkg-go] moving to salsa.debian.org

On 2018-03-01 10:29 AM, Michael Stapelberg wrote: > To elaborate on this point, for HTTP requests, a redirect will be set up. > > aviau, can you confirm that git also supports redirects? Did we test > this with “gbp clone” as well? > > If the answer to either of the two questions is no, we should c

Re: [pkg-go] moving to salsa.debian.org

We still have 208 packages which don’t use a secure Vcs-* uri (but rather git://). Will redirects work for them, too, or will we need to upload a new version? On Thu, Mar 1, 2018 at 4:37 PM, Alexandre Viau wrote: > On 2018-03-01 10:29 AM, Michael Stapelberg wrote: > > To elaborate on this point,

Re: [pkg-go] moving to salsa.debian.org

To elaborate on this point, for HTTP requests, a redirect will be set up. aviau, can you confirm that git also supports redirects? Did we test this with “gbp clone” as well? If the answer to either of the two questions is no, we should consider uploading packages with updated Vcs-* tags so that c

Re: [pkg-go] moving to salsa.debian.org

On 2018-03-01 09:23 AM, Martín Ferrari wrote: > It is true, it does not need to be at the same time. But if we are going > to upload about a thousand packages with the repo changes, we should > probably avoid doing twice :) We are uploading 0 packages as part of this bulk migration. -- Alexandre

Re: [pkg-go] moving to salsa.debian.org

On 01/03/18 08:18, Michael Stapelberg wrote: > I agree with mwhudson’s reply — go-team as group name is what we settled > on (see my thread on the subject, which had a long feedback time > window). I’m okay with the compiler team being a subgroup. Sounds good to me, just wanted to make sure that

Re: [pkg-go] moving to salsa.debian.org

On Wed, Feb 28, 2018 at 10:12 PM, Martín Ferrari wrote: > Hi Michael, > > Thanks for moving this forward! > > On 27/02/18 21:10, Michael Stapelberg wrote: > > > dh-make-golang’s create-salsa-project subcommand now calls this logic > > via an HTTP request, so that we can update the logic independe

Re: [pkg-go] moving to salsa.debian.org

On 28/02/18 23:28, Michael Hudson-Doyle wrote: > The salsa group is now called "go-team" and I thought that's the one we > were going to stick with? I was not sure if that was already agreed, same with the names for the submodules, in particular where the packages are stored. > The go compiler s

Re: [pkg-go] moving to salsa.debian.org

On 1 March 2018 at 10:12, Martín Ferrari wrote: > Hi Michael, > > Thanks for moving this forward! > > On 27/02/18 21:10, Michael Stapelberg wrote: > > > dh-make-golang’s create-salsa-project subcommand now calls this logic > > via an HTTP request, so that we can update the logic independent of th

Re: [pkg-go] moving to salsa.debian.org

Hi Michael, Thanks for moving this forward! On 27/02/18 21:10, Michael Stapelberg wrote: > dh-make-golang’s create-salsa-project subcommand now calls this logic > via an HTTP request, so that we can update the logic independent of the > version of dh-make-golang that users are running (we’ve see

Re: [pkg-go] moving to salsa.debian.org

On Tue, Feb 27, 2018 at 11:20:40PM +0100, Michael Stapelberg wrote: > I think 7 days from when Tincho gives his okay would be reasonable, especially > given that the subject has been under discussion for a while. > Be sure to start a new email thread so that people who have muted this one > will >

Re: [pkg-go] moving to salsa.debian.org

I think 7 days from when Tincho gives his okay would be reasonable, especially given that the subject has been under discussion for a while. Be sure to start a new email thread so that people who have muted this one will see it in their inbox. Thanks! On Tue, Feb 27, 2018 at 11:06 PM, Alexandre

Re: [pkg-go] moving to salsa.debian.org

On 2018-02-27 04:10 PM, Michael Stapelberg wrote: > > Tincho, aviau, can you confirm that we’re good to go? > aviau, are you still up for coordinating and doing the next steps > (sending the announcement, migrating the repositories)? Yep, we are good to go and I'll be doing the next step. Would n

Re: [pkg-go] moving to salsa.debian.org

Status update: I updated my “ci” tool to not only configure the CI settings, but also all other repository settings (webhooks, protected branches, etc.). See https://salsa.debian.org/go-team/ci/blob/master/config/config.go dh-make-golang’s create-salsa-project subcommand now calls this logic via

Re: [pkg-go] moving to salsa.debian.org

No need to do anything manually, there will be an automated migration. On Wed, Feb 21, 2018 at 1:58 PM, Félix Sipma wrote: > I'm not sure of what was the conclusion, sorry if it was already answered. > Is > it planned to move the remaining packages to salsa automatically or do we > have > to do

Re: [pkg-go] moving to salsa.debian.org

I'm not sure of what was the conclusion, sorry if it was already answered. Is it planned to move the remaining packages to salsa automatically or do we have to do this by hand? In the latter case, is alioth->salsa redirection automatically added? Thanks! signature.asc Description: PGP signature

Re: [pkg-go] moving to salsa.debian.org

Sorry for my late reply, life was pretty busy the last few days.. On 27/01/18 16:29, Alexandre Viau wrote: > I don't think the advantages are worth renaming. It could create confusion. > > I don't mind doing it, but please also consider that I would have to > rename the team in the 150 packages t

Re: [pkg-go] moving to salsa.debian.org

On 2018-02-07 02:49 AM, Michael Stapelberg wrote: > I don’t mind having the compiler packages in the go-team. > > Hypothetically, can we set ACLs on subgroups? If so, we should have > go-team/packages (already exists) and go-team/compiler, with the > option to maybe ACL go-team/compiler differently

Re: [pkg-go] moving to salsa.debian.org

On 07/02/2018 08:49, Michael Stapelberg wrote: > I don’t mind having the compiler packages in the go-team. > > Hypothetically, can we set ACLs on subgroups? If so, we should have > go-team/packages (already exists) and go-team/compiler, with the option > to maybe ACL go-team/compiler differently i

Re: [pkg-go] moving to salsa.debian.org

I don’t mind having the compiler packages in the go-team. Hypothetically, can we set ACLs on subgroups? If so, we should have go-team/packages (already exists) and go-team/compiler, with the option to maybe ACL go-team/compiler differently in the future if the need arises. On Tue, Feb 6, 2018 at

Re: [pkg-go] moving to salsa.debian.org

On 6 February 2018 at 13:25, Alexandre Viau wrote: > On 2018-02-04 02:50 PM, Michael Stapelberg wrote: > > > > On Sat, Jan 27, 2018 at 4:29 PM, Alexandre Viau wrote: > >> I don't think the advantages are worth renaming. It could create >> confusion. >> > What confusion specifically do you have i

Re: [pkg-go] moving to salsa.debian.org

On 2018-02-05 06:38 AM, Dr. Tobias Quathamer wrote: > how's the status on this topic? Salsa has now left the beta status, so > from that point we should be safe to migrate. How about the things > listed above? Someone needs to migrate the team website to Gitlab Pages. See this issue for guideline

Re: [pkg-go] moving to salsa.debian.org

On 2018-02-04 02:50 PM, Michael Stapelberg wrote: > > > On Sat, Jan 27, 2018 at 4:29 PM, Alexandre Viau > wrote: > > I don't think the advantages are worth renaming. It could create > confusion. > > What confusion specifically do you have in mind? I think it would

Re: [pkg-go] moving to salsa.debian.org

Am 21.01.2018 um 19:03 schrieb Martín Ferrari: > On 19/01/18 15:25, Alexandre Viau wrote: >> I don't mind waiting, do you have another date to suggest? Or will you >> let us know when your needs are fulfilled? > > Will do, sure. > > I think it would be best if we discuss as a team the migration.

Re: [pkg-go] moving to salsa.debian.org

I don't think the advantages are worth renaming. It could create confusion. I don't mind doing it, but please also consider that I would have to rename the team in the 150 packages that I already migrated. It was announced today that Alioth lists will be maintained, they will probably keep the sa

Re: [pkg-go] moving to salsa.debian.org

Should we take this chance to rename the team to “go-team”? The pkg- prefix was originally taken to be consistent with pkg-perl and pkg-python, and then kept to disambiguate the go compiler packaging team and the go application packaging team. Given that the compiler team is a small handful of pe

Re: [pkg-go] moving to salsa.debian.org

On 2018-01-21 01:03 PM, Martín Ferrari wrote: > My list of things I would like to fix before migrating: > * Repo setup tool: /home/groups/pkg-go/meta/setup-repository I have sent a pull request to dh-make-golang here: - https://github.com/Debian/dh-make-golang/pull/83 Cheers, -- Alexandre Viau

Re: [pkg-go] moving to salsa.debian.org

On 2018-01-21 01:03 PM, Martín Ferrari wrote:> My list of things I would like to fix before migrating: > * Automatic tagging of pending fixes I have modified my repository setup command so that it adds a webhook to tag pending fixes: - https://github.com/Debian/dh-make-golang/pull/83 Cheers, --

Re: [pkg-go] moving to salsa.debian.org

Can the email notifications for the moves be suppressed? It’s quite noisy in my inbox. On Thu, Jan 25, 2018 at 9:18 PM, Alexandre Viau wrote: > > > On 25/01/18 12:38 PM, Alexandre Viau wrote: > >> All of the currently-migrated projects are packages. I will write a > >> script to migrate them to

Re: [pkg-go] moving to salsa.debian.org

On 25/01/18 12:38 PM, Alexandre Viau wrote: >> All of the currently-migrated projects are packages. I will write a >> script to migrate them to the packages/ subgroup and edit the Vcs-* urls >> accordingly. I tested with a few packages, and moving them can be done relatively quickly. I'll migra

Re: [pkg-go] moving to salsa.debian.org

Originally send with wrong email. Sending again. On 25/01/18 12:34 PM, Alexandre Viau wrote: > On 21/01/18 01:03 PM, Martín Ferrari wrote: >> On 19/01/18 15:25, Alexandre Viau wrote: >> One thing that I think has not been discussed is the repo layout: now it >> seems we are using a flat layout, w

Re: [pkg-go] moving to salsa.debian.org

On 23/01/18 03:46 AM, Julian Gilbey wrote: > On Tue, Jan 23, 2018 at 02:35:45AM -0500, Alexandre Viau wrote: >> That would be my new draft announcement: >> >> ``` >> [...] >> - Repository creation on Alioth will be created when the migration >> starts. It will not be re-enabled. > You mean "Reposit

Re: [pkg-go] moving to salsa.debian.org

On Tue, Jan 23, 2018 at 02:35:45AM -0500, Alexandre Viau wrote: > That would be my new draft announcement: > > ``` > [...] > - Repository creation on Alioth will be created when the migration > starts. It will not be re-enabled. You mean "Repository creation on Alioth will be DISABLED when ..."

Re: [pkg-go] moving to salsa.debian.org

On 18/01/18 04:30 PM, Michael Stapelberg wrote: > Thanks for the draft! Comments inline: > > On Wed, Jan 17, 2018 at 10:31 PM, Alexandre Viau > wrote: > > You might want to wait a couple of days after the migration before > spending time doing this because I might

Re: [pkg-go] moving to salsa.debian.org

On Tue, Jan 23, 2018 at 8:35 AM, Alexandre Viau wrote: > On 18/01/18 04:30 PM, Michael Stapelberg wrote: > > Thanks for the draft! Comments inline: > > > > On Wed, Jan 17, 2018 at 10:31 PM, Alexandre Viau > > wrote: > > > > You might want to wait a couple of days aft

Re: [pkg-go] moving to salsa.debian.org

On 19/01/18 15:25, Alexandre Viau wrote: >> Salsa is not ready yet, people (including me) are working on fixing the >> warts, but there are still many things to do. > > The rationale is that Alioth will be deprecated. Yes, but even formorer acknowledges this will take a few months. > Everything

Re: [pkg-go] moving to salsa.debian.org

On Fri, Jan 19, 2018 at 5:35 PM, Dr. Tobias Quathamer wrote: > Am 19.01.2018 um 16:25 schrieb Alexandre Viau: > > On 19/01/18 07:26 AM, Martín Ferrari wrote: > >> On 17/01/18 21:31, Alexandre Viau wrote: > >> > >>> I will be migrating all of pkg-go's Alioth repositories to > >>> salsa.debian.org

Re: [pkg-go] moving to salsa.debian.org

Am 19.01.2018 um 16:25 schrieb Alexandre Viau: > On 19/01/18 07:26 AM, Martín Ferrari wrote: >> On 17/01/18 21:31, Alexandre Viau wrote: >> >>> I will be migrating all of pkg-go's Alioth repositories to >>> salsa.debian.org on January 29. >> Please, don't rush it: that date is way too soon. What is

Re: [pkg-go] moving to salsa.debian.org

On 19/01/18 07:26 AM, Martín Ferrari wrote: > On 17/01/18 21:31, Alexandre Viau wrote: > >> I will be migrating all of pkg-go's Alioth repositories to >> salsa.debian.org on January 29. > Please, don't rush it: that date is way too soon. What is the rationale > for such a sudden switch? > > Salsa i

Re: [pkg-go] moving to salsa.debian.org

On 17/01/18 21:31, Alexandre Viau wrote: > I will be migrating all of pkg-go's Alioth repositories to > salsa.debian.org on January 29. Please, don't rush it: that date is way too soon. What is the rationale for such a sudden switch? Salsa is not ready yet, people (including me) are working on fi

Re: [pkg-go] moving to salsa.debian.org

Thanks for the draft! Comments inline: On Wed, Jan 17, 2018 at 10:31 PM, Alexandre Viau wrote: > On 17/01/18 08:05 AM, Michael Stapelberg wrote: > > I’d be happy to review any draft announcement you come up with. > > > > Alright. > > Here is a draft announcement: > > Dear pkg-go contributors, >

Re: [pkg-go] moving to salsa.debian.org

On 17/01/18 08:05 AM, Michael Stapelberg wrote: > I’d be happy to review any draft announcement you come up with. > Alright. Here is a draft announcement: Dear pkg-go contributors, I will be migrating all of pkg-go's Alioth repositories to salsa.debian.org on January 29. === About the migratio

Re: [pkg-go] moving to salsa.debian.org

Thanks everyone for the details, and especially aviau for getting the technical bits sorted out. Let’s also consider the social aspect of this migration, though. I suggest we send out an announcement regarding the migration timeline and expected impact. More specifically: • Please outline how one

Re: [pkg-go] moving to salsa.debian.org

On 16/01/18 02:54 PM, Alexandre Viau wrote: > I have setup redirects for already-migrated packages. > > I used the ``generate-map-already-migrated.py`` script from the > following repository: > - https://salsa.debian.org/aviau/migrate-pkg-go-to-salsa > > Then, I sent a pull request to the Alioth

Re: [pkg-go] moving to salsa.debian.org

I have setup redirects for already-migrated packages. I used the ``generate-map-already-migrated.py`` script from the following repository: - https://salsa.debian.org/aviau/migrate-pkg-go-to-salsa Then, I sent a pull request to the AliothRewriter repository and created pkg-go.conf: - https://sa

Re: [pkg-go] moving to salsa.debian.org

According to Alexander Wirt:  > From the experience of the last weeks I think we can say that [it] won't happen. - https://lists.debian.org/debian-devel/2018/01/msg00256.html On 16/01/18 02:54 AM, Michael Stapelberg wrote: > Last I heard, there was still a chance that salsa would be reset in > i

Re: [pkg-go] moving to salsa.debian.org

On 16/01/18 03:08 AM, Michael Stapelberg wrote: > How do we ensure that people are redirect from alioth to salsa? I > think some redirection support is underway or already working, so it > would be good to set up these redirects. Redirects are already working. It is on a per-package basis[1]. > R

Re: [pkg-go] moving to salsa.debian.org

How do we ensure that people are redirect from alioth to salsa? I think some redirection support is underway or already working, so it would be good to set up these redirects. Redirects only cover the web interface part, so what do we do with the old git repositories? Could we mark them read-only,

Re: [pkg-go] moving to salsa.debian.org

Last I heard, there was still a chance that salsa would be reset in its entirety. ganneff, is this still the latest, or will salsa definitely keep its data? On Thu, Dec 28, 2017 at 11:36 PM, Alexandre Viau wrote: > Hello Team, > > Alioth will be deprecated. We have to move to salsa.debian.org.

[pkg-go] moving to salsa.debian.org

Hello Team, Alioth will be deprecated. We have to move to salsa.debian.org. I have created a pkg-go team: - https://salsa.debian.org/pkg-go-team You may request to join and I will add you as owners. I suggest we move pacakges manually, one by one, as we upload them. There is no rush because A