Re: Registering account in gitlab.haskell.org

[ccycle]

Now I can successfully log in. Thank you for approving!
On Feb 6, 2023 19:48 +0900, Bryan Richter , wrote:
> My fault. I chose the wrong "confirmation" option in the admin panel. It is 
> the one that manually confirms your email address.
>
> Now I've also approved your account!
>
> > On Mon, 6 Feb 2023 at 12:40, ccycle  wrote:
> > > Thank you, but now I got same error and cannot log in. Will I able to log 
> > > in after a while?
> > > On Feb 6, 2023 16:42 +0900, Bryan Richter , 
> > > wrote:
> > > > You've been approved! Sorry for the hiccup, there was a spam problem on 
> > > > the server for a while.
> > > >
> > > > > On Mon, 6 Feb 2023 at 08:41, ccycle  wrote:
> > > > > > Hi, I'm new to ghc-devs@haskell.org and would like to report a bug 
> > > > > > in GHC that I have encountered. I tried to log in with an account 
> > > > > > registered in gitlab.haskell.org to create an issue and then I got 
> > > > > > the following error:
> > > > > >
> > > > > > > Your account is pending approval from your GitLab administrator 
> > > > > > > and hence blocked. Please contact your GitLab administrator if 
> > > > > > > you think this is an error.
> > > > > >
> > > > > > Could someone approve my account? My account pending approval is:
> > > > > >
> > > > > > Username: ccycle
> > > > > > Email: ccycle...@gmail.com
> > > > > >
> > > > > >
> > > > > > ___
> > > > > > ghc-devs mailing list
> > > > > > ghc-devs@haskell.org
> > > > > > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: Registering account in gitlab.haskell.org

[Bryan Richter via ghc-devs]

My fault. I chose the wrong "confirmation" option in the admin panel. It is
the one that manually confirms your email address.

Now I've also approved your account!

On Mon, 6 Feb 2023 at 12:40, ccycle  wrote:

> Thank you, but now I got same error and cannot log in. Will I able to log
> in after a while?
> On Feb 6, 2023 16:42 +0900, Bryan Richter ,
> wrote:
>
> You've been approved! Sorry for the hiccup, there was a spam problem on
> the server for a while.
>
> On Mon, 6 Feb 2023 at 08:41, ccycle  wrote:
>
>> Hi, I'm new to ghc-devs@haskell.org <https://mailto:ghc-devs@haskell.org> and
>> would like to report a bug in GHC that I have encountered. I tried to log
>> in with an account registered in gitlab.haskell.org to create an issue
>> and then I got the following error:
>>
>> > Your account is pending approval from your GitLab administrator and
>> hence blocked. Please contact your GitLab administrator if you think this
>> is an error.
>>
>> Could someone approve my account? My account pending approval is:
>>
>> Username: ccycle
>> Email: ccycle...@gmail.com
>>
>>
>> ___
>> ghc-devs mailing list
>> ghc-devs@haskell.org
>> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>>
>
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: Registering account in gitlab.haskell.org

[ccycle]

Thank you, but now I got same error and cannot log in. Will I able to log in 
after a while?
On Feb 6, 2023 16:42 +0900, Bryan Richter , wrote:
> You've been approved! Sorry for the hiccup, there was a spam problem on the 
> server for a while.
>
> > On Mon, 6 Feb 2023 at 08:41, ccycle  wrote:
> > > Hi, I'm new to ghc-devs@haskell.org and would like to report a bug in GHC 
> > > that I have encountered. I tried to log in with an account registered in 
> > > gitlab.haskell.org to create an issue and then I got the following error:
> > >
> > > > Your account is pending approval from your GitLab administrator and 
> > > > hence blocked. Please contact your GitLab administrator if you think 
> > > > this is an error.
> > >
> > > Could someone approve my account? My account pending approval is:
> > >
> > > Username: ccycle
> > > Email: ccycle...@gmail.com
> > >
> > >
> > > ___
> > > ghc-devs mailing list
> > > ghc-devs@haskell.org
> > > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: Registering account in gitlab.haskell.org

[Bryan Richter via ghc-devs]

You've been approved! Sorry for the hiccup, there was a spam problem on the
server for a while.

On Mon, 6 Feb 2023 at 08:41, ccycle  wrote:

> Hi, I'm new to ghc-devs@haskell.org <https://mailto:ghc-devs@haskell.org> and
> would like to report a bug in GHC that I have encountered. I tried to log
> in with an account registered in gitlab.haskell.org to create an issue
> and then I got the following error:
>
> > Your account is pending approval from your GitLab administrator and
> hence blocked. Please contact your GitLab administrator if you think this
> is an error.
>
> Could someone approve my account? My account pending approval is:
>
> Username: ccycle
> Email: ccycle...@gmail.com
>
>
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Registering account in gitlab.haskell.org

[ccycle]

Hi, I'm new to ghc-devs@haskell.org and would like to report a bug in GHC that 
I have encountered. I tried to log in with an account registered in 
gitlab.haskell.org to create an issue and then I got the following error:

> Your account is pending approval from your GitLab administrator and hence 
> blocked. Please contact your GitLab administrator if you think this is an 
> error.

Could someone approve my account? My account pending approval is:

Username: ccycle
Email: ccycle...@gmail.com


___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: Two-factor authentication enforced on gitlab.haskell.org

[Ben Gamari]

Ben Gamari  writes:

> Hi all,
>
> Due to a recent up-tick in spam activity, we have started enforcing
> two-factor authentication on gitlab.haskell.org. We hope that this isn't
> too much of a burden, but do let us know if so and we can evaluate other
> options.
>
Hi all,

Due to user response we have reverted the two-factor authentication
requirement and will instead manually review new account creations for
now. Do feel free to ping either Matt, Andreas, or I via IRC or email if
you attempt to create an account and your request sits unapproved for
more than an hour or two.

Hopefully in the near term we will be able to able to find less onerous
way of dealing with the growing spam problem.

Cheers,

- Ben



signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Two-factor authentication enforced on gitlab.haskell.org

[Ben Gamari]

Hi all,

Due to a recent up-tick in spam activity, we have started enforcing
two-factor authentication on gitlab.haskell.org. We hope that this isn't
too much of a burden, but do let us know if so and we can evaluate other
options.

Cheers,

- Ben


signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: gitlab.haskell.org

[Ben Gamari]

Tom Ellis  writes:

> If a sponsor (perhaps the HF) could pay for GitLab to host the service
> on our behalf would that be helpful?  I don't know whether GHC
> development relies deeply on some aspect of our self-hosted setup.
> (I suspect it does because otherwise we'd likely be using a free
> GitLab tier for open source organisations, but I thought the question
> was worth asking.)
>
Migrating towards the SaaS offering is indeed quite enticing. However,
last time I checked it wasn't clear to me that it was feasible in our case.
The problem isn't the cost as we could in principle request
Ultimate-level access to the SaaS via GitLab's FOSS program (which is
the same program through which we have our current self-hosted license).

The original reason was that we needed to patch
GitLab during the migration away from Trac to ensure that ticket
metadata was faithfully preserved. While at this point we are running
a completely unmodified GitLab instance, my understanding is that there
are a few sticking points that would make migration to the SaaS
difficult:

 * the default 10 GB storage quota is extremely small when one considers
   the size of our CI logs, artifacts, and Docker images

 * some administrative and debugging tasks sadly become difficult
   without server access (e.g. I've sometimes found it helpful to look
   at the server log while debugging CI issues)

 * Response time of GitLab.com's search functionality has historically
   been extremely variable, rendering it at times unusable. I'm not sure
   whether this has improved recently.

The first point is especially concerning and has been the primary source
of our troubles in self-hosting. As long as we don't run out of storage,
GitLab administration tends to be a very minor time commitment (an hour
or so a month dealing with spam and upgrading). Thankfully, after today
I think we have sufficiently over-provisioned to avoid any future
storage issues for the foreseeable future.

Cheers,

- Ben


signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: gitlab.haskell.org

[Tom Ellis]

If a sponsor (perhaps the HF) could pay for GitLab to host the service
on our behalf would that be helpful?  I don't know whether GHC
development relies deeply on some aspect of our self-hosted setup.
(I suspect it does because otherwise we'd likely be using a free
GitLab tier for open source organisations, but I thought the question
was worth asking.)

Tom

On Mon, Oct 18, 2021 at 10:12:07AM +0100, Matthew Pickering wrote:
> I restarted the service and things appear to be working atm.. but I
> don't understand how the volumes are configured on the machine so will
> have to wait for Ben to fix it properly.
> 
> On Mon, Oct 18, 2021 at 9:11 AM Zubin Duggal  wrote:
> > It is not just you, Gitlab has been unstable since yesterday due to a
> > lack of disk space.
> >
> > On 21/10/18 07:29, Simon Peyton Jones via ghc-devs wrote:
> > >I'm getting "502" from gitlab.haskell.org.   Is it just me?
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: gitlab.haskell.org

[Matthew Pickering]

I restarted the service and things appear to be working atm.. but I
don't understand how the volumes are configured on the machine so will
have to wait for Ben to fix it properly.

On Mon, Oct 18, 2021 at 9:11 AM Zubin Duggal  wrote:
>
> It is not just you, Gitlab has been unstable since yesterday due to a
> lack of disk space.
>
> On 21/10/18 07:29, Simon Peyton Jones via ghc-devs wrote:
> >I'm getting "502" from gitlab.haskell.org.   Is it just me?
> >
> >Thanks
> >
> >Simon
> >
> >PS: I am leaving Microsoft at the end of November 2021, at which point 
> >simo...@microsoft.com<mailto:simo...@microsoft.com> will cease to work.  Use 
> >simon.peytonjo...@gmail.com<mailto:simon.peytonjo...@gmail.com> instead.  
> >(For now, it just forwards to simo...@microsoft.com.)
> >
>
> >___
> >ghc-devs mailing list
> >ghc-devs@haskell.org
> >http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: gitlab.haskell.org

[Zubin Duggal]

It is not just you, Gitlab has been unstable since yesterday due to a
lack of disk space.

On 21/10/18 07:29, Simon Peyton Jones via ghc-devs wrote:

I'm getting "502" from gitlab.haskell.org.   Is it just me?

Thanks

Simon

PS: I am leaving Microsoft at the end of November 2021, at which point 
simo...@microsoft.com<mailto:simo...@microsoft.com> will cease to work.  Use 
simon.peytonjo...@gmail.com<mailto:simon.peytonjo...@gmail.com> instead.  (For now, 
it just forwards to simo...@microsoft.com.)




___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs


___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

gitlab.haskell.org

[Simon Peyton Jones via ghc-devs]

I'm getting "502" from gitlab.haskell.org.   Is it just me?

Thanks

Simon

PS: I am leaving Microsoft at the end of November 2021, at which point 
simo...@microsoft.com<mailto:simo...@microsoft.com> will cease to work.  Use 
simon.peytonjo...@gmail.com<mailto:simon.peytonjo...@gmail.com> instead.  (For 
now, it just forwards to simo...@microsoft.com.)

___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: gitlab.haskell.org certificate expired?

[Ben Gamari]

Daniel Gröber  writes:

> Hi,
>
> indeed looks to be broken, even though my browser still doesn't complain
> the openssl command sure does:
>
For the record, the problem was a NixOS bug [1] which resulted in the
automated renewal failing. The problem has been worked around for now
and should be fixed upstream soon.

Cheers,

- Ben

[1] https://github.com/NixOS/nixpkgs/issues/101445


signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: gitlab.haskell.org certificate expired?

[Ben Gamari]

Richard Eisenberg  writes:

> Hi Ben,
>
> It looks like the Let's Encrypt certificate for gitlab.haskell.org 
> <http://gitlab.haskell.org/> has expired, as of about 15 minutes ago. I guess 
> it's time to renew.
>
Thanks for the ping. In principle this happens automatically but it
seems that we were hit by a NixOS bug [1]. Anyways, I've worked around
it for now and things should be back to normal.

Cheers,

- Ben

[1] https://github.com/NixOS/nixpkgs/issues/101445


signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: gitlab.haskell.org certificate expired?

[Daniel Gröber]

Hi,

indeed looks to be broken, even though my browser still doesn't complain
the openssl command sure does:

$ openssl s_client -showcerts -verify_return_error -4 -connect 
gitlab.haskell.org:443 < /dev/null
CONNECTED(0003)
depth=2 O = Digital Signature Trust Co., CN = DST Root CA X3
verify return:1
depth=1 C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3
verify return:1
depth=0 CN = gitlab.haskell.org
verify error:num=10:certificate has expired
notAfter=Feb 14 23:21:04 2021 GMT
140217764021376:error:1416F086:SSL 
routines:tls_process_server_certificate:certificate verify 
failed:../ssl/statem/statem_clnt.c:1915:
---
no peer certificate available
---
No client certificate CA names sent
Server Temp Key: X25519, 253 bits
---
SSL handshake has read 2594 bytes and written 317 bytes
Verification error: certificate has expired
---
New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 10 (certificate has expired)
---

FYI I wrote a super simple monitoring script using faketime+openssl to
prevent this sort of thing from happening in case you guys are interested:

https://meta.it-syndikat.org/t/tls-monitoring-fur-unsere-infrastruktur/2492

The description is in German unfortunately, but the script itself is
commented in English of course ;)

We install this as a cron.daily job and use a cron monitoring make sure the
script runs, but I suspect if you're not worried about the "it actually
ran" part cron's default emails would work just as well.

--Daniel

On Sun, Feb 14, 2021 at 11:37:45PM +, Richard Eisenberg wrote:
> Hi Ben,
> 
> It looks like the Let's Encrypt certificate for gitlab.haskell.org 
> <http://gitlab.haskell.org/> has expired, as of about 15 minutes ago. I guess 
> it's time to renew.
> 
> Thanks,
> Richard
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: IP/key change for gitlab.haskell.org?

[Stefan Schulze Frielinghaus]

Just in case someone else runs into a similar problem as mine which is
related to the SSH key change:

Removing the old SSH fingerprint from known_hosts file and then running
git resulted in an error for me and the culprit seems to be SSH:

$ ssh -vvvT g...@gitlab.haskell.org
...
debug3: send packet: type 30
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
Connection reset by 139.178.85.33 port 22

If I manually add

gitlab.haskell.org,139.178.85.33 ssh-ed25519 
C3NzaC1lZDI1NTE5IA7ltOZyaULDgxE3Vw6RgQVp+OPKQi79ssUenbhdWy36

to $HOME/.ssh/known_hosts, then SSH works again for me and consequently
git also.  I retrieved the known_hosts file entry manually via

$ ssh-keyscan gitlab.haskell.org >> $HOME/.ssh/known_hosts

which interestingly works without any problem.  Note, I'm running a
stock Fedora 32 without any SSH configuration changes except adding my
SSH key.  This is still kind of mystic to me and so far I couldn't
figure out why this is the case, but at least it solves my problem.

Hope this helps in case someone else runs into the same problem.

Cheers,
Stefan


On Thu, Jun 25, 2020 at 11:41:12AM +0100, Richard Eisenberg wrote:
> An innocent `git push` yielded this today:
> 
> @@@
> @   WARNING: POSSIBLE DNS SPOOFING DETECTED!  @
> @@@
> The ED25519 host key for gitlab.haskell.org has changed,
> and the key for the corresponding IP address 139.178.85.33
> is unknown. This could either mean that
> DNS SPOOFING is happening or the IP address for the host
> and its host key have changed at the same time.
> @@@
> @WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
> @@@
> IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
> Someone could be eavesdropping on you right now (man-in-the-middle attack)!
> It is also possible that a host key has just been changed.
> The fingerprint for the ED25519 key sent by the remote host is
> SHA256:/dI7zsBRZNPB+0TqskF7rSaZ/LhQw0cF4c5W+4uMlRo.
> Please contact your system administrator.
> Add correct host key in /Users/rae/.ssh/known_hosts to get rid of this 
> message.
> Offending ED25519 key in /Users/rae/.ssh/known_hosts:21
> ED25519 host key for gitlab.haskell.org has changed and you have requested 
> strict checking.
> Host key verification failed.
> 
> I know the server had a rough weekend. Is this a natural consequence, or is 
> something fishy going on?
> 
> Thanks,
> Richard
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: IP/key change for gitlab.haskell.org?

[Ben Gamari]

On June 25, 2020 6:41:12 AM EDT, Richard Eisenberg  wrote:
>An innocent `git push` yielded this today:
>
>@@@
>@   WARNING: POSSIBLE DNS SPOOFING DETECTED!  @
>@@@
>The ED25519 host key for gitlab.haskell.org has changed,
>and the key for the corresponding IP address 139.178.85.33
>is unknown. This could either mean that
>DNS SPOOFING is happening or the IP address for the host
>and its host key have changed at the same time.
>@@@
>@WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
>@@@
>IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
>Someone could be eavesdropping on you right now (man-in-the-middle
>attack)!
>It is also possible that a host key has just been changed.
>The fingerprint for the ED25519 key sent by the remote host is
>SHA256:/dI7zsBRZNPB+0TqskF7rSaZ/LhQw0cF4c5W+4uMlRo.
>Please contact your system administrator.
>Add correct host key in /Users/rae/.ssh/known_hosts to get rid of this
>message.
>Offending ED25519 key in /Users/rae/.ssh/known_hosts:21
>ED25519 host key for gitlab.haskell.org has changed and you have
>requested strict checking.
>Host key verification failed.
>
>I know the server had a rough weekend. Is this a natural consequence,
>or is something fishy going on?
>
>Thanks,
>Richard
>___
>ghc-devs mailing list
>ghc-devs@haskell.org
>http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Yes, as Simon pointed out this is expected. My apologies for the incovenience.

Cheers,

- Ben 
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: IP/key change for gitlab.haskell.org?

[Simon Jakobi via ghc-devs]

Hi Richard,

Ben had pointed out this issue in
https://mail.haskell.org/pipermail/ghc-devs/2020-June/019000.html

On my system I used the command

ssh-keygen -f "/home/simon/.ssh/known_hosts" -R gitlab.haskell.org

to remove the problematic key.

The next `git pull` then included a prompt to add the new key.

Cheers,
Simon

Am Do., 25. Juni 2020 um 12:41 Uhr schrieb Richard Eisenberg 
:
>
> An innocent `git push` yielded this today:
>
> @@@
> @   WARNING: POSSIBLE DNS SPOOFING DETECTED!  @
> @@@
> The ED25519 host key for gitlab.haskell.org has changed,
> and the key for the corresponding IP address 139.178.85.33
> is unknown. This could either mean that
> DNS SPOOFING is happening or the IP address for the host
> and its host key have changed at the same time.
> @@@
> @WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
> @@@
> IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
> Someone could be eavesdropping on you right now (man-in-the-middle attack)!
> It is also possible that a host key has just been changed.
> The fingerprint for the ED25519 key sent by the remote host is
> SHA256:/dI7zsBRZNPB+0TqskF7rSaZ/LhQw0cF4c5W+4uMlRo.
> Please contact your system administrator.
> Add correct host key in /Users/rae/.ssh/known_hosts to get rid of this 
> message.
> Offending ED25519 key in /Users/rae/.ssh/known_hosts:21
> ED25519 host key for gitlab.haskell.org has changed and you have requested 
> strict checking.
> Host key verification failed.
>
> I know the server had a rough weekend. Is this a natural consequence, or is 
> something fishy going on?
>
> Thanks,
> Richard
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

IP/key change for gitlab.haskell.org?

[Richard Eisenberg]

An innocent `git push` yielded this today:

@@@
@   WARNING: POSSIBLE DNS SPOOFING DETECTED!  @
@@@
The ED25519 host key for gitlab.haskell.org has changed,
and the key for the corresponding IP address 139.178.85.33
is unknown. This could either mean that
DNS SPOOFING is happening or the IP address for the host
and its host key have changed at the same time.
@@@
@WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ED25519 key sent by the remote host is
SHA256:/dI7zsBRZNPB+0TqskF7rSaZ/LhQw0cF4c5W+4uMlRo.
Please contact your system administrator.
Add correct host key in /Users/rae/.ssh/known_hosts to get rid of this message.
Offending ED25519 key in /Users/rae/.ssh/known_hosts:21
ED25519 host key for gitlab.haskell.org has changed and you have requested 
strict checking.
Host key verification failed.

I know the server had a rough weekend. Is this a natural consequence, or is 
something fishy going on?

Thanks,
Richard
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: gitlab.haskell.org spam issues

[Takenobu Tani]

Thanks always, Ömer, Matthew, Ben :)

Regards,
Takenobu

On Sun, Jan 12, 2020 at 9:10 PM Matthew Pickering
 wrote:
>
> There are still *a lot* of spam users though, i'm not sure what we can
> do to tackle this.
>
> On Sun, Jan 12, 2020 at 12:09 PM Ben Gamari  wrote:
> >
> > Takenobu Tani  writes:
> >
> > > They are also in snippets:
> > >
> > >   https://gitlab.haskell.org/explore/snippets
> > >
> > I have handled these. Thanks Takenobu!
> >
> > Cheers,
> >
> > - Ben
> > ___
> > ghc-devs mailing list
> > ghc-devs@haskell.org
> > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: gitlab.haskell.org spam issues

[Matthew Pickering]

There are still *a lot* of spam users though, i'm not sure what we can
do to tackle this.

On Sun, Jan 12, 2020 at 12:09 PM Ben Gamari  wrote:
>
> Takenobu Tani  writes:
>
> > They are also in snippets:
> >
> >   https://gitlab.haskell.org/explore/snippets
> >
> I have handled these. Thanks Takenobu!
>
> Cheers,
>
> - Ben
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: gitlab.haskell.org spam issues

[Ben Gamari]

Takenobu Tani  writes:

> They are also in snippets:
>
>   https://gitlab.haskell.org/explore/snippets
>
I have handled these. Thanks Takenobu!

Cheers,

- Ben


signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: gitlab.haskell.org spam issues

[Matthew Pickering]

I just went through the "report abuse" queue and deleted users as
reported by Takenobu.

On Sun, Jan 12, 2020 at 10:01 AM Ömer Sinan Ağacan  wrote:
>
> I just deleted the user with their messages.
>
> I don't see a delete link in snippets, so not sure how to delete those.
>
> Ömer
>
> Takenobu Tani , 12 Oca 2020 Paz, 06:09
> tarihinde şunu yazdı:
> >
> > They are also in snippets:
> >
> >   https://gitlab.haskell.org/explore/snippets
> >
> > Regards,
> > Takenobu
> >
> > On Sun, Jan 12, 2020 at 7:08 AM Ryan Scott  wrote:
> > >
> > > There appears to be an account [1] that is submitting spam as GitLab 
> > > issues. I've noticed the following spam issues so far:
> > >
> > > * https://gitlab.haskell.org/ghc/ghc/issues/17664
> > > * https://gitlab.haskell.org/ghc/ghc/issues/17666
> > > * https://gitlab.haskell.org/haskell/ghcup/issues/125
> > > * https://gitlab.haskell.org/haskell/ghcup/issues/127
> > > * https://gitlab.haskell.org/haskell/ghcup/issues/129
> > >
> > > Best,
> > > Ryan S.
> > > -
> > > [1] https://gitlab.haskell.org/nunikonaza88
> > > ___
> > > ghc-devs mailing list
> > > ghc-devs@haskell.org
> > > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
> > ___
> > ghc-devs mailing list
> > ghc-devs@haskell.org
> > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: gitlab.haskell.org spam issues

[Ömer Sinan Ağacan]

I just deleted the user with their messages.

I don't see a delete link in snippets, so not sure how to delete those.

Ömer

Takenobu Tani , 12 Oca 2020 Paz, 06:09
tarihinde şunu yazdı:
>
> They are also in snippets:
>
>   https://gitlab.haskell.org/explore/snippets
>
> Regards,
> Takenobu
>
> On Sun, Jan 12, 2020 at 7:08 AM Ryan Scott  wrote:
> >
> > There appears to be an account [1] that is submitting spam as GitLab 
> > issues. I've noticed the following spam issues so far:
> >
> > * https://gitlab.haskell.org/ghc/ghc/issues/17664
> > * https://gitlab.haskell.org/ghc/ghc/issues/17666
> > * https://gitlab.haskell.org/haskell/ghcup/issues/125
> > * https://gitlab.haskell.org/haskell/ghcup/issues/127
> > * https://gitlab.haskell.org/haskell/ghcup/issues/129
> >
> > Best,
> > Ryan S.
> > -
> > [1] https://gitlab.haskell.org/nunikonaza88
> > ___
> > ghc-devs mailing list
> > ghc-devs@haskell.org
> > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: gitlab.haskell.org spam issues

[Takenobu Tani]

They are also in snippets:

  https://gitlab.haskell.org/explore/snippets

Regards,
Takenobu

On Sun, Jan 12, 2020 at 7:08 AM Ryan Scott  wrote:
>
> There appears to be an account [1] that is submitting spam as GitLab issues. 
> I've noticed the following spam issues so far:
>
> * https://gitlab.haskell.org/ghc/ghc/issues/17664
> * https://gitlab.haskell.org/ghc/ghc/issues/17666
> * https://gitlab.haskell.org/haskell/ghcup/issues/125
> * https://gitlab.haskell.org/haskell/ghcup/issues/127
> * https://gitlab.haskell.org/haskell/ghcup/issues/129
>
> Best,
> Ryan S.
> -
> [1] https://gitlab.haskell.org/nunikonaza88
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

gitlab.haskell.org spam issues

[Ryan Scott]

There appears to be an account [1] that is submitting spam as GitLab
issues. I've noticed the following spam issues so far:

* https://gitlab.haskell.org/ghc/ghc/issues/17664
* https://gitlab.haskell.org/ghc/ghc/issues/17666
* https://gitlab.haskell.org/haskell/ghcup/issues/125
* https://gitlab.haskell.org/haskell/ghcup/issues/127
* https://gitlab.haskell.org/haskell/ghcup/issues/129

Best,
Ryan S.
-
[1] https://gitlab.haskell.org/nunikonaza88
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: Pushing to gitlab.haskell.org

[Brandon Allbery]

Exactly. Also it makes some sense to use https for fetch but ssh for push;
that's how I have my own repos and those for various other projects set up.

On Mon, Jun 3, 2019 at 12:34 PM Simon Peyton Jones via ghc-devs <
ghc-devs@haskell.org> wrote:

> |  You probably need to use the "git@" remote.
> |
> |  g...@gitlab.haskell.org:ghc/ghc.git
> |
> |  git remote set-url origin g...@gitlab.haskell.org:ghc/ghc.git
>
> Correct!  I don't know how this worked before. (Maybe it never did; this
> is a relatively new machine.)
>
> Maybe we should change the guidance on
> https://gitlab.haskell.org/ghc/ghc/wikis/building/getting-the-sources
>
> to give the git url?  Or does that /require/ ssh and hence exclude some
> folk?
>
> Simon
>
> |  -Original Message-
> |  From: Matthew Pickering 
> |  Sent: 03 June 2019 15:08
> |  To: Simon Peyton Jones 
> |  Subject: Re: Pushing to gitlab.haskell.org
> |
> |  You probably need to use the "git@" remote.
> |
> |  g...@gitlab.haskell.org:ghc/ghc.git
> |
> |  git remote set-url origin g...@gitlab.haskell.org:ghc/ghc.git
> |
> |
> |  On Mon, Jun 3, 2019 at 3:04 PM Simon Peyton Jones via ghc-devs  |  d...@haskell.org> wrote:
> |  >
> |  > Devs
> |  >
> |  > Suddenly I can’t push to (a non-master branch on) gitlab.haskell.org.
> |  >
> |  > In .git/config I have
> |  >
> |  > [remote "origin"]
> |  >
> |  >   url =
> |  >
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitl
> |  > ab.haskell.org%2Fghc%2Fghcdata=02%7C01%7Csimonpj%40microsoft.com
> %
> |  > 7C186b15a68a134060a1bd08d6e82ce8b3%7C72f988bf86f141af91ab2d7cd011db47%
> |  > 7C1%7C0%7C636951676910548930sdata=cTjUrROo3Dje%2FlbiFdtUPadlFUPsN
> |  > 2OWUgLIOYv%2BL8o%3Dreserved=0
> |  >
> |  >   fetch = +refs/heads/*:refs/remotes/origin/*
> |  >
> |  > [branch "master"]
> |  >
> |  >   remote = origin
> |  >
> |  >   merge = refs/heads/master
> |  >
> |  > An attempt to push leads to a request for a username.  If I enter
> one, a
> |  request for a password.
> |  >
> |  > simonpj@MSRC-3645512:~/code/HEAD$ git push origin wip/T16735
> |  >
> |  > Username for
> |  '
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.
> |  haskell.orgdata=02%7C01%7Csimonpj%40microsoft.com
> %7C186b15a68a134060a
> |
> 1bd08d6e82ce8b3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6369516769105
> |
> 48930sdata=O%2F%2B7WovumSLxe8%2FXrh1NpowWs%2FYVqhdEsDCsM5diz%2Bk%3D
> |  mp;reserved=0':   C-c C-c
> |  >
> |  > I thought I had SSH keys uploaded.  But in fact I found that my
> |  id_rsa.pub was a bit different to the one in gitlab.  Not sure _how_
> that
> |  happened, or why it hasn’t bitten before.
> |  >
> |  > So I uploaded a new id_rsa.pub key.
> |  >
> |  > Same behaviour.
> |  >
> |  > So I tried ssh -v gitlab.haskell.org, and got the output below.   It
> |  seems to skip id_dsa, but doesn’t even try id_rsa.
> |  >
> |  > Can anyone help? This is tiresome.
> |  >
> |  > Thanks
> |  >
> |  > Simon
> |  >
> |  >
> |  >
> |  > simonpj@MSRC-3645512:~/code/HEAD$ ssh -v gitlab.haskell.org
> |  >
> |  > OpenSSH_7.6p1 Ubuntu-4, OpenSSL 1.0.2n  7 Dec 2017
> |  >
> |  > debug1: Reading configuration data /home/simonpj/.ssh/config
> |  >
> |  > debug1: Reading configuration data /etc/ssh/ssh_config
> |  >
> |  > debug1: /etc/ssh/ssh_config line 19: Applying options for *
> |  >
> |  > debug1: Connecting to gitlab.haskell.org [2604:1380:0:8900::3] port
> 22.
> |  >
> |  > debug1: Connection established.
> |  >
> |  > debug1: identity file /home/simonpj/.ssh/id_rsa type 0
> |  >
> |  > debug1: key_load_public: No such file or directory
> |  >
> |  > debug1: identity file /home/simonpj/.ssh/id_rsa-cert type -1
> |  >
> |  > debug1: identity file /home/simonpj/.ssh/id_dsa type 1
> |  >
> |  > debug1: key_load_public: No such file or directory
> |  >
> |  > debug1: identity file /home/simonpj/.ssh/id_dsa-cert type -1
> |  >
> |  > debug1: key_load_public: No such file or directory
> |  >
> |  > debug1: identity file /home/simonpj/.ssh/id_ecdsa type -1
> |  >
> |  > debug1: key_load_public: No such file or directory
> |  >
> |  > debug1: identity file /home/simonpj/.ssh/id_ecdsa-cert type -1
> |  >
> |  > debug1: key_load_public: No such file or directory
> |  >
> |  > debug1: identity file /home/simonpj/.ssh/i

RE: Pushing to gitlab.haskell.org

[Simon Peyton Jones via ghc-devs]

|  You probably need to use the "git@" remote.
|  
|  g...@gitlab.haskell.org:ghc/ghc.git
|  
|  git remote set-url origin g...@gitlab.haskell.org:ghc/ghc.git

Correct!  I don't know how this worked before. (Maybe it never did; this is a 
relatively new machine.)

Maybe we should change the guidance on
https://gitlab.haskell.org/ghc/ghc/wikis/building/getting-the-sources

to give the git url?  Or does that /require/ ssh and hence exclude some folk?

Simon

|  -Original Message-
|  From: Matthew Pickering 
|  Sent: 03 June 2019 15:08
|  To: Simon Peyton Jones 
|  Subject: Re: Pushing to gitlab.haskell.org
|  
|  You probably need to use the "git@" remote.
|  
|  g...@gitlab.haskell.org:ghc/ghc.git
|  
|  git remote set-url origin g...@gitlab.haskell.org:ghc/ghc.git
|  
|  
|  On Mon, Jun 3, 2019 at 3:04 PM Simon Peyton Jones via ghc-devs  wrote:
|  >
|  > Devs
|  >
|  > Suddenly I can’t push to (a non-master branch on) gitlab.haskell.org.
|  >
|  > In .git/config I have
|  >
|  > [remote "origin"]
|  >
|  >   url =
|  > https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitl
|  > ab.haskell.org%2Fghc%2Fghcdata=02%7C01%7Csimonpj%40microsoft.com%
|  > 7C186b15a68a134060a1bd08d6e82ce8b3%7C72f988bf86f141af91ab2d7cd011db47%
|  > 7C1%7C0%7C636951676910548930sdata=cTjUrROo3Dje%2FlbiFdtUPadlFUPsN
|  > 2OWUgLIOYv%2BL8o%3Dreserved=0
|  >
|  >   fetch = +refs/heads/*:refs/remotes/origin/*
|  >
|  > [branch "master"]
|  >
|  >   remote = origin
|  >
|  >   merge = refs/heads/master
|  >
|  > An attempt to push leads to a request for a username.  If I enter one, a
|  request for a password.
|  >
|  > simonpj@MSRC-3645512:~/code/HEAD$ git push origin wip/T16735
|  >
|  > Username for
|  'https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.
|  haskell.orgdata=02%7C01%7Csimonpj%40microsoft.com%7C186b15a68a134060a
|  1bd08d6e82ce8b3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6369516769105
|  48930sdata=O%2F%2B7WovumSLxe8%2FXrh1NpowWs%2FYVqhdEsDCsM5diz%2Bk%3D
|  mp;reserved=0':   C-c C-c
|  >
|  > I thought I had SSH keys uploaded.  But in fact I found that my
|  id_rsa.pub was a bit different to the one in gitlab.  Not sure _how_ that
|  happened, or why it hasn’t bitten before.
|  >
|  > So I uploaded a new id_rsa.pub key.
|  >
|  > Same behaviour.
|  >
|  > So I tried ssh -v gitlab.haskell.org, and got the output below.   It
|  seems to skip id_dsa, but doesn’t even try id_rsa.
|  >
|  > Can anyone help? This is tiresome.
|  >
|  > Thanks
|  >
|  > Simon
|  >
|  >
|  >
|  > simonpj@MSRC-3645512:~/code/HEAD$ ssh -v gitlab.haskell.org
|  >
|  > OpenSSH_7.6p1 Ubuntu-4, OpenSSL 1.0.2n  7 Dec 2017
|  >
|  > debug1: Reading configuration data /home/simonpj/.ssh/config
|  >
|  > debug1: Reading configuration data /etc/ssh/ssh_config
|  >
|  > debug1: /etc/ssh/ssh_config line 19: Applying options for *
|  >
|  > debug1: Connecting to gitlab.haskell.org [2604:1380:0:8900::3] port 22.
|  >
|  > debug1: Connection established.
|  >
|  > debug1: identity file /home/simonpj/.ssh/id_rsa type 0
|  >
|  > debug1: key_load_public: No such file or directory
|  >
|  > debug1: identity file /home/simonpj/.ssh/id_rsa-cert type -1
|  >
|  > debug1: identity file /home/simonpj/.ssh/id_dsa type 1
|  >
|  > debug1: key_load_public: No such file or directory
|  >
|  > debug1: identity file /home/simonpj/.ssh/id_dsa-cert type -1
|  >
|  > debug1: key_load_public: No such file or directory
|  >
|  > debug1: identity file /home/simonpj/.ssh/id_ecdsa type -1
|  >
|  > debug1: key_load_public: No such file or directory
|  >
|  > debug1: identity file /home/simonpj/.ssh/id_ecdsa-cert type -1
|  >
|  > debug1: key_load_public: No such file or directory
|  >
|  > debug1: identity file /home/simonpj/.ssh/id_ed25519 type -1
|  >
|  > debug1: key_load_public: No such file or directory
|  >
|  > debug1: identity file /home/simonpj/.ssh/id_ed25519-cert type -1
|  >
|  > debug1: Local version string SSH-2.0-OpenSSH_7.6p1 Ubuntu-4
|  >
|  > debug1: Remote protocol version 2.0, remote software version
|  > OpenSSH_7.9
|  >
|  > debug1: match: OpenSSH_7.9 pat OpenSSH* compat 0x0400
|  >
|  > debug1: Authenticating to gitlab.haskell.org:22 as 'simonpj'
|  >
|  > debug1: SSH2_MSG_KEXINIT sent
|  >
|  > debug1: SSH2_MSG_KEXINIT received
|  >
|  > debug1: kex: algorithm: curve25519-sha...@libssh.org
|  >
|  > debug1: kex: host key algorithm: ssh-ed25519
|  >
|  > debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC:
|  >  compression: none
|  >
|  > debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC:
|  >

Re: Pushing to gitlab.haskell.org

[Niklas Hambüchen]

Hey Simon,

you mention SSH keys, but in your quoted config I can see HTTPS, not SSH:

> [remote "origin"]
>   url = https://gitlab.haskell.org/ghc/ghc

Should this perhaps be

url = g...@gitlab.haskell.org:ghc/ghc.git

instead?

> So I tried ssh -v gitlab.haskell.org

You need to include the user name "git" for this. Otherwise it will try to use 
your local user name on the remote server.
This is the command to run and the output you should get if it's working:

$ ssh g...@gitlab.haskell.org
PTY allocation request failed on channel 0
Welcome to GitLab, @nh2!
Connection to gitlab.haskell.org closed.

Hope this helps,

Niklas
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Pushing to gitlab.haskell.org

[Simon Peyton Jones via ghc-devs]

Devs
Suddenly I can't push to (a non-master branch on) gitlab.haskell.org.
In .git/config I have

[remote "origin"]

  url = https://gitlab.haskell.org/ghc/ghc

  fetch = +refs/heads/*:refs/remotes/origin/*

[branch "master"]

  remote = origin

  merge = refs/heads/master
An attempt to push leads to a request for a username.  If I enter one, a 
request for a password.

simonpj@MSRC-3645512:~/code/HEAD$ git push origin wip/T16735

Username for 'https://gitlab.haskell.org':   C-c C-c
I thought I had SSH keys uploaded.  But in fact I found that my id_rsa.pub was 
a bit different to the one in gitlab.  Not sure _how_ that happened, or why it 
hasn't bitten before.
So I uploaded a new id_rsa.pub key.
Same behaviour.
So I tried ssh -v gitlab.haskell.org, and got the output below.   It seems to 
skip id_dsa, but doesn't even try id_rsa.
Can anyone help? This is tiresome.
Thanks
Simon


simonpj@MSRC-3645512:~/code/HEAD$ ssh -v gitlab.haskell.org

OpenSSH_7.6p1 Ubuntu-4, OpenSSL 1.0.2n  7 Dec 2017

debug1: Reading configuration data /home/simonpj/.ssh/config

debug1: Reading configuration data /etc/ssh/ssh_config

debug1: /etc/ssh/ssh_config line 19: Applying options for *

debug1: Connecting to gitlab.haskell.org [2604:1380:0:8900::3] port 22.

debug1: Connection established.

debug1: identity file /home/simonpj/.ssh/id_rsa type 0

debug1: key_load_public: No such file or directory

debug1: identity file /home/simonpj/.ssh/id_rsa-cert type -1

debug1: identity file /home/simonpj/.ssh/id_dsa type 1

debug1: key_load_public: No such file or directory

debug1: identity file /home/simonpj/.ssh/id_dsa-cert type -1

debug1: key_load_public: No such file or directory

debug1: identity file /home/simonpj/.ssh/id_ecdsa type -1

debug1: key_load_public: No such file or directory

debug1: identity file /home/simonpj/.ssh/id_ecdsa-cert type -1

debug1: key_load_public: No such file or directory

debug1: identity file /home/simonpj/.ssh/id_ed25519 type -1

debug1: key_load_public: No such file or directory

debug1: identity file /home/simonpj/.ssh/id_ed25519-cert type -1

debug1: Local version string SSH-2.0-OpenSSH_7.6p1 Ubuntu-4

debug1: Remote protocol version 2.0, remote software version OpenSSH_7.9

debug1: match: OpenSSH_7.9 pat OpenSSH* compat 0x0400

debug1: Authenticating to gitlab.haskell.org:22 as 'simonpj'

debug1: SSH2_MSG_KEXINIT sent

debug1: SSH2_MSG_KEXINIT received

debug1: kex: algorithm: curve25519-sha...@libssh.org

debug1: kex: host key algorithm: ssh-ed25519

debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none

debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none

debug1: expecting SSH2_MSG_KEX_ECDH_REPLY

debug1: Server host key: ssh-ed25519 
SHA256:wtE9yoEHLsotzqKfbDs1JIqR+c8ZZyW+FAJAmteBfcI

debug1: Host 'gitlab.haskell.org' is known and matches the ED25519 host key.

debug1: Found key in /home/simonpj/.ssh/known_hosts:7

debug1: rekey after 134217728 blocks

debug1: SSH2_MSG_NEWKEYS sent

debug1: expecting SSH2_MSG_NEWKEYS

debug1: SSH2_MSG_NEWKEYS received

debug1: rekey after 134217728 blocks

debug1: Skipping ssh-dss key /home/simonpj/.ssh/id_dsa - not in 
PubkeyAcceptedKeyTypes

debug1: SSH2_MSG_EXT_INFO received

debug1: kex_input_ext_info: 
server-sig-algs=

debug1: SSH2_MSG_SERVICE_ACCEPT received

debug1: Authentications that can continue: 
publickey,password,keyboard-interactive

debug1: Next authentication method: publickey

debug1: Offering public key: RSA 
SHA256:H1l824hIxHozwRuEqdaYJjW10mRRlQVUhxREvuseqtU /home/simonpj/.ssh/id_rsa

debug1: Authentications that can continue: 
publickey,password,keyboard-interactive

debug1: Trying private key: /home/simonpj/.ssh/id_ecdsa

debug1: Trying private key: /home/simonpj/.ssh/id_ed25519

debug1: Next authentication method: keyboard-interactive

Password:   C-c C-c



simonpj@MSRC-3645512:~/code/HEAD$


___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: gitlab.haskell.org is down

[Alp Mestanogullari]

GitLab should be back now, seems to be working fine for me (both using 
the web UI and fetching from ghc/ghc.git).


On 29/03/2019 09:46, Simon Peyton Jones via ghc-devs wrote:

Yes, I'm getting 500 too.

Simon

|  -Original Message-
|  From: ghc-devs  On Behalf Of Ömer Sinan
|  Agacan
|  Sent: 29 March 2019 06:20
|  To: Ben Gamari 
|  Cc: GHC developers 
|  Subject: Re: gitlab.haskell.org is down
|
|  I'm still getting 500.
|
|  Ömer
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs


--
Alp Mestanogullari, Haskell Consultant
Well-Typed LLP, https://www.well-typed.com/

Registered in England and Wales, OC335890
118 Wymering Mansions, Wymering Road, London, W9 2NF, England

___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

RE: gitlab.haskell.org is down

[Simon Peyton Jones via ghc-devs]

Yes, I'm getting 500 too.

Simon

|  -Original Message-
|  From: ghc-devs  On Behalf Of Ömer Sinan
|  Agacan
|  Sent: 29 March 2019 06:20
|  To: Ben Gamari 
|  Cc: GHC developers 
|  Subject: Re: gitlab.haskell.org is down
|  
|  I'm still getting 500.
|  
|  Ömer
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: gitlab.haskell.org is down

[Ömer Sinan Ağacan]

I'm still getting 500.

Ömer

Ben Gamari , 29 Mar 2019 Cum, 00:46 tarihinde şunu yazdı:
>
> Ben Gamari  writes:
>
> > Shayne Fletcher via ghc-devs  writes:
> >
> >> Hi,
> >>
> >> It seems gitlab.haskell.org has been down since around 17:30 GMT. Outage?
> >>
> > Yes, I just sent notification of this. A routine service restart ended
> > up going wrong. In touch with our infrastructure company's support team.
> > More updates coming soon.
> >
> Gitlab.haskell.org is back up.
>
> Cheers,
>
> - Ben
>
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: gitlab.haskell.org is down

[Ben Gamari]

Ben Gamari  writes:

> Shayne Fletcher via ghc-devs  writes:
>
>> Hi,
>>
>> It seems gitlab.haskell.org has been down since around 17:30 GMT. Outage?
>>
> Yes, I just sent notification of this. A routine service restart ended
> up going wrong. In touch with our infrastructure company's support team.
> More updates coming soon.
>
Gitlab.haskell.org is back up.

Cheers,

- Ben



signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: gitlab.haskell.org is down

[Ben Gamari]

Shayne Fletcher via ghc-devs  writes:

> Hi,
>
> It seems gitlab.haskell.org has been down since around 17:30 GMT. Outage?
>
Yes, I just sent notification of this. A routine service restart ended
up going wrong. In touch with our infrastructure company's support team.
More updates coming soon.

Cheers,

- Ben


signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

gitlab.haskell.org is down

[Shayne Fletcher via ghc-devs]

Hi,

It seems gitlab.haskell.org has been down since around 17:30 GMT. Outage?

-- 
Shayne Fletcher
Language Engineer
c: +1 917 699 7763
e: shayne.fletc...@daml.com
Digital Asset Holdings, LLC
4 World Trade Center150 Greenwich
Street, 47th Floor
<https://maps.google.com/?q=150+Greenwich+Street,+47th+Floor%C2%A0+%C2%A0+%C2%A0+%C2%A0+%C2%A0+New+York,+NY+10007,+USA=gmail=g>
New York, NY 10007, USA
<https://maps.google.com/?q=150+Greenwich+Street,+47th+Floor%C2%A0+%C2%A0+%C2%A0+%C2%A0+%C2%A0+New+York,+NY+10007,+USA=gmail=g>
digitalasset.com <http://www.digitalasset.com/>

-- 
This message, and any attachments, is for the intended recipient(s) only, 
may contain information that is privileged, confidential and/or proprietary 
and subject to important terms and conditions available at 
http://www.digitalasset.com/emaildisclaimer.html 
<http://www.digitalasset.com/emaildisclaimer.html>. If you are not the 
intended recipient, please delete this message.
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: git clone https://gitlab.haskell.org/ghc/ghc.git on travis doesn't work

[Shayne Fletcher via ghc-devs]

On Sat, Mar 9, 2019 at 9:09 PM Michael Sloan  wrote:

> Ah, probably so, thanks!
>
> On Sat, Mar 9, 2019 at 6:05 PM Brandon Allbery 
> wrote:
> >
> > I think the public name is pointed to the staging site because the main
> one is down for the trac to github migration.
>

That's exactly it - been down Sat. I guess it will take as long as it takes!


> >>> > For now I've just done "git config --global http.sslverify false"
>
>> > temporarily to do the pull.  Perhaps this is Shayne Fletcher's cheeky
> >> > workaround? :)
>

No, that ain't it :)

-- 
This message, and any attachments, is for the intended recipient(s) only, 
may contain information that is privileged, confidential and/or proprietary 
and subject to important terms and conditions available at 
http://www.digitalasset.com/emaildisclaimer.html 
. If you are not the 
intended recipient, please delete this message.
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: git clone https://gitlab.haskell.org/ghc/ghc.git on travis doesn't work

[Michael Sloan]

Ah, probably so, thanks!

On Sat, Mar 9, 2019 at 6:05 PM Brandon Allbery  wrote:
>
> I think the public name is pointed to the staging site because the main one 
> is down for the trac to github migration.
>
> On Sat, Mar 9, 2019 at 8:59 PM Michael Sloan  wrote:
>>
>> Whoah, I can't get https://ghc.haskell.org/ to load at all - it's also
>> trying to use the gitlab.staging.haskell.org cert.  I can't get chrome
>> to ignore the cert error because it's using HSTS - HTTP Strict
>> Transport Security.
>>
>> On Sat, Mar 9, 2019 at 5:53 PM Michael Sloan  wrote:
>> >
>> > I just encountered this when doing a "git pull" on my Ubuntu 18.04.1 
>> > machine:
>> >
>> > > fatal: unable to access 'https://gitlab.haskell.org/ghc/ghc/': server 
>> > > certificate verification failed. CAfile: 
>> > > /etc/ssl/certs/ca-certificates.crt CRLfile: none
>> >
>> > Chrome also believes that the certificate of
>> > https://gitlab.haskell.org/ghc/ghc is invalid and I have to click the
>> > "Proceed to ... (unsafe)" link.  Chrome's certificate viewer shows
>> > that the certificate is for "gitlab.staging.haskell.org" whereas the
>> > domain is "gitlab.haskell.org", so I'm guessing that's the problem.
>> > I'm not very experienced with such cert stuff, but  perhaps a wildcard
>> > cert like "*.haskell.org" could allow using the same cert regardless
>> > of whether it's on staging vs prod.
>> >
>> > For now I've just done "git config --global http.sslverify false"
>> > temporarily to do the pull.  Perhaps this is Shayne Fletcher's cheeky
>> > workaround? :)
>> >
>> > -Michael
>> >
>> > On Fri, Mar 8, 2019 at 10:23 PM Ben Gamari  wrote:
>> > >
>> > > Shayne Fletcher via ghc-devs  writes:
>> > >
>> > > > I appreciate this isn't really "our" problem :) Nonetheless, if 
>> > > > there's any
>> > > > config we can do on the repo on gitlab, that would be cool. Other URLs
>> > > > (like github) for example are fine - something specific to gitlab.
>> > > >
>> > > I feel like I'm missing something here. I recall you mentioned this in
>> > > your previous message but there I'm still lacking crucial context. Can
>> > > you offer any additional details? How exactly does it fail?
>> > >
>> > > In principle there is no reason why cloning from gitlab.haskell.org from
>> > > Travis shouldn't work. I'd be happy to fix the issue if there is one but
>> > > without knowing more I'm pretty powerless to change the situation.
>> > >
>> > > Cheers,
>> > >
>> > > - Ben
>> > >
>> > > ___
>> > > ghc-devs mailing list
>> > > ghc-devs@haskell.org
>> > > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>> ___
>> ghc-devs mailing list
>> ghc-devs@haskell.org
>> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>
>
>
> --
> brandon s allbery kf8nh
> allber...@gmail.com
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: git clone https://gitlab.haskell.org/ghc/ghc.git on travis doesn't work

[Brandon Allbery]

I think the public name is pointed to the staging site because the main one
is down for the trac to github migration.

On Sat, Mar 9, 2019 at 8:59 PM Michael Sloan  wrote:

> Whoah, I can't get https://ghc.haskell.org/ to load at all - it's also
> trying to use the gitlab.staging.haskell.org cert.  I can't get chrome
> to ignore the cert error because it's using HSTS - HTTP Strict
> Transport Security.
>
> On Sat, Mar 9, 2019 at 5:53 PM Michael Sloan  wrote:
> >
> > I just encountered this when doing a "git pull" on my Ubuntu 18.04.1
> machine:
> >
> > > fatal: unable to access 'https://gitlab.haskell.org/ghc/ghc/': server
> certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt
> CRLfile: none
> >
> > Chrome also believes that the certificate of
> > https://gitlab.haskell.org/ghc/ghc is invalid and I have to click the
> > "Proceed to ... (unsafe)" link.  Chrome's certificate viewer shows
> > that the certificate is for "gitlab.staging.haskell.org" whereas the
> > domain is "gitlab.haskell.org", so I'm guessing that's the problem.
> > I'm not very experienced with such cert stuff, but  perhaps a wildcard
> > cert like "*.haskell.org" could allow using the same cert regardless
> > of whether it's on staging vs prod.
> >
> > For now I've just done "git config --global http.sslverify false"
> > temporarily to do the pull.  Perhaps this is Shayne Fletcher's cheeky
> > workaround? :)
> >
> > -Michael
> >
> > On Fri, Mar 8, 2019 at 10:23 PM Ben Gamari  wrote:
> > >
> > > Shayne Fletcher via ghc-devs  writes:
> > >
> > > > I appreciate this isn't really "our" problem :) Nonetheless, if
> there's any
> > > > config we can do on the repo on gitlab, that would be cool. Other
> URLs
> > > > (like github) for example are fine - something specific to gitlab.
> > > >
> > > I feel like I'm missing something here. I recall you mentioned this in
> > > your previous message but there I'm still lacking crucial context. Can
> > > you offer any additional details? How exactly does it fail?
> > >
> > > In principle there is no reason why cloning from gitlab.haskell.org
> from
> > > Travis shouldn't work. I'd be happy to fix the issue if there is one
> but
> > > without knowing more I'm pretty powerless to change the situation.
> > >
> > > Cheers,
> > >
> > > - Ben
> > >
> > > ___
> > > ghc-devs mailing list
> > > ghc-devs@haskell.org
> > > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>


-- 
brandon s allbery kf8nh
allber...@gmail.com
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: git clone https://gitlab.haskell.org/ghc/ghc.git on travis doesn't work

[Michael Sloan]

Whoah, I can't get https://ghc.haskell.org/ to load at all - it's also
trying to use the gitlab.staging.haskell.org cert.  I can't get chrome
to ignore the cert error because it's using HSTS - HTTP Strict
Transport Security.

On Sat, Mar 9, 2019 at 5:53 PM Michael Sloan  wrote:
>
> I just encountered this when doing a "git pull" on my Ubuntu 18.04.1 machine:
>
> > fatal: unable to access 'https://gitlab.haskell.org/ghc/ghc/': server 
> > certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt 
> > CRLfile: none
>
> Chrome also believes that the certificate of
> https://gitlab.haskell.org/ghc/ghc is invalid and I have to click the
> "Proceed to ... (unsafe)" link.  Chrome's certificate viewer shows
> that the certificate is for "gitlab.staging.haskell.org" whereas the
> domain is "gitlab.haskell.org", so I'm guessing that's the problem.
> I'm not very experienced with such cert stuff, but  perhaps a wildcard
> cert like "*.haskell.org" could allow using the same cert regardless
> of whether it's on staging vs prod.
>
> For now I've just done "git config --global http.sslverify false"
> temporarily to do the pull.  Perhaps this is Shayne Fletcher's cheeky
> workaround? :)
>
> -Michael
>
> On Fri, Mar 8, 2019 at 10:23 PM Ben Gamari  wrote:
> >
> > Shayne Fletcher via ghc-devs  writes:
> >
> > > I appreciate this isn't really "our" problem :) Nonetheless, if there's 
> > > any
> > > config we can do on the repo on gitlab, that would be cool. Other URLs
> > > (like github) for example are fine - something specific to gitlab.
> > >
> > I feel like I'm missing something here. I recall you mentioned this in
> > your previous message but there I'm still lacking crucial context. Can
> > you offer any additional details? How exactly does it fail?
> >
> > In principle there is no reason why cloning from gitlab.haskell.org from
> > Travis shouldn't work. I'd be happy to fix the issue if there is one but
> > without knowing more I'm pretty powerless to change the situation.
> >
> > Cheers,
> >
> > - Ben
> >
> > ___
> > ghc-devs mailing list
> > ghc-devs@haskell.org
> > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: git clone https://gitlab.haskell.org/ghc/ghc.git on travis doesn't work

[Michael Sloan]

I just encountered this when doing a "git pull" on my Ubuntu 18.04.1 machine:

> fatal: unable to access 'https://gitlab.haskell.org/ghc/ghc/': server 
> certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt 
> CRLfile: none

Chrome also believes that the certificate of
https://gitlab.haskell.org/ghc/ghc is invalid and I have to click the
"Proceed to ... (unsafe)" link.  Chrome's certificate viewer shows
that the certificate is for "gitlab.staging.haskell.org" whereas the
domain is "gitlab.haskell.org", so I'm guessing that's the problem.
I'm not very experienced with such cert stuff, but  perhaps a wildcard
cert like "*.haskell.org" could allow using the same cert regardless
of whether it's on staging vs prod.

For now I've just done "git config --global http.sslverify false"
temporarily to do the pull.  Perhaps this is Shayne Fletcher's cheeky
workaround? :)

-Michael

On Fri, Mar 8, 2019 at 10:23 PM Ben Gamari  wrote:
>
> Shayne Fletcher via ghc-devs  writes:
>
> > I appreciate this isn't really "our" problem :) Nonetheless, if there's any
> > config we can do on the repo on gitlab, that would be cool. Other URLs
> > (like github) for example are fine - something specific to gitlab.
> >
> I feel like I'm missing something here. I recall you mentioned this in
> your previous message but there I'm still lacking crucial context. Can
> you offer any additional details? How exactly does it fail?
>
> In principle there is no reason why cloning from gitlab.haskell.org from
> Travis shouldn't work. I'd be happy to fix the issue if there is one but
> without knowing more I'm pretty powerless to change the situation.
>
> Cheers,
>
> - Ben
>
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: git clone https://gitlab.haskell.org/ghc/ghc.git on travis doesn't work

[Shayne Fletcher via ghc-devs]

On Sat, Mar 9, 2019 at 11:41 AM Oleg Grenrus  wrote:

> I can reproduce that problem on Ubuntu 14.04 which Travis uses now by
> default.
> It's "fixed" in Ubuntu 16.04. Use
>
> dist: xenial
>
> and your travis build should proceed.
>
>
Nice! Thanks!!

-- 
This message, and any attachments, is for the intended recipient(s) only, 
may contain information that is privileged, confidential and/or proprietary 
and subject to important terms and conditions available at 
http://www.digitalasset.com/emaildisclaimer.html 
. If you are not the 
intended recipient, please delete this message.
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: git clone https://gitlab.haskell.org/ghc/ghc.git on travis doesn't work

[Oleg Grenrus]

I can reproduce that problem on Ubuntu 14.04 which Travis uses now by
default.
It's "fixed" in Ubuntu 16.04. Use

    dist: xenial

and your travis build should proceed.

---

Ubuntu 14.04

root@6f98cdde6521:/# git clone https://gitlab.haskell.org/ghc/ci-images.git
Cloning into 'ci-images'...
fatal: unable to access 'https://gitlab.haskell.org/ghc/ci-images.git/':
gnutls_handshake() failed: Handshake failed

Ubuntu 16.04

root@a66b1076e2f8:/#  git clone https://gitlab.haskell.org/ghc/ci-images.git
Cloning into 'ci-images'...
remote: Enumerating objects: 110, done.
remote: Counting objects: 100% (110/110), done.
remote: Compressing objects: 100% (53/53), done.
remote: Total 110 (delta 49), reused 81 (delta 36)
Receiving objects: 100% (110/110), 17.14 KiB | 0 bytes/s, done.
Resolving deltas: 100% (49/49), done.
Checking connectivity... done.


---

- Oleg

On 9.3.2019 14.15, Shayne Fletcher wrote:
>
> On Sat, Mar 9, 2019 at 1:23 AM Ben Gamari  <mailto:b...@well-typed.com>> wrote:
>
> Shayne Fletcher via ghc-devs  <mailto:ghc-devs@haskell.org>> writes:
>
> [...] 
>
> I feel like I'm missing something here. I recall you mentioned this in
> your previous message but there I'm still lacking crucial context. Can
> you offer any additional details? How exactly does it fail?
>
>
> git clone https://gitlab.haskell.org/ghc/ghc.git fails on Travis Linux
> Ubuntu VMs with "fatal: unable to access
> 'https://gitlab.haskell.org/ghc/ghc.git/': gnutls_handshake() failed:
> Handshake failed.
>
> In principle there is no reason why cloning from
> gitlab.haskell.org <http://gitlab.haskell.org> from
> Travis shouldn't work. I'd be happy to fix the issue if there is
> one but
> without knowing more I'm pretty powerless to change the situation.
>
>
> The issue as I understand relates to gitlab's use of the "Let's
> Encrypt" certificate authority. Apparently this is a relatively new
> authority and is unrecognized by the SSL software on the Ubuntu VM
> that Travis provides. I don't know of any workarounds at this time
> that can be applied in the VM that to overcome this problem. I also
> don't know if anything can be done on the gitlab side to mitigate it
> but suspect not. I do have a procedure that allows me to side-step the
> problem for my own case and can share that with anyone that needs it.
>
> Cheers,
>
> - Ben
>
>
>
>
> This message, and any attachments, is for the intended recipient(s)
> only, may contain information that is privileged, confidential and/or
> proprietary and subject to important terms and conditions available
> at http://www.digitalasset.com/emaildisclaimer.html
> <http://www.digitalasset.com/emaildisclaimer.html>. If you are not the
> intended recipient, please delete this message. 



signature.asc
Description: OpenPGP digital signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: git clone https://gitlab.haskell.org/ghc/ghc.git on travis doesn't work

[Shayne Fletcher via ghc-devs]

On Sat, Mar 9, 2019 at 1:23 AM Ben Gamari  wrote:

> Shayne Fletcher via ghc-devs  writes:
>
> [...]

> I feel like I'm missing something here. I recall you mentioned this in
> your previous message but there I'm still lacking crucial context. Can
> you offer any additional details? How exactly does it fail?
>
>
git clone https://gitlab.haskell.org/ghc/ghc.git fails on Travis Linux
Ubuntu VMs with "fatal: unable to access '
https://gitlab.haskell.org/ghc/ghc.git/': gnutls_handshake() failed:
Handshake failed.

In principle there is no reason why cloning from gitlab.haskell.org from
> Travis shouldn't work. I'd be happy to fix the issue if there is one but
> without knowing more I'm pretty powerless to change the situation.
>
>
The issue as I understand relates to gitlab's use of the "Let's Encrypt"
certificate authority. Apparently this is a relatively new authority and is
unrecognized by the SSL software on the Ubuntu VM that Travis provides. I
don't know of any workarounds at this time that can be applied in the VM
that to overcome this problem. I also don't know if anything can be done on
the gitlab side to mitigate it but suspect not. I do have a procedure that
allows me to side-step the problem for my own case and can share that with
anyone that needs it.

Cheers,
>
> - Ben
>
>

-- 
This message, and any attachments, is for the intended recipient(s) only, 
may contain information that is privileged, confidential and/or proprietary 
and subject to important terms and conditions available at 
http://www.digitalasset.com/emaildisclaimer.html 
<http://www.digitalasset.com/emaildisclaimer.html>. If you are not the 
intended recipient, please delete this message.
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: git clone https://gitlab.haskell.org/ghc/ghc.git on travis doesn't work

[Oleg Grenrus]

At least at some point travis refused to clone git:// (over ssh) urls; but 
https:// works fine. As ghcs’ submodules are relative it /should just work/

- Oleg

Sent from my iPhone

> On 9 Mar 2019, at 8.22, Ben Gamari  wrote:
> 
> Shayne Fletcher via ghc-devs  writes:
> 
>> I appreciate this isn't really "our" problem :) Nonetheless, if there's any
>> config we can do on the repo on gitlab, that would be cool. Other URLs
>> (like github) for example are fine - something specific to gitlab.
>> 
> I feel like I'm missing something here. I recall you mentioned this in
> your previous message but there I'm still lacking crucial context. Can
> you offer any additional details? How exactly does it fail?
> 
> In principle there is no reason why cloning from gitlab.haskell.org from
> Travis shouldn't work. I'd be happy to fix the issue if there is one but
> without knowing more I'm pretty powerless to change the situation.
> 
> Cheers,
> 
> - Ben
> 
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Re: git clone https://gitlab.haskell.org/ghc/ghc.git on travis doesn't work

[Ben Gamari]

Shayne Fletcher via ghc-devs  writes:

> I appreciate this isn't really "our" problem :) Nonetheless, if there's any
> config we can do on the repo on gitlab, that would be cool. Other URLs
> (like github) for example are fine - something specific to gitlab.
>
I feel like I'm missing something here. I recall you mentioned this in
your previous message but there I'm still lacking crucial context. Can
you offer any additional details? How exactly does it fail?

In principle there is no reason why cloning from gitlab.haskell.org from
Travis shouldn't work. I'd be happy to fix the issue if there is one but
without knowing more I'm pretty powerless to change the situation.

Cheers,

- Ben



signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

git clone https://gitlab.haskell.org/ghc/ghc.git on travis doesn't work

[Shayne Fletcher via ghc-devs]

I appreciate this isn't really "our" problem :) Nonetheless, if there's any
config we can do on the repo on gitlab, that would be cool. Other URLs
(like github) for example are fine - something specific to gitlab.

-- 
This message, and any attachments, is for the intended recipient(s) only, 
may contain information that is privileged, confidential and/or proprietary 
and subject to important terms and conditions available at 
http://www.digitalasset.com/emaildisclaimer.html 
. If you are not the 
intended recipient, please delete this message.
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs