Re: [Wireshark-dev] GitLab migration update

Peter posted the instructions somewhere for that (either on the main wiki, or the main project). Have to look it up. Basically you have to remove the association of your fork with the "old" version, and then reset it. cheers Am Di., 25. Aug. 2020 um 23:01 Uhr schrieb Dario Lombardo : > > > On Tu

Re: [Wireshark-dev] GitLab migration update

On Tue, Aug 25, 2020 at 12:56 PM Peter Wu wrote: > > It looks like you have to delete the old stale fork relationship first, > otherwise you will end up with a 409 Conflict error ("Project already > forked"). > > To automate fixing the fork status without requiring creation of an > access token,

Re: [Wireshark-dev] GitLab migration update

On Mon, Aug 24, 2020 at 11:24:09AM +0200, Uli Heilmeier wrote: > > > Am 24.08.20 um 06:33 schrieb Gerald Combs: > > > The issue creation script made the repository private in order to > > avoid rate limiting. If you do this through the web interface, > > you're presented with a nice, clear warni

Re: [Wireshark-dev] GitLab migration update

Am 24.08.20 um 06:33 schrieb Gerald Combs: > The issue creation script made the repository private in order to avoid rate > limiting. If you do this through the web interface, you're presented with a > nice, clear warning that you'll sever the relationship of any forked > repositories: > > h

Re: [Wireshark-dev] GitLab migration update

On Aug 23, 2020, at 9:33 PM, Gerald Combs wrote: > You can still comment on Gerrit changes, but it should otherwise be > read-only. SSH access is still enabled for now in order to make it easier to > migrate changes. I'll shut it off in the next couple of weeks. Does "it" mean "Gerrit" or "SSH

[Wireshark-dev] GitLab migration update

The Gerrit+Bugzilla portion of the GitLab migration is now complete. You can still comment on Gerrit changes, but it should otherwise be read-only. SSH access is still enabled for now in order to make it easier to migrate changes. I'll shut it off in the next couple of weeks. (I also disabled t

Re: [Wireshark-dev] GitLab migration update

On 4/6/20 12:29 AM, Jaap Keuter wrote: > >> On 4 Apr 2020, at 01:46, Gerald Combs > > wrote: >> >> We also have a self-hosted test server up and running at  >> https://gitlab-test.wireshark.org . Feel >> free to create an account, c

Re: [Wireshark-dev] GitLab migration update

On Sun, Apr 5, 2020 at 11:57 PM Peter Wu wrote: > On Sun, Apr 05, 2020 at 01:10:37AM +0200, Dario Lombardo wrote: > > However, I logged in in via github and then connected my google account, > > but no projects show up. Maybe the project has been set up as "private" > > (explicit allowance) inste

Re: [Wireshark-dev] GitLab migration update

> On 4 Apr 2020, at 01:46, Gerald Combs wrote: > > We also have a self-hosted test server up and running at > https://gitlab-test.wireshark.org . Feel > free to create an account, create merge requests, etc. If you'd like to try > out a feature that require

Re: [Wireshark-dev] GitLab migration update

On Sun, Apr 05, 2020 at 01:10:37AM +0200, Dario Lombardo wrote: > However, I logged in in via github and then connected my google account, > but no projects show up. Maybe the project has been set up as "private" > (explicit allowance) instead of "internal" (implicit for logged users). The project

Re: [Wireshark-dev] GitLab migration update

I get Signing in using your Google account without a pre-existing GitLab account is not allowed. Create a GitLab account first, and then connect it to your Google account. I guess this is how gitlab works. I've never tried that before. However, I logged in in via github and then connected my goo

Re: [Wireshark-dev] GitLab migration update

On 4/4/20 9:16 AM, Dario Lombardo wrote: > Hi Gerald > The test server allows me to log in with github and gitlab.com > account. Gerrit allowed google account sso and gitlab.com > itself allows that. > Is that wanted? Can we allow google login as well? I d

Re: [Wireshark-dev] GitLab migration update

On Sat, Apr 4, 2020, 01:47 Gerald Combs wrote: > > We also have a self-hosted test server up and running at > https://gitlab-test.wireshark.org. Feel free to create an account, create > merge requests, etc. If you'd like to try out a feature that requires a > configuration change, let me know. >

[Wireshark-dev] GitLab migration update

Back in October I proposed migrating Gerrit, Bugzilla, Buildbot, and Moin to GitLab: https://www.wireshark.org/lists/wireshark-dev/201910/msg6.html I think we're ready to work on the migration in earnest. As stated in the email this will give us a more modern, standardized, and tightly inte