migration to GitLab

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

migration to GitLab

Jonas Hahnfeld
I've started preparation for migrating to GitLab. There has been no
activity for the past hours on SourceForge, please keep it that way.
Write access is still open, but I expect to disable it shortly.
Likewise for the repo, please don't push to Savannah anymore.

I'll keep you posted on the status.

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

Re: migration to GitLab

Jonas Hahnfeld
Am Sonntag, den 10.05.2020, 20:47 +0200 schrieb Jonas Hahnfeld:
> I've started preparation for migrating to GitLab. There has been no
> activity for the past hours on SourceForge, please keep it that way.
> Write access is still open, but I expect to disable it shortly.
> Likewise for the repo, please don't push to Savannah anymore.
>
> I'll keep you posted on the status.

All right, I populated the repository and started the script to migrate
the issues. In case you are a member of the group, it's possible to
watch the progress -- but please don't touch anything, in particular
refrain from creating any new issue.

Thanks
Jonas

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

Re: migration to GitLab

Dan Eble
On May 10, 2020, at 15:36, Jonas Hahnfeld <[hidden email]> wrote:
>
> All right, I populated the repository

When I try to fetch from gitlab with https, it prompts me to authenticate.  It's inconvenient.  Is it expected?  

Dan


Reply | Threaded
Open this post in threaded view
|

Re: migration to GitLab

Joram Berger
Hi Dan,

as far as I understand (from experience with other projects), you can
clone anonymously (and fetch without authentication then).
If you want to be able to push, you need to authenticate and then you
also need to authenticate for fetch or pull.
A way around that is to use the ssh urls and use ssh keys. In
combination with the ssh-agent, you can then enter your ssh key password
only once and push and pull afterwards.

As `git remote -v` lists two separate urls for fetch and push I suspect
there should be a way around that issue.

Cheers,
Joram

Reply | Threaded
Open this post in threaded view
|

Re: migration to GitLab

Dan Eble
On May 10, 2020, at 18:51, Joram Noeck <[hidden email]> wrote:
>
> as far as I understand (from experience with other projects), you can
> clone anonymously (and fetch without authentication then).
> If you want to be able to push, you need to authenticate and then you
> also need to authenticate for fetch or pull.
> A way around that is to use the ssh urls and use ssh keys. In
> combination with the ssh-agent, you can then enter your ssh key password
> only once and push and pull afterwards.

Thanks for the reply.  git configuration might be my problem, but I doubt it.  I've been using https to fetch and ssh to push to gnu.org repo for months (using the pushInsteadOf option).  Now I'm trying to fetch from the new lilypond repo with https and it prompts me for credentials.  I wonder if the new repo is configured not to allow anonymous fetching.

    $ git remote -v
    . . .
    origin https://gitlab.com/lilypond/lilypond.git (fetch)
    origin [hidden email]:lilypond/lilypond.git (push)
    $ git fetch origin
    Username for 'https://gitlab.com': ^C

Dan


Reply | Threaded
Open this post in threaded view
|

RE: migration to GitLab

lilypond-5
In reply to this post by Joram Berger


> -----Oorspronkelijk bericht-----
> Van: lilypond-devel <lilypond-devel-bounces+lilypond=[hidden email]>
> Namens Joram Noeck
> Verzonden: Monday, May 11, 2020 12:51 AM
> Aan: [hidden email]
> Onderwerp: Re: migration to GitLab
>
> Hi Dan,
>
> as far as I understand (from experience with other projects), you can clone
> anonymously (and fetch without authentication then).
> If you want to be able to push, you need to authenticate and then you also
> need to authenticate for fetch or pull.
> A way around that is to use the ssh urls and use ssh keys. In combination with
> the ssh-agent, you can then enter your ssh key password only once and push
> and pull afterwards.
>
> As `git remote -v` lists two separate urls for fetch and push I suspect there
> should be a way around that issue.
>
> Cheers,
> Joram
I can do a "clone https://gitlab.com/lilypond-issues/lilypond-trial.git" (with 5916 issues of which 11773 stil open, issues seems to be in here) without authentication without a problem.
However I can not do a "clone https://gitlab.com/lilypond/lilypond.git"
Is the lilypond git a public git?
In github all projects are public by default, but in gitlab they are private by default.
In lilypond I only see the project infrastructure is visible to me.
You can change this in Project->Settings->General->Visibility

Jaap de Wolff


Reply | Threaded
Open this post in threaded view
|

Re: migration to GitLab

Jonas Hahnfeld
In reply to this post by Dan Eble
Am Sonntag, den 10.05.2020, 18:24 -0400 schrieb Dan Eble:
> On May 10, 2020, at 15:36, Jonas Hahnfeld <
> [hidden email]
> > wrote:
> > All right, I populated the repository
>
> When I try to fetch from gitlab with https, it prompts me to authenticate.  It's inconvenient.  Is it expected?  

Yes, as Jaap noted lilypond/lilypond was private until a few minutes
ago. This was the easiest way to disable spam checking during
migration. As the script has finished, I've now made it public so
anonymous cloning should work.

Please allow me some time for a few manual tasks, in particular getting
everything ready for convenient contributing like setting up the
webhook that adds Patch::new to incoming merge requests. I'll post once
the project is ready to be used, including instructions how to convert
an existing development tree.

Thanks
Jonas

signature.asc (499 bytes) Download Attachment