mirror GitLab -> Savannah

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

mirror GitLab -> Savannah

Jonas Hahnfeld
To keep this short: I'd like to enable push mirroring from GitLab to
Savannah for the following branches [1]:
 - master
 - release/unstable
 - stable/*
 - translation*
This is a feature of GitLab and runs automatically in the background:
https://gitlab.com/help/user/project/repository/repository_mirroring.md

I've already created a new lilypod_bot user and requested access to the
Savannah project. Unless somebody objects, I'll configure GitLab
accordingly and paste the generated SSH key for the Savannah user.

Regards,
Jonas


1: These are exactly those which I configured "protected". This means
they cannot be force-pushed which corresponds to what we had before.

signature.asc (499 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: mirror GitLab -> Savannah

Valentin Villenave-3
On 5/14/20, Jonas Hahnfeld <[hidden email]> wrote:
> To keep this short: I'd like to enable push mirroring from GitLab to
> Savannah for the following branches [1]:
>  - master
>  - release/unstable
>  - stable/*
>  - translation*

Why not staging? (Assuming that’s still gonna be a thing in months to come.)

By the way, I still haven’t understood why it would be
necessary/advisable to erase all the old branches on Savannah. (I’m
thinking about a few branches that may or may not be of historical
interest, such as cvs/master and some of the dev/* branches.)

V.

Reply | Threaded
Open this post in threaded view
|

Re: mirror GitLab -> Savannah

David Kastrup
Valentin Villenave <[hidden email]> writes:

> On 5/14/20, Jonas Hahnfeld <[hidden email]> wrote:
>> To keep this short: I'd like to enable push mirroring from GitLab to
>> Savannah for the following branches [1]:
>>  - master
>>  - release/unstable
>>  - stable/*
>>  - translation*
>
> Why not staging? (Assuming that’s still gonna be a thing in months to
> come.)

Probably would not work.  staging is rebased comparatively frequently
and Savannah does not allow for non-forwarding pushes (what I actually
did whenever a non-forwarding push became necessary because of a
problematic commit was _delete_ the branch and recreate a new one with
the same name).

> By the way, I still haven’t understood why it would be
> necessary/advisable to erase all the old branches on Savannah. (I’m
> thinking about a few branches that may or may not be of historical
> interest, such as cvs/master and some of the dev/* branches.)

I think it was just seen as an opportunity for cleanup.

--
David Kastrup

Reply | Threaded
Open this post in threaded view
|

Re: mirror GitLab -> Savannah

Jonas Hahnfeld
In reply to this post by Valentin Villenave-3
Am Donnerstag, den 14.05.2020, 22:22 +0200 schrieb Valentin Villenave:
> On 5/14/20, Jonas Hahnfeld <[hidden email]> wrote:
> > To keep this short: I'd like to enable push mirroring from GitLab to
> > Savannah for the following branches [1]:
> >  - master
> >  - release/unstable
> >  - stable/*
> >  - translation*
>
> Why not staging? (Assuming that’s still gonna be a thing in months to come.)

Partly because of the latter, hopefully we'll not live with this
forever. More concretely because development happens at GitLab. As such
nobody should be relying on Savannah, least of all for pushing. So even
if we continue using it, it doesn't provide a value being mirrored from
GitLab to Savannah.
Lastly because of what David wrote: Force pushing is a problem. Apart
from Savannah not accepting it, I also don't want to make staging a
protected branch on GitLab (then you can't even delete it, which is
what we did to workaround). And we can have either all branches or only
protected ones...

> By the way, I still haven’t understood why it would be
> necessary/advisable to erase all the old branches on Savannah. (I’m
> thinking about a few branches that may or may not be of historical
> interest, such as cvs/master and some of the dev/* branches.)

Note that this proposal is not about deleting anything for now. However
I never understood why we have both branches and tags for something
that's never going to change such as
 - cvs/HEAD <-> cvs/master
 - tarball/HEAD <-> tarball/master
Not changing is exactly the property of tags...

Jonas

signature.asc (499 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: mirror GitLab -> Savannah

Jonas Hahnfeld
In reply to this post by Jonas Hahnfeld
Am Donnerstag, den 14.05.2020, 20:31 +0200 schrieb Jonas Hahnfeld:

> To keep this short: I'd like to enable push mirroring from GitLab to
> Savannah for the following branches [1]:
>  - master
>  - release/unstable
>  - stable/*
>  - translation*
> This is a feature of GitLab and runs automatically in the background:
> https://gitlab.com/help/user/project/repository/repository_mirroring.md
>
> I've already created a new lilypod_bot user and requested access to the
> Savannah project. Unless somebody objects, I'll configure GitLab
> accordingly and paste the generated SSH key for the Savannah user.
Update on this one: I've tried to configure the necessary options, but
apparently it's broken on gitlab.com since this week:
https://gitlab.com/gitlab-org/gitlab/-/issues/216619

For now, I've manually pushed master to Savannah in order to update the
webpage with the link to the new issue tracker.

Jonas

signature.asc (499 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: mirror GitLab -> Savannah

Jonas Hahnfeld
Am Samstag, den 16.05.2020, 11:49 +0200 schrieb Jonas Hahnfeld:

> Am Donnerstag, den 14.05.2020, 20:31 +0200 schrieb Jonas Hahnfeld:
> > To keep this short: I'd like to enable push mirroring from GitLab to
> > Savannah for the following branches [1]:
> >  - master
> >  - release/unstable
> >  - stable/*
> >  - translation*
> > This is a feature of GitLab and runs automatically in the background:
> > https://gitlab.com/help/user/project/repository/repository_mirroring.md
> >
> > I've already created a new lilypod_bot user and requested access to the
> > Savannah project. Unless somebody objects, I'll configure GitLab
> > accordingly and paste the generated SSH key for the Savannah user.
>
> Update on this one: I've tried to configure the necessary options, but
> apparently it's broken on gitlab.com since this week:
> https://gitlab.com/gitlab-org/gitlab/-/issues/216619
The GitLab devs have identified and remedied the problem, the mirroring
is now working correctly since a few days.

Cheers
Jonas

signature.asc (499 bytes) Download Attachment