Re: GitLab migration update

[Roland Knall <rknall () gmail com>]

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 <lomato () gmail com
> :

> On Tue, Aug 25, 2020 at 12:56 PM Peter Wu <peter () lekensteyn nl> 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, I wrote a small script that can be executed from your web
> > browser. See https://gitlab.com/wireshark/wireshark/-/issues/16806
> My wireshark repo on gitlab is not a fork of the main one (I've created it
> much earlier). Do you think the fork status can be forced on it as well?
> Just out of curiosity, I've already re-forked.
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
> Archives:    https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>              mailto:wireshark-dev-request () wireshark org
> ?subject=unsubscribe
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe