Re: [Wireshark-dev] GitLab migration update

2020-08-26 Thread Roland Knall 
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 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, 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 
> Archives:https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>  mailto:wireshark-dev-requ...@wireshark.org
> ?subject=unsubscribe
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] GitLab migration update

2020-08-25 Thread Dario Lombardo 
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, 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 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] GitLab migration update

2020-08-25 Thread Peter Wu 
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 warning that you'll sever the
> > relationship of any forked repositories:
> > 
> > https://docs.gitlab.com/ee/public_access/public_access.html#reducing-visibility
> > https://gitlab.com/gitlab-org/gitlab/-/issues/33358
> > https://gitlab.com/gitlab-org/gitlab/-/issues/22417
> > https://gitlab.com/gitlab-org/gitlab/-/issues/19111
> > 
> > If you do it from the API there's no warning. Unfortunately this
> > means that if you were proactive an forked
> > https://gitlab.com/wireshark/wireshark then you either need to
> > rename or remove your current repository and fork again. Sorry about
> > the hassle.
> 
> You don't have to do this. There is also the option to set "forked from" 
> repository with an API call.
> 
> With httpie you have to call:
> http POST 
> 'https://gitlab.com/api/v4/projects/%2Fwireshark/fork/7898047?access_token='
> 
> 7898047 is the ID of https://gitlab.com/wireshark/wireshark
> 
> You can create the API Token in your gitlab user profile -> 'Access Tokens'. 
> Before the call it could be necessary to
> remove the fork relationship (Project settings -> General -> Advanced -> 
> 'Remove fork relationship').

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
-- 
Kind regards,
Peter Wu
https://lekensteyn.nl
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] GitLab migration update

2020-08-24 Thread Uli Heilmeier 


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:
> 
> https://docs.gitlab.com/ee/public_access/public_access.html#reducing-visibility
> https://gitlab.com/gitlab-org/gitlab/-/issues/33358
> https://gitlab.com/gitlab-org/gitlab/-/issues/22417
> https://gitlab.com/gitlab-org/gitlab/-/issues/19111
> 
> If you do it from the API there's no warning. Unfortunately this means that 
> if you were proactive an forked https://gitlab.com/wireshark/wireshark then 
> you either need to rename or remove your current repository and fork again. 
> Sorry about the hassle.

You don't have to do this. There is also the option to set "forked from" 
repository with an API call.

With httpie you have to call:
http POST 
'https://gitlab.com/api/v4/projects/%2Fwireshark/fork/7898047?access_token='

7898047 is the ID of https://gitlab.com/wireshark/wireshark

You can create the API Token in your gitlab user profile -> 'Access Tokens'. 
Before the call it could be necessary to
remove the fork relationship (Project settings -> General -> Advanced -> 
'Remove fork relationship').


___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] GitLab migration update

2020-08-23 Thread Guy Harris 
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 access to Gerrit"?

> Bugzilla should be read-only as well. Each Bugzilla bug should have a 
> matching entry at https://gitlab.com/wireshark/wireshark/issues

The issue number of the most recent Wireshark bug appears to be the same as its 
Bugzilla bug number; is that a property true for all bugs?

Where is the link to the issues database from 
https://gitlab.com/wireshark/wireshark?  GitHub has one on the top-level page 
for GitHub repositories.
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

[Wireshark-dev] GitLab migration update

2020-08-23 Thread Gerald Combs 
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 the new 
UI because it wasn't displaying the migration banner.)

Bugzilla should be read-only as well. Each Bugzilla bug should have a matching 
entry at https://gitlab.com/wireshark/wireshark/issues


The migration went well except for one significant issue:

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:

https://docs.gitlab.com/ee/public_access/public_access.html#reducing-visibility
https://gitlab.com/gitlab-org/gitlab/-/issues/33358
https://gitlab.com/gitlab-org/gitlab/-/issues/22417
https://gitlab.com/gitlab-org/gitlab/-/issues/19111

If you do it from the API there's no warning. Unfortunately this means that if 
you were proactive an forked https://gitlab.com/wireshark/wireshark then you 
either need to rename or remove your current repository and fork again. Sorry 
about the hassle.


As mentioned in a previous email I'll be hosting a remote Developer Den 
tomorrow morning and Tuesday morning PDT. Tomorrow's invitation is attached.
BEGIN:VCALENDAR
PRODID:-//zoom.us//iCalendar Event//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:PUBLISH
CLASS:PUBLIC
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
TZURL:http://tzurl.org/zoneinfo-outlook/America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20200821T220324Z
DTSTART;TZID=America/Los_Angeles:20200824T09
DTEND;TZID=America/Los_Angeles:20200824T12
SUMMARY:Wireshark Developer Den
UID:20200821T220324Z-96323346131@fe80:0:0:0:c3b:3ff:fe80:9023eth0
TZID:America/Los_Angeles
DESCRIPTION:Gerald Combs is inviting you to a scheduled Zoom meeting.\n\n
 Join Zoom Meeting\nhttps://riverbed.zoom.us/j/96323346131?pwd=TXN0YUtISi
 t2UEczNE8zUmZtUDBRdz09\n\nMeeting ID: 963 2334 6131\nPasscode: 892934\nO
 ne tap mobile\n+16699006833\,\,96323346131#\,\,\,\,\,\,0#\,\,892934# US 
 (San Jose)\n+13462487799\,\,96323346131#\,\,\,\,\,\,0#\,\,892934# US (Ho
 uston)\n\nDial by your location\n+1 669 900 6833 US (San Jose)\n
 +1 346 248 7799 US (Houston)\n+1 253 215 8782 US (Tacoma
 )\n+1 312 626 6799 US (Chicago)\n+1 929 205 6099 US (New
  York)\n+1 301 715 8592 US (Germantown)\n888 475 4499 US
  Toll-free\n877 853 5257 US Toll-free\n+43 72 011 5988 A
 ustria\n+43 120 609 3072 Austria\n+43 12 535 501 Austria
 \n+43 12 535 502 Austria\n+43 670 309 0165 Austria\n
 0 800 104 430 Austria Toll-free\n0 800 102 309 Austria Toll-
 free\n+33 1 8699 5831 France\n+33 1 7037 2246 France\n  
   +33 1 7037 9729 France\n+33 1 7095 0103 France\n+3
 3 1 7095 0350 France\n0 800 944 049 France Toll-free\n0 
 800 940 415 France Toll-free\n+49 69 3807 9883 Germany\n
 +49 695 050 2596 Germany\n+49 69 7104 9922 Germany\n+49 
 30 5679 5800 Germany\n0 800 000 6954 Germany Toll-free\n
 0 800 1800 150 Germany Toll-free\n0 800 000 1590 Germany Toll-fr
 ee\n+39 021 241 28 823 Italy\n+39 069 480 6488 Italy\n  
   +39 020 066 7245 Italy\n800 125 671 Italy Toll-free\n 
800 790 654 Italy Toll-free\n800 088 202 Italy Toll-free\n   
  +351 308 804 188 Portugal\n+351 308 810 988 Portugal\n 
+351 211 202 618 Portugal\n800 780 072 Portugal Toll-free\n  
   800 780 052 Portugal Toll-free\n+48 22 307 3488 Poland\n  
   +48 22 398 7356 Poland\n+48 22 306 5342 Poland\n00
  800 321 1464 Poland Toll-free\n00 800 112 5171 Poland Toll-free
 \n+34 91 787 0058 Spain\n+34 917 873 431 Spain\n
 +34 84 368 5025 Spain\n800 906 063 Spain Toll-free\n900 
 053 647 Spain Toll-free\n800 654 404 Spain Toll-free\n+4
 6 8 5016 3827 Sweden\n+46 8 5050 0828 Sweden\n+46 8 5050
  0829 Sweden\n+46 8 5052 0017 Sweden\n+46 850 539 728 Sw
 eden\n+46 8 4468 2488 Sweden\n0 200 123 720 Sweden Toll-
 free\n0 200 123 514 Sweden Toll-free\n+41 22 591 01 56 S
 witzerland\n+41 31 528 09 88 Switzerland\n+41 43 210 70 
 42 Switzerland\n+41 43 210 71 08 Switzerland\n+41 44 529
  92 72 Switzerland\n

Re: [Wireshark-dev] GitLab migration update

2020-04-06 Thread Gerald Combs 
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, create merge requests, etc. If you'd like to try 
>> out a feature that requires a configuration change, let me know.
> 
> Having setup an account and the triangular workflow I’ve pushed a dummy 
> change. For that I receive an email that the pipeline has failed (obviously).
> The header of this email though has “To: undisclosed-recipients:;”, which 
> causes it to land in the spam folder. That doesn’t seem right.

It looks like that's an open bug. 
https://gitlab.com/gitlab-org/gitlab/-/issues/16507
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] GitLab migration update

2020-04-06 Thread Dario Lombardo 
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) instead of "internal" (implicit for logged users).
>
> The project is public, you can access it even when not logged in:
> https://gitlab-test.wireshark.org/wireshark/wireshark


Yes, but I guess we should be added as internal developers to the project.
This way the project will show up in my projects list and I will be able to
merge the MR (I'm talking about the regular operations).


>
>
> GitLab CI is not enabled however because no runners are configured.
> This is one downside of self-hosted GitLab, see
>
> https://gitlab.com/wireshark/gitlab-migration/-/wikis/SaaS-or-Self-Managed%3F


If we want to test the whole stack, without using more machines, the
gitlab-runner can be installed on the same machine as gitlab itself. Not
optimal, but functional.


>
> --
> Kind regards,
> Peter Wu
> https://lekensteyn.nl
> ___
> Sent via:Wireshark-dev mailing list 
> Archives:https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
>  mailto:wireshark-dev-requ...@wireshark.org
> ?subject=unsubscribe



-- 

Naima is online.
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] GitLab migration update

2020-04-06 Thread Jaap Keuter 

> 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 requires a configuration change, let me know.

Having setup an account and the triangular workflow I’ve pushed a dummy change. 
For that I receive an email that the pipeline has failed (obviously).
The header of this email though has “To: undisclosed-recipients:;”, which 
causes it to land in the spam folder. That doesn’t seem right.

Thanks,
Jaap

___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] GitLab migration update

2020-04-05 Thread Peter Wu 
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 is public, you can access it even when not logged in:
https://gitlab-test.wireshark.org/wireshark/wireshark

GitLab CI is not enabled however because no runners are configured.
This is one downside of self-hosted GitLab, see
https://gitlab.com/wireshark/gitlab-migration/-/wikis/SaaS-or-Self-Managed%3F
-- 
Kind regards,
Peter Wu
https://lekensteyn.nl
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] GitLab migration update

2020-04-04 Thread Dario Lombardo 
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 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).

On Sun, Apr 5, 2020 at 12:43 AM Gerald Combs  wrote:

> 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 <
> http://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 didn't add Google initially because it's non-trivial compared to GitLab
> and GitHub. It should be working now.
>


-- 

Naima is online.
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] GitLab migration update

2020-04-04 Thread Gerald Combs 
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 didn't add Google initially because it's non-trivial compared to GitLab and 
GitHub. It should be working now.
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Re: [Wireshark-dev] GitLab migration update

2020-04-04 Thread Dario Lombardo 
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.
>

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?

>
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

[Wireshark-dev] GitLab migration update

2020-04-03 Thread Gerald Combs 
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 integrated 
development environment. I don't have a solid schedule in place yet (see 
below), but hope to start migrating each service in the next few weeks.

A migration wiki is up and running at 
https://gitlab.com/wireshark/gitlab-migration/-/wikis/home which covers and 
expands on the issues discussed in the -dev mailing list thread. The "Code 
Review Comparison" section at 
https://gitlab.com/wireshark/gitlab-migration/-/wikis/Code-Review-(Gerrit) is 
probably of most interest to developers, since it details the various workflow 
differences between Gerrit and GitLab.

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.

In the near term we need to decide whether or not we want to self-host or use 
gitlab.com. An overview of the differences between the two options can be found 
at 
https://gitlab.com/wireshark/gitlab-migration/-/wikis/SaaS-or-Self-Managed%3F. 
Once that has been decided we'll have a better idea of our migration 
requirements and what our timeline will be.
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe