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

Groups > linux.debian.kernel > #60319 > unrolled thread

Migrating to Salsa

Back to article view | Back to linux.debian.kernel

Contents

  Migrating to Salsa Ben Hutchings <ben@decadent.org.uk> - 2018-02-23 01:20 +0100
    Re: Migrating to Salsa Bastian Blank <waldi@debian.org> - 2018-02-23 08:30 +0100
      Re: Migrating to Salsa Ben Hutchings <ben@decadent.org.uk> - 2018-02-23 11:50 +0100
        Re: Migrating to Salsa Salvatore Bonaccorso <carnil@debian.org> - 2018-02-23 15:30 +0100
          Re: Migrating to Salsa Ben Hutchings <ben@decadent.org.uk> - 2018-02-23 23:00 +0100
            Re: Migrating to Salsa Bastian Blank <waldi@debian.org> - 2018-02-24 09:30 +0100
    Re: Migrating to Salsa Yves-Alexis Perez <corsac@debian.org> - 2018-02-23 10:00 +0100
    Re: Migrating to Salsa Salvatore Bonaccorso <carnil@debian.org> - 2018-02-23 15:30 +0100
    Re: Migrating to Salsa Ben Hutchings <ben@decadent.org.uk> - 2018-03-11 18:40 +0100
    Re: Migrating to Salsa Ben Hutchings <ben@decadent.org.uk> - 2018-03-11 23:50 +0100

#60319 — Migrating to Salsa

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

We need to move everything from Alioth to Salsa some time before the
end of May.

There is already a "kernel-team" group on Salsa, and the members of the
"kernel" group on Alioth have been added to this group.

Since all our live version control repositories use git, it should be a
simple and quick process to replicate them on Salsa.  I think what we
need to do is:

1. Agree the date and time to start migration.
2. At that time, add hooks on Alioth to disable further writes.
3. Start migration.
4. Update all references to Alioth:
   - Configure anonscm.debian.org to forward to Salsa
   - Update package Vcs fields
   - Update kernel-handbook text

I don't think we use many other features of Alioth.  The features I
know about are:

* kernel-svn-changes mailing list and hook.  I think this will be
  redundant.  Any Salsa user can "watch" a repository or group to
  receive email notifications about commits.
* IRC notification hook (KGB client).  Salsa has an "integration" for
  the Irker notification service.  This needs to be enabled and
  configured with the server and channel details for each repository.
  I don't know whether anything needs to be done on the Irker server
  side.

Have I missed anything?

I propose that we start the migration after the point release is done,
so on Sunday 11th March, starting at 16:00 UTC.

Ben.

-- 
Ben Hutchings
[W]e found...that it wasn't as easy to get programs right as we had
thought. ... I realized that a large part of my life from then on was
going to be spent in finding mistakes in my own programs. - Maurice
Wilkes, 1949

[toc] | [next] | [standalone]

#60321

On Fri, Feb 23, 2018 at 01:13:11AM +0100, Ben Hutchings wrote:
> * kernel-svn-changes mailing list and hook.  I think this will be
>   redundant.  Any Salsa user can "watch" a repository or group to
>   receive email notifications about commits.

I don't know where this information is from, but pushs don't currently
create notifications.  Right now you need to use the email on push
feature.

> * IRC notification hook (KGB client).  Salsa has an "integration" for
>   the Irker notification service.  This needs to be enabled and
>   configured with the server and channel details for each repository.
>   I don't know whether anything needs to be done on the Irker server
>   side.

No changes needs to be done on the server.

Bastian

-- 
Every living thing wants to survive.
		-- Spock, "The Ultimate Computer", stardate 4731.3

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

#60324

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

On Fri, 2018-02-23 at 08:03 +0100, Bastian Blank wrote:
> On Fri, Feb 23, 2018 at 01:13:11AM +0100, Ben Hutchings wrote:
> > * kernel-svn-changes mailing list and hook.  I think this will be
> >   redundant.  Any Salsa user can "watch" a repository or group to
> >   receive email notifications about commits.
> 
> I don't know where this information is from, but pushs don't currently
> create notifications.  Right now you need to use the email on push
> feature.

Oh, that's annoying.  So we can enable email on push, but we may not
have a suitable list to send to for long.

> > * IRC notification hook (KGB client).  Salsa has an "integration" for
> >   the Irker notification service.  This needs to be enabled and
> >   configured with the server and channel details for each repository.
> >   I don't know whether anything needs to be done on the Irker server
> >   side.
> 
> No changes needs to be done on the server.

Great.

Ben.

-- 
Ben Hutchings
Who are all these weirdos? - David Bowie, reading IRC for the first
time

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

#60327

Hello

Thanks Ben for pushing that forward.

On Fri, Feb 23, 2018 at 11:40:37AM +0100, Ben Hutchings wrote:
> On Fri, 2018-02-23 at 08:03 +0100, Bastian Blank wrote:
> > On Fri, Feb 23, 2018 at 01:13:11AM +0100, Ben Hutchings wrote:
> > > * kernel-svn-changes mailing list and hook.  I think this will be
> > >   redundant.  Any Salsa user can "watch" a repository or group to
> > >   receive email notifications about commits.
> > 
> > I don't know where this information is from, but pushs don't currently
> > create notifications.  Right now you need to use the email on push
> > feature.
> 
> Oh, that's annoying.  So we can enable email on push, but we may not
> have a suitable list to send to for long.

For the time beeing the kernel-svn-changes mailing list can be
configured to be used and then the list migrated as well by the list
continuation project. 

But we might need to ask are people still interested in using the
commit mailing list / are there users?

> > > * IRC notification hook (KGB client).  Salsa has an "integration" for
> > >   the Irker notification service.  This needs to be enabled and
> > >   configured with the server and channel details for each repository.
> > >   I don't know whether anything needs to be done on the Irker server
> > >   side.
> > 
> > No changes needs to be done on the server.
> 
> Great.

JFTR, if one wants: There is now as well the option to continue using
KGB. webhook-support has been added to kgb.

Cf. https://salsa.debian.org/kgb-team/kgb/wikis/usage

Regards,
Salvatore

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

#60338

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

On Fri, 2018-02-23 at 15:24 +0100, Salvatore Bonaccorso wrote:
> Hello
> 
> Thanks Ben for pushing that forward.
> 
> On Fri, Feb 23, 2018 at 11:40:37AM +0100, Ben Hutchings wrote:
> > On Fri, 2018-02-23 at 08:03 +0100, Bastian Blank wrote:
> > > On Fri, Feb 23, 2018 at 01:13:11AM +0100, Ben Hutchings wrote:
> > > > * kernel-svn-changes mailing list and hook.  I think this will be
> > > >   redundant.  Any Salsa user can "watch" a repository or group to
> > > >   receive email notifications about commits.
> > > 
> > > I don't know where this information is from, but pushs don't currently
> > > create notifications.  Right now you need to use the email on push
> > > feature.
> > 
> > Oh, that's annoying.  So we can enable email on push, but we may not
> > have a suitable list to send to for long.
> 
> For the time beeing the kernel-svn-changes mailing list can be
> configured to be used and then the list migrated as well by the list
> continuation project. 
> 
> But we might need to ask are people still interested in using the
> commit mailing list / are there users?

I just had a look at a script for Salsa migration
(https://salsa.debian.org/jcowgill/multimedia-cli/blob/master/multimedia-cli.py)
and realised that there is now a standard way to send VCS commit emails
through tracker.debian.org.

So in case anyone does care, it seems like that's the way to go.

> > > > * IRC notification hook (KGB client).  Salsa has an "integration" for
> > > >   the Irker notification service.  This needs to be enabled and
> > > >   configured with the server and channel details for each repository.
> > > >   I don't know whether anything needs to be done on the Irker server
> > > >   side.
> > > 
> > > No changes needs to be done on the server.
> > 
> > Great.
> 
> JFTR, if one wants: There is now as well the option to continue using
> KGB. webhook-support has been added to kgb.
> 
> Cf. https://salsa.debian.org/kgb-team/kgb/wikis/usage

Oh, that's nice.  I haven't seen Irker's notifications, so I am not in
a position to judge whether either is preferable.

Ben.

-- 
Ben Hutchings
Who are all these weirdos? - David Bowie, reading IRC for the first
time

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

#60339

On Fri, Feb 23, 2018 at 10:55:54PM +0100, Ben Hutchings wrote:
> I just had a look at a script for Salsa migration
> (https://salsa.debian.org/jcowgill/multimedia-cli/blob/master/multimedia-cli.py)
> and realised that there is now a standard way to send VCS commit emails
> through tracker.debian.org.
> 
> So in case anyone does care, it seems like that's the way to go.

It is even planned to make this usable as maintainer.  However I'm not
sure about the current state.

> > JFTR, if one wants: There is now as well the option to continue using
> > KGB. webhook-support has been added to kgb.
> > 
> > Cf. https://salsa.debian.org/kgb-team/kgb/wikis/usage
> Oh, that's nice.  I haven't seen Irker's notifications, so I am not in
> a position to judge whether either is preferable.

It looks like this:

08:05 < salsabot> [AliothRewriter] Alexander Wirt pushed 2 new commits to master: https://salsa.debian.org/salsa/AliothRewriter/compare/831058a9...002939d3
08:05 < salsabot> AliothRewriter/master a74bdd05 Damyan Ivanov (1 file): add definitions for pkg-perl packages (3467 lines)
08:05 < salsabot> AliothRewriter/master 002939d3 Alexander Wirt (1 file): Merge branch 'master' into 'master'

Bastian

-- 
There's coffee in that nebula!
		-- Capt. Kathryn Janeway, Star Trek: Voyager, "The Cloud"

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

#60323

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

On Fri, 2018-02-23 at 01:13 +0100, Ben Hutchings wrote:
> We need to move everything from Alioth to Salsa some time before the
> end of May.
> 
> There is already a "kernel-team" group on Salsa, and the members of the
> "kernel" group on Alioth have been added to this group.
> 
> Since all our live version control repositories use git, it should be a
> simple and quick process to replicate them on Salsa.  I think what we
> need to do is:
> 
> 1. Agree the date and time to start migration.
> 2. At that time, add hooks on Alioth to disable further writes.
> 3. Start migration.
> 4. Update all references to Alioth:
>    - Configure anonscm.debian.org to forward to Salsa
>    - Update package Vcs fields
>    - Update kernel-handbook text

Looks good to me.
> 
> I don't think we use many other features of Alioth.  The features I
> know about are:
> 
> * kernel-svn-changes mailing list and hook.  I think this will be
>   redundant.  Any Salsa user can "watch" a repository or group to
>   receive email notifications about commits.

As Bastian said, notifications for pushes don't work. For the stuff I migrated
myself I added email integration to the previous lists, which should work for
a time until proper notification are supported.

> * IRC notification hook (KGB client).  Salsa has an "integration" for
>   the Irker notification service.  This needs to be enabled and
>   configured with the server and channel details for each repository.
>   I don't know whether anything needs to be done on the Irker server
>   side.

Yes, it works just fine. By the way there's a bunch of salsa scripts at https:
//salsa.debian.org/mehdi/salsa-scripts which are helpful to setup a salsa
project.
> 
> Have I missed anything?
> 
> I propose that we start the migration after the point release is done,
> so on Sunday 11th March, starting at 16:00 UTC.

It's fine by me.

Regards,
-- 
Yves-Alexis

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

#60328

Hi Ben,

On Fri, Feb 23, 2018 at 01:13:11AM +0100, Ben Hutchings wrote:
> We need to move everything from Alioth to Salsa some time before the
> end of May.
> 
> There is already a "kernel-team" group on Salsa, and the members of the
> "kernel" group on Alioth have been added to this group.
> 
> Since all our live version control repositories use git, it should be a
> simple and quick process to replicate them on Salsa.  I think what we
> need to do is:
> 
> 1. Agree the date and time to start migration.
> 2. At that time, add hooks on Alioth to disable further writes.
> 3. Start migration.
> 4. Update all references to Alioth:
>    - Configure anonscm.debian.org to forward to Salsa
>    - Update package Vcs fields
>    - Update kernel-handbook text

Look good to me.

> I propose that we start the migration after the point release is done,
> so on Sunday 11th March, starting at 16:00 UTC.

Works for me as well.

Regards,
Salvatore

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

#60447

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

On Fri, 2018-02-23 at 01:13 +0100, Ben Hutchings wrote:
> We need to move everything from Alioth to Salsa some time before the
> end of May.
> 
> There is already a "kernel-team" group on Salsa, and the members of the
> "kernel" group on Alioth have been added to this group.
> 
> Since all our live version control repositories use git, it should be a
> simple and quick process to replicate them on Salsa.  I think what we
> need to do is:
> 
> 1. Agree the date and time to start migration.
> 2. At that time, add hooks on Alioth to disable further writes.
> 3. Start migration.

These are now done, and all the migrations appear to have completed
successfully.

I did not do anything about these repositories on Alioth, which I think
were part of an experiment with submodules some years ago:

- preview/packages/linux
- preview/source/linux
- source/linux

> 4. Update all references to Alioth:
>    - Configure anonscm.debian.org to forward to Salsa
>    - Update package Vcs fields
>    - Update kernel-handbook text

This is still TBD.

> I don't think we use many other features of Alioth.  The features I
> know about are:
> 
> * kernel-svn-changes mailing list and hook.  I think this will be
>   redundant.  Any Salsa user can "watch" a repository or group to
>   receive email notifications about commits.

I have enabled the email hook, sending via tracker.debian.org.

> * IRC notification hook (KGB client).  Salsa has an "integration" for
>   the Irker notification service.  This needs to be enabled and
>   configured with the server and channel details for each repository.
>   I don't know whether anything needs to be done on the Irker server
>   side.

I have enabled the KGB webhook.

> Have I missed anything?

Hopefully not.

There are some files served from <https://kernel.alioth.debian.org/>
but I don't think any of them need to be preserved.

Ben.

> I propose that we start the migration after the point release is done,
> so on Sunday 11th March, starting at 16:00 UTC.
> 
> Ben.
> 
-- 
Ben Hutchings
Unix is many things to many people,
but it's never been everything to anybody.

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

#60457

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

On Fri, 2018-02-23 at 01:13 +0100, Ben Hutchings wrote:
[...]
> 4. Update all references to Alioth:
>    - Configure anonscm.debian.org to forward to Salsa

I have sent a merge request for AliothRewriter to do this:
https://salsa.debian.org/salsa/AliothRewriter/merge_requests/232

>    - Update package Vcs fields

I've done this in the current development branch (master or sid) for
all the repositories except nfs-utils, which has diverged from the
actual state of packaging.

>    - Update kernel-handbook text
[...]

I've done this.

Ben.

-- 
Ben Hutchings
Unix is many things to many people,
but it's never been everything to anybody.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web