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

[Julian Gilbey]

[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 left behind.
> 
> I will produce a list of what was left behind, and the reason, so that
> we can finish the work. I may have the time to fix it all by myself
> during the migration.
> 
> I'll send the migration email soon. So maybe we can migrate next monday,
> or the one after that.
> 
> Sorry for the delay, I had very few times in the past weeks due to
> mid-semester.

Thanks, that sounds really good!

If you're still a bit busy, it's probably better to wait a little
until you know you'll have time to fix any problems that might arise
rather than rushing it and things going wrong.

Best wishes,

   Julian

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

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

[Julian Gilbey]

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 reason, so that
> we can finish the work. I may have the time to fix it all by myself
> during the migration.
> 
> I'll send the migration email soon. So maybe we can migrate next monday,
> or the one after that.
> 
> Sorry for the delay, I had very few times in the past weeks due to
> mid-semester.

Thanks, that sounds really good!

If you're still a bit busy, it's probably better to wait a little
until you know you'll have time to fix any problems that might arise
rather than rushing it and things going wrong.

Best wishes,

   Julian

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

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

[Michael Hudson-Doyle]

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 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 selectively re-upload only these packages during the migration.
>>
>> I have modified my migration script to do that.
>>
>> However, if there are packages that have new un-uploaded upstream
>> versions, I will leave them behind, as I don't want to risk
>> automatically uploading new upstream versions. This means that there may
>> still be some manual work to do after the migration, but it should be
>> very minimal compared to what will be automated.
>>
>> 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 reason, so that
>> we can finish the work. I may have the time to fix it all by myself
>> during the migration.
>>
>> I'll send the migration email soon. So maybe we can migrate next monday,
>> or the one after that.
>>
>> Sorry for the delay, I had very few times in the past weeks due to
>> mid-semester.
>>
>> Cheers,
>>
>> --
>> Alexandre Viau
>> av...@debian.org
>>
>>
>
>
> --
> Best regards,
> Michael
>
> ___
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
>
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

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

[Michael Stapelberg]

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://). 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 selectively re-upload only these packages during the migration.
>
> I have modified my migration script to do that.
>
> However, if there are packages that have new un-uploaded upstream
> versions, I will leave them behind, as I don't want to risk
> automatically uploading new upstream versions. This means that there may
> still be some manual work to do after the migration, but it should be
> very minimal compared to what will be automated.
>
> 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 reason, so that
> we can finish the work. I may have the time to fix it all by myself
> during the migration.
>
> I'll send the migration email soon. So maybe we can migrate next monday,
> or the one after that.
>
> Sorry for the delay, I had very few times in the past weeks due to
> mid-semester.
>
> Cheers,
>
> --
> Alexandre Viau
> av...@debian.org
>
>


-- 
Best regards,
Michael
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

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

[Alexandre Viau]

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 redirect won't work for these packages.
> 
> I can selectively re-upload only these packages during the migration.

I have modified my migration script to do that.

However, if there are packages that have new un-uploaded upstream
versions, I will leave them behind, as I don't want to risk
automatically uploading new upstream versions. This means that there may
still be some manual work to do after the migration, but it should be
very minimal compared to what will be automated.

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 reason, so that
we can finish the work. I may have the time to fix it all by myself
during the migration.

I'll send the migration email soon. So maybe we can migrate next monday,
or the one after that.

Sorry for the delay, I had very few times in the past weeks due to
mid-semester.

Cheers,

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



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

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

[Alexandre Viau]

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 selectively re-upload only these packages during the migration.

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




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

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

[Alexandre Viau]

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 consider
> uploading packages with updated Vcs-* tags so that cloning keeps working.

Yes, git supports HTTP redirects. The HTTP VCS-* urls in d/control will
still work. And it will work with "gbp clone".

You can test it with any of the package that are listed here:
 -
https://salsa.debian.org/salsa/AliothRewriter/blob/master/definitions/pkg-go.conf

For example:
 - $ gbp clone https://anonscm.debian.org/git/pkg-go/packages/syncthing.git

Cheers,

-- 

Alexandre Viau
av...@debian.org




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

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

[Michael Stapelberg]

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, 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 cloning keeps working.
>
> Yes, git supports HTTP redirects. The HTTP VCS-* urls in d/control will
> still work. And it will work with "gbp clone".
>
> You can test it with any of the package that are listed here:
>  -
> https://salsa.debian.org/salsa/AliothRewriter/blob/
> master/definitions/pkg-go.conf
>
> For example:
>  - $ gbp clone https://anonscm.debian.org/git/pkg-go/packages/syncthing.
> git
>
> Cheers,
>
> --
>
> Alexandre Viau
> av...@debian.org
>
>
>


-- 
Best regards,
Michael
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

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

[Michael Stapelberg]

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 cloning keeps working.

On Thu, Mar 1, 2018 at 4:20 PM, Alexandre Viau  wrote:

> 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 Viau
> av...@debian.org
>
>
>


-- 
Best regards,
Michael
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

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

[Alexandre Viau]

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 Viau
av...@debian.org




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

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

[Martín Ferrari]

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 we agreed on it before
doing changes :)

> Can you explain why the maintainer address needs to be changed in the
> same step as the repository move?

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

> As far as I’m concerned, we can leave it as-is for the time being. The
> mailing list will be migrated, and there will be a separate turn-down
> cycle for that in a few years.

OK, if that is possible, I have no objections.

-- 
Martín Ferrari (Tincho)

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

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

[Michael Stapelberg]

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 independent of the
> > version of dh-make-golang that users are running (we’ve seen people run
> > very old versions). See
>
> I was going to say that my version of the tool does not have it, but
> then I realised it is there, but the help or the man say nothing about
> it.. Is there a reference somewhere?
>

No, dh-make-golang subcommands are fairly new and undocumented. I filed
https://github.com/Debian/dh-make-golang/issues/91 to track the cleanup I
had planned.


>
> > 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)?
>
> I have some things in mind that I think have not been resolved yet:
>
> * Have we decided on a naming scheme, including group name? What about
> the go compiler stuff? (I think it will make sense to join everytihng
> under one group)
>

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.


> * What about mailing list and maintainer address? I know the perl people
> solved this somehow, but I don't understand how :)
>
> These two are important, because we should define them before changing
> all repos and mass-committing hundreds of changes.
>

Can you explain why the maintainer address needs to be changed in the same
step as the repository move?

As far as I’m concerned, we can leave it as-is for the time being. The
mailing list will be migrated, and there will be a separate turn-down cycle
for that in a few years.

-- 
Best regards,
Michael
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

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

[Martín Ferrari]

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 stuff should be a subgroup of the go-team group,
> although I don't think anything about that should block the package
> migration.

True.

-- 
Martín Ferrari (Tincho)

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

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

[Michael Hudson-Doyle]

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 the
> > version of dh-make-golang that users are running (we’ve seen people run
> > very old versions). See
>
> I was going to say that my version of the tool does not have it, but
> then I realised it is there, but the help or the man say nothing about
> it.. Is there a reference somewhere?
>
> > 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)?
>
> I have some things in mind that I think have not been resolved yet:
>
> * Have we decided on a naming scheme, including group name? What about
> the go compiler stuff? (I think it will make sense to join everytihng
> under one group)
>

The salsa group is now called "go-team" and I thought that's the one we
were going to stick with?

The go compiler stuff should be a subgroup of the go-team group, although I
don't think anything about that should block the package migration.


> * What about mailing list and maintainer address? I know the perl people
> solved this somehow, but I don't understand how :)
>

I don't know the answer to this bit.

Cheers,
mwh


> These two are important, because we should define them before changing
> all repos and mass-committing hundreds of changes.
>
> --
> Martín Ferrari (Tincho)
>
> ___
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
>
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

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

[Martín Ferrari]

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 seen people run
> very old versions). See

I was going to say that my version of the tool does not have it, but
then I realised it is there, but the help or the man say nothing about
it.. Is there a reference somewhere?

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

I have some things in mind that I think have not been resolved yet:

* Have we decided on a naming scheme, including group name? What about
the go compiler stuff? (I think it will make sense to join everytihng
under one group)
* What about mailing list and maintainer address? I know the perl people
solved this somehow, but I don't understand how :)

These two are important, because we should define them before changing
all repos and mass-committing hundreds of changes.

-- 
Martín Ferrari (Tincho)

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

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

[Julian Gilbey]

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
> see it in their inbox.
> Thanks!

Thanks all for your hard work!

   Julian

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

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

[Michael Stapelberg]

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 Viau  wrote:

> 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 next week be okay? What kind of delay do we want?
>
> Cheers,
>
> --
> Alexandre Viau
> av...@debian.org
>
>
>


-- 
Best regards,
Michael
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

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

[Alexandre Viau]

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 next week be okay? What kind of delay do we want?

Cheers,

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




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

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

[Michael Stapelberg]

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
an HTTP request, so that we can update the logic independent of the version
of dh-make-golang that users are running (we’ve seen people run very old
versions). See

I ran the updated “ci” tool on all of our repos, so all of them now have
the tagpending and KGB webhooks configured. As you may recall from the CI
thread, the tool runs every hour, so even manually created repositories
will end up with the correct configuration eventually. Creating repos via
dh-make-golang is preferred, as the configuration will then be correct from
the very beginning.

With the hooks correctly configured, I think we have addressed all
blockers. The website repository can remain on alioth for the time being,
and we’ll migrate it later — that shouldn’t block the packaging
repositories.

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

On Wed, Feb 21, 2018 at 2:25 PM, Michael Stapelberg 
wrote:

> 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 this by hand? In the latter case, is alioth->salsa redirection
>> automatically added?
>>
>> Thanks!
>>
>> ___
>> Pkg-go-maintainers mailing list
>> Pkg-go-maintainers@lists.alioth.debian.org
>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-
>> go-maintainers
>>
>
>
>
> --
> Best regards,
> Michael
>



-- 
Best regards,
Michael
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

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

[Michael Stapelberg]

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 this by hand? In the latter case, is alioth->salsa redirection
> automatically added?
>
> Thanks!
>
> ___
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
>



-- 
Best regards,
Michael
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

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

[Félix Sipma]

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
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

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

[Martín Ferrari]

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 that I already migrated.
While I won't suggest a change for the sake of it, I think the fact that
some packages were migrated before we had this discussion should not be
a determining factor. This is why I complained when you started doing it.

Now, on to the name itself, I think it'd be wise to try to have a
similar scheme to other teams. Dunno if there is any consensus yet, but
for example the perl team has gone for perl-team.

-- 
Martín Ferrari (Tincho)

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

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

[Alexandre Viau]

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 in the future if the
> need arises.

Yes, we could. However, I suggest we don't do that unless "the need
arises", like you said.

For now, I am adding:
 - DDs as owners of the main group
 - *-guests as masters of the main group

For *-guest users, the situation is about the same as we had in Alioth:
 - They can create repositories
 - They can push on all repositories
 - They could "wipe" all repositories if they wanted (by using the
gitlab UI and unprotecting branches). However, they can't delete a project.

Maybe guests could have less permissions, however, giving them
"developper" permissions means they won't be able to create
repositories, and that is unfortunate.

By the way, I have:
 - Reuploaded all existing packages with VCS-urls to set to "go-team"
 - Requested a team rename: https://salsa.debian.org/salsa/support/issues/50
 - Updated the rewrite map:
https://salsa.debian.org/salsa/AliothRewriter/merge_requests/121

Alexander Wirt has merged the Rewrite map update, but he didn't rename
the team yet.

Until the team is renamed, the VCS-* urls are pointing to the wrong
location. It probably won't last for long, please be patient :).

Cheers,

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




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

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

[Michael Hudson-Doyle]

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 in mind? I think it would be more
> confusing to be named “pkg-go” in the long run, especially as other teams
> dropped the pkg- prefix.
>
>
> Will the compiler team still exist? What name will it have?
>

I think it probably makes sense to have the golang-1.x and golang-defaults
packages under 'go-team' too, I don't know if the other Michael or Paul or
Tianon have other opinions.

Cheers,
mwh


> I too have just noticed that other teams have dropped the prefix. In that
> case, I tend to prefer go-team too.
>
> I can probably rename it (and the packages)  in the next few days.
>
> Please don't rename the team without also updating all repositories and
> uploading all packages, which I intend to do, if you give me the time.
>
> --
> Alexandre viauav...@debian.org
>
>
> ___
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
>
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

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

[Alexandre Viau]

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 guidelines:
 - https://salsa.debian.org/salsa/support/issues/43

When I last tested, it didn't work. Apparently that was fixed.

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



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

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

[Alexandre Viau]

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 be
> more confusing to be named “pkg-go” in the long run, especially as
> other teams dropped the pkg- prefix.

Will the compiler team still exist? What name will it have?

I too have just noticed that other teams have dropped the prefix. In
that case, I tend to prefer go-team too.

I can probably rename it (and the packages)  in the next few days.

Please don't rename the team without also updating all repositories and
uploading all packages, which I intend to do, if you give me the time.

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



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

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

[Dr. Tobias Quathamer]

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. Get all
> the tools we use now changed or replaced, and set a time table.
> 
> My list of things I would like to fix before migrating:
> 
> * Team website
> * Repo setup tool: /home/groups/pkg-go/meta/setup-repository
> * KGB
> * Automatic tagging of pending fixes
> * PET, hopefully, but that might not be feasible in time.
> 
> One thing that I think has not been discussed is the repo layout: now it
> seems we are using a flat layout, whereas before we had a packages tree,
> separate from other things like meta, website, and even a users/
> subtree. What are we going to do with those?

Dear all,

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?

Regards,
Tobias



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

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

[Alexandre Viau]

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 same name, pkg-go.


On 2018-01-27 07:02 AM, Michael Stapelberg wrote:
> 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 people, and the
> application team is quite large, I think it’s fair the application
> team should get the shortest name.
>
> Given salsa’s team restrictions (team must end in “-team”), I think
> “go-team” is both descriptive and short. Thoughts?
>
> On Fri, Jan 26, 2018 at 8:00 PM, Alexandre Viau  > wrote:
>
> 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,
>
> --
> Alexandre Viau
> av...@debian.org 
>
>
> ___
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers@lists.alioth.debian.org
> 
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
> 
> 
>
>
>
>
> -- 
> Best regards,
> Michael

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



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

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

[Michael Stapelberg]

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 people, and the
application team is quite large, I think it’s fair the application team
should get the shortest name.

Given salsa’s team restrictions (team must end in “-team”), I think
“go-team” is both descriptive and short. Thoughts?

On Fri, Jan 26, 2018 at 8:00 PM, Alexandre Viau  wrote:

> 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,
>
> --
> Alexandre Viau
> av...@debian.org
>
>
> ___
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
>



-- 
Best regards,
Michael
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

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

[Alexandre Viau]

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
av...@debian.org



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

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

[Alexandre Viau]

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,

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



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

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

[Michael Stapelberg]

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 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 migrate them over the course of the next few days, unless somebody
> prefers another subgroup name.
>
> Cheers,
>
> --
> Alexandre Viau
> av...@debian.org
>
>
> ___
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
>



-- 
Best regards,
Michael
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

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

[Alexandre Viau]

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 migrate them over the course of the next few days, unless somebody
prefers another subgroup name.

Cheers,

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



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

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

[Alexandre Viau]

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, whereas before we had a packages tree,
>> separate from other things like meta, website, and even a users/
>> subtree. What are we going to do with those?
> 
> Good point. This is something that I overlooked.
> 
> I suggest creating a packages/ subgroup[1].
> 
> This also allows us to manage permissions individually. For example, we
> could give -guest access to the packages/ subgroup as masters but no to
> the other trees.
> 
> Looking at the group page will also be less cluttered.
> 
> 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.
> 
> Please comment if you would prefer another layout.
> 
> 1. https://salsa.debian.org/pkg-go-team/packages
> 

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



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

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

[Alexandre Viau]

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 "Repository creation on Alioth will be DISABLED when ..."

Yeah, oops!

> I presume that when the time comes, this announcement will be emailed
> to all Go package maintainers individually, and not just to this list?
Yep!

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




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

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

[Julian Gilbey]

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

I presume that when the time comes, this announcement will be emailed
to all Go package maintainers individually, and not just to this list?

Best wishes,

   Julian

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

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

[Alexandre Viau]

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 automate it for all
> repositories.
>
>
> Let’s figure this out before starting the process :). I’m in favor for
> automating the step. The less people have to do mindless work that can
> easily go wrong, the better (as evidenced by a number of incorrect
> Vcs-* tags in our packages).

Alright, done. I have updated my migration script to edit Vcs-* urls!
(https://salsa.debian.org/aviau/migrate-pkg-go-to-salsa)

It does not create a changelog entry yet, but I'll fix that before the
migration.
 
>
>
> - A copy of the migrated repositories will remain available in
>
>
> “A read-only copy” please.

Okay, I agree.

>  
>
> git.debian.org:/git/pkg-go/packages-migrated-to-salsa
>
> - You will still be able to create repositories on Alioth, but there
> will be no other bulk migration.
>
> - If all went well, we might disable repository creation on Alioth a
> couple of days after the migration.
>
>
> I’d like to disable repository creation at the start of the migration.
> There’s no point in allowing backslide/stragglers like that.
> Everything should be in one place.

Okay, but can you allow me to do that? You are the only owner of the
setup-repository script. I would just `chmod -x setup-repository`.

That would be my new draft announcement:

```
Dear pkg-go contributors,

I will be migrating all of pkg-go's Alioth repositories to
salsa.debian.org  on .

=== About the migration ===

- A mail will be sent to pkg-go-maintainers@lists.alioth.debian.org
 when
the migration starts and when it ends

- All repositories in git.debian.org:/git/pkg-go/packages will be
migrated to the pkg-go-team group on salsa.debian.org
[1] You should join
the group if you are not already in it!

- Repositories will keep the same name, with ".git" removed.

- HTTP anonscm.debian.org  links of migrated
repositories will be
redirected to the new location.
 for example, you can test the following links:
  - https://anonscm.debian.org/cgit/pkg-go/packages/syncthing

  - https://anonscm.debian.org/git/pkg-go/packages/syncthing.git


- Vcs-* urls will be automatically replaced in debian/control

- Repository creation on Alioth will be created when the migration
starts. It will not be re-enabled.

=== During the migration ===

- You may still push to Alioth. However, your pushes could be denied
because the repository no longer exists.Don't panic! It was moved to
Gitlab. If you push to Alioth during the migration, take a moment to
confirm that your changes are available on salsa after the migration,
just in case there was some sort of race condition.

- You may start using salsa repositories immediately after they are
created. No need to wait for the migration to end.

=== After the migration ===

- A read-only copy of the migrated repositories will remain available in
git.debian.org:/git/pkg-go/packages-migrated-to-salsa

- You may point your git working directories to the new remote address
with this oneliner:
 ``git remote set-url origin g...@salsa.debian.org:pkg-go-team/$(git
config --get remote.origin.url | tr "/" "\n" | tail -n 1)``

1. https://salsa.debian.org/pkg-go-team


Cheers,

```

We will wait for an answer from tincho before we pick a date, but do you
have any other comments on the announcement?

Thanks,

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




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

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

[Michael Stapelberg]

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 after the migration before
> > spending time doing this because I might automate it for all
> > repositories.
> >
> >
> > Let’s figure this out before starting the process :). I’m in favor for
> > automating the step. The less people have to do mindless work that can
> > easily go wrong, the better (as evidenced by a number of incorrect
> > Vcs-* tags in our packages).
>
> Alright, done. I have updated my migration script to edit Vcs-* urls!
> (https://salsa.debian.org/aviau/migrate-pkg-go-to-salsa)
>
> It does not create a changelog entry yet, but I'll fix that before the
> migration.
>
> >
> >
> > - A copy of the migrated repositories will remain available in
> >
> >
> > “A read-only copy” please.
>
> Okay, I agree.
>
> >
> >
> > git.debian.org:/git/pkg-go/packages-migrated-to-salsa
> >
> > - You will still be able to create repositories on Alioth, but there
> > will be no other bulk migration.
> >
> > - If all went well, we might disable repository creation on Alioth a
> > couple of days after the migration.
> >
> >
> > I’d like to disable repository creation at the start of the migration.
> > There’s no point in allowing backslide/stragglers like that.
> > Everything should be in one place.
>
> Okay, but can you allow me to do that? You are the only owner of the
> setup-repository script. I would just `chmod -x setup-repository`.
>

I can perform that step when the migration starts.


>
> That would be my new draft announcement:
>
> ```
> Dear pkg-go contributors,
>
> I will be migrating all of pkg-go's Alioth repositories to
> salsa.debian.org  on .
>
> === About the migration ===
>
> - A mail will be sent to pkg-go-maintainers@lists.alioth.debian.org
>  when
> the migration starts and when it ends
>
> - All repositories in git.debian.org:/git/pkg-go/packages will be
> migrated to the pkg-go-team group on salsa.debian.org
> [1] You should join
> the group if you are not already in it!
>
> - Repositories will keep the same name, with ".git" removed.
>
> - HTTP anonscm.debian.org  links of migrated
> repositories will be
> redirected to the new location.
>  for example, you can test the following links:
>   - https://anonscm.debian.org/cgit/pkg-go/packages/syncthing
> 
>   - https://anonscm.debian.org/git/pkg-go/packages/syncthing.git
> 
>
> - Vcs-* urls will be automatically replaced in debian/control
>
> - Repository creation on Alioth will be created when the migration
> starts. It will not be re-enabled.
>
> === During the migration ===
>
> - You may still push to Alioth. However, your pushes could be denied
> because the repository no longer exists.Don't panic! It was moved to
> Gitlab. If you push to Alioth during the migration, take a moment to
> confirm that your changes are available on salsa after the migration,
> just in case there was some sort of race condition.
>
> - You may start using salsa repositories immediately after they are
> created. No need to wait for the migration to end.
>
> === After the migration ===
>
> - A read-only copy of the migrated repositories will remain available in
> git.debian.org:/git/pkg-go/packages-migrated-to-salsa
>
> - You may point your git working directories to the new remote address
> with this oneliner:
>  ``git remote set-url origin g...@salsa.debian.org:pkg-go-team/$(git
> config --get remote.origin.url | tr "/" "\n" | tail -n 1)``
>
> 1. https://salsa.debian.org/pkg-go-team
> 
>
> Cheers,
>
> ```
>
> We will wait for an answer from tincho before we pick a date, but do you
> have any other comments on the announcement?
>

Looks good to me :)


>
> Thanks,
>
> --
> Alexandre Viau
> av...@debian.org
>
>
>


-- 
Best regards,
Michael
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

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

[Martín Ferrari]

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 I need/use is ready.
> 
> 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. Get all
the tools we use now changed or replaced, and set a time table.

My list of things I would like to fix before migrating:

* Team website
* Repo setup tool: /home/groups/pkg-go/meta/setup-repository
* KGB
* Automatic tagging of pending fixes
* PET, hopefully, but that might not be feasible in time.

One thing that I think has not been discussed is the repo layout: now it
seems we are using a flat layout, whereas before we had a packages tree,
separate from other things like meta, website, and even a users/
subtree. What are we going to do with those?


-- 
Martín Ferrari (Tincho)

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

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

[Dr. Tobias Quathamer]

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 the rationale
>> for such a sudden switch?
>>
>> 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.

I think it would be wise to wait until the beta phase of salsa is
officially over.

Even though salsa seems to be very stable, the admins have stated that
there's a (probably minimal) chance of a database reset.

Regards,
Tobias



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

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

[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 the rationale
> for such a sudden switch?
>
> 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.

Everything I need/use is ready.

I don't mind waiting, do you have another date to suggest? Or will you
let us know when your needs are fulfilled?

Cheers,

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




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

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

[Michael Stapelberg]

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,
>
> I will be migrating all of pkg-go's Alioth repositories to
> salsa.debian.org on January 29.
>
> === About the migration ===
>
> - A mail will be sent to pkg-go-maintainers@lists.alioth.debian.org when
> the migration starts and when it ends
>
> - All repositories in git.debian.org:/git/pkg-go/packages will be
> migrated to the pkg-go-team group on salsa.debian.org[1] You should join
> the group if you are not already in it!
>
> - Repositories will keep the same name, with ".git" removed.
>
> - HTTP anonscm.debian.org links of migrated repositories will be
> redirected to the new location.
>  for example, you can test the following links:
>   - https://anonscm.debian.org/cgit/pkg-go/packages/syncthing
>   - https://anonscm.debian.org/git/pkg-go/packages/syncthing.git
>
> === During the migration ===
>
> - Your pushes could be denied because the repository no longer exists.
> Don't panic! It was moved to Gitlab.
>
> - You may start using salsa repositories immediately after they are
> created.
>
> - If you push during the migration, take a moment to confirm that your
> changes are available on salsa
>
> === After the migration ===
>
> - On the next upload of your packages, please replace the VCS-*
> anonscm.debian.org links with the proper salsa.debian.org links.
>
> For example:
>  https://anonscm.debian.org/cgit/pkg-go/packages/syncthing ->
> https://salsa.debian.org/pkg-go-team/syncthing
>  https://anonscm.debian.org/git/pkg-go/packages/syncthing.git ->
> https://salsa.debian.org/pkg-go-team/syncthing.git
>
> You might want to wait a couple of days after the migration before
> spending time doing this because I might automate it for all repositories.
>

Let’s figure this out before starting the process :). I’m in favor for
automating the step. The less people have to do mindless work that can
easily go wrong, the better (as evidenced by a number of incorrect Vcs-*
tags in our packages).


>
> - A copy of the migrated repositories will remain available in
>

“A read-only copy” please.


> git.debian.org:/git/pkg-go/packages-migrated-to-salsa
>
> - You will still be able to create repositories on Alioth, but there
> will be no other bulk migration.
>
> - If all went well, we might disable repository creation on Alioth a
> couple of days after the migration.
>

I’d like to disable repository creation at the start of the migration.
There’s no point in allowing backslide/stragglers like that. Everything
should be in one place.


>
> - You may point your git working directories to the new remote address
> with this oneliner:
>  ``git remote set-url origin g...@salsa.debian.org:pkg-go-team/$(git
> config --get remote.origin.url | tr "/" "\n" | tail -n 1)``
>
> 1. https://salsa.debian.org/pkg-go-team
>
> Cheers,
>
> --
> Alexandre Viau
> av...@debian.org
>
>
>


-- 
Best regards,
Michael
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

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

[Alexandre Viau]

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 migration ===

- A mail will be sent to pkg-go-maintainers@lists.alioth.debian.org when
the migration starts and when it ends

- All repositories in git.debian.org:/git/pkg-go/packages will be
migrated to the pkg-go-team group on salsa.debian.org[1] You should join
the group if you are not already in it!

- Repositories will keep the same name, with ".git" removed.

- HTTP anonscm.debian.org links of migrated repositories will be
redirected to the new location.
 for example, you can test the following links:
  - https://anonscm.debian.org/cgit/pkg-go/packages/syncthing
  - https://anonscm.debian.org/git/pkg-go/packages/syncthing.git

=== During the migration ===

- Your pushes could be denied because the repository no longer exists.
Don't panic! It was moved to Gitlab.

- You may start using salsa repositories immediately after they are created.

- If you push during the migration, take a moment to confirm that your
changes are available on salsa

=== After the migration ===

- On the next upload of your packages, please replace the VCS-*
anonscm.debian.org links with the proper salsa.debian.org links.

For example:
 https://anonscm.debian.org/cgit/pkg-go/packages/syncthing ->
https://salsa.debian.org/pkg-go-team/syncthing
 https://anonscm.debian.org/git/pkg-go/packages/syncthing.git ->
https://salsa.debian.org/pkg-go-team/syncthing.git

You might want to wait a couple of days after the migration before
spending time doing this because I might automate it for all repositories.

- A copy of the migrated repositories will remain available in
git.debian.org:/git/pkg-go/packages-migrated-to-salsa

- You will still be able to create repositories on Alioth, but there
will be no other bulk migration.

- If all went well, we might disable repository creation on Alioth a
couple of days after the migration.

- You may point your git working directories to the new remote address
with this oneliner:
 ``git remote set-url origin g...@salsa.debian.org:pkg-go-team/$(git
config --get remote.origin.url | tr "/" "\n" | tail -n 1)``

1. https://salsa.debian.org/pkg-go-team

Cheers,

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




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

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

[Michael Stapelberg]

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 can easily update their git working directories to
switch to the new remote address. Perhaps there is a git or sed oneliner we
could use?
• Let’s give people at least 7 days notice to activate their account on
GitLab, and to voice any feedback or concerns they might have regarding the
migration.
• It might be good to send a targeted reminder to people who are in the
pkg-go team on alioth, but not yet on GitLab.

I’d be happy to review any draft announcement you come up with.

Thanks!

On Tue, Jan 16, 2018 at 10:00 PM, Joerg Jaspert  wrote:

> On 14919 March 1977, 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.
>
> MergeRequest in https://salsa.debian.org/salsa/AliothRewriter
>
> > Redirects only cover the web interface part, so what do we do with the
> old
> > git repositories? Could we mark them read-only, to prevent accidental
> > pushes to the wrong repository?
>
> Yes. Thats the common way.
>
> --
> bye, Joerg
>



-- 
Best regards,
Michael
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

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

[Alexandre Viau]

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 AliothRewriter repository and created
> pkg-go.conf:
>  -
> https://salsa.debian.org/salsa/AliothRewriter/blob/master/definitions/pkg-go.conf
> 
> For example, you may now:
>  - Visit https://salsa.debian.org/pkg-go-team/syncthing
>  - Clone https://salsa.debian.org/pkg-go-team/syncthing.git

oops, wrong links!

These are the relevant links:
 - Visit: https://anonscm.debian.org/cgit/pkg-go/packages/syncthing.git
 - Clone: https://anonscm.debian.org/git/pkg-go/packages/syncthing.git

Cheers,

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



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

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

[Alexandre Viau]

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://salsa.debian.org/salsa/AliothRewriter/blob/master/definitions/pkg-go.conf

For example, you may now:
 - Visit https://salsa.debian.org/pkg-go-team/syncthing
 - Clone https://salsa.debian.org/pkg-go-team/syncthing.git

Cheers,

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



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

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

[Alexandre Viau]

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
> 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
> .
>
> 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 Alioth will remain accessible read-only.
>
> I will move my own packages as I go, and remove them from
> git.debian.org 
> at the same time to avoid confusion.
>
> I'll also spend some time with dh-make-golang and see if there is an
> easy way to automatically create projects using the gitlab api...
>
> Cheers,
>
> --
> Alexandre Viau
> av...@debian.org 
>
>
> ___
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers@lists.alioth.debian.org
> 
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
> 
> 
>
>
>
>
> -- 
> Best regards,
> Michael

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



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

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

[Michael Stapelberg]

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, to prevent accidental
pushes to the wrong repository?

On Tue, Jan 16, 2018 at 8:54 AM, Michael Stapelberg 
wrote:

> 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.
>>
>> 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 Alioth will remain accessible read-only.
>>
>> I will move my own packages as I go, and remove them from git.debian.org
>> at the same time to avoid confusion.
>>
>> I'll also spend some time with dh-make-golang and see if there is an
>> easy way to automatically create projects using the gitlab api...
>>
>> Cheers,
>>
>> --
>> Alexandre Viau
>> av...@debian.org
>>
>>
>> ___
>> Pkg-go-maintainers mailing list
>> Pkg-go-maintainers@lists.alioth.debian.org
>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-
>> go-maintainers
>>
>
>
>
> --
> Best regards,
> Michael
>



-- 
Best regards,
Michael
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

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

[Michael Stapelberg]

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.
>
> 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 Alioth will remain accessible read-only.
>
> I will move my own packages as I go, and remove them from git.debian.org
> at the same time to avoid confusion.
>
> I'll also spend some time with dh-make-golang and see if there is an
> easy way to automatically create projects using the gitlab api...
>
> Cheers,
>
> --
> Alexandre Viau
> av...@debian.org
>
>
> ___
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
>



-- 
Best regards,
Michael
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers