Re: [sr #110155] Can not "git fetch upstream" public repos

burak sarac wrote: > Its definitely fine! Works like a charm now, I would say even faster than > before:) Thank you for the kind words! zimoun wrote: > It works when cloning anonymously. I do not know yet when member > because my account is probably still too fresh. Member access for commit is

Re: [sr #110155] Can not "git fetch upstream" public repos

Dear, Thank you. It works when cloning anonymously. I do not know yet when member because my account is probably still too fresh. All the best, simon

[Savannah-hackers-public] Problems with email and debbugs?

Looks like email delivery stopped at fencepost. And debbugs takes a very long time to return results of a query. Another DDoS attack on GNU servers? TIA

Re: [Savannah-hackers-public] Problems with email and debbugs?

Eli Zaretskii wrote: > Looks like email delivery stopped at fencepost. And debbugs takes a > very long time to return results of a query. > > Another DDoS attack on GNU servers? I shouldn't be responding to this as I don't know first hand information but I didn't see other responses so will

Re: [Savannah-hackers-public] Problems with email and debbugs?

> Date: Fri, 6 Dec 2019 12:34:29 -0700 > From: Bob Proulx > Cc: sysad...@gnu.org, savannah-hackers-public@gnu.org > > Eli Zaretskii wrote: > > Looks like email delivery stopped at fencepost. And debbugs takes a > > very long time to return results of a query. > > > > Another DDoS attack on GNU

[Savannah-hackers-public] [gnu.org #1456067] Re: Problems with email and debbugs?

On Fri Dec 06 14:52:40 2019, e...@gnu.org wrote: > Maybe I should describe what I actually saw. So here goes: > > . The debbugs page opened quickly, but then asking to display a > specific bug report too several tens of seconds, maybe more than a > minute. > > . My mailbox on

[sr #110155] Can not "git fetch upstream" public repos

URL: Summary: Can not "git fetch upstream" public repos Project: Savannah Administration Submitted by: buraksarac Submitted on: Fri 06 Dec 2019 09:45:51 AM UTC Category:

[sr #110154] wallchanger Project Homepage does not work

URL: Summary: wallchanger Project Homepage does not work Project: Savannah Administration Submitted by: michalb1981 Submitted on: Fri 06 Dec 2019 06:56:48 AM UTC Category:

Re: [sr #110155] Can not "git fetch upstream" public repos

Thank you Tobias for the link, I didnt know, relieved also upset as well why one would do such a j.rk move on public repos. Anyway crossing fingers that it will end soon and have a nice weekend Burak 2019-12-06 15:21 GMT+01:00, Tobias Geerinckx-Rice : > Follow-up Comment #2, sr #110155 (project

[sr #110155] Can not "git fetch upstream" public repos

Follow-up Comment #2, sr #110155 (project administration): Burak, It's not you. As Simon hints, the FSF's been the target of a large-footprint DDoS attack for the past week. Sometimes one can get lucky and anonymous git

[sr #110155] Can not "git fetch upstream" public repos

Follow-up Comment #1, sr #110155 (project administration): Dear, I have the same issue about Guix repos. First error 502 then 443 connection refused. Is it related to the DDoS attack? All the best, simon ___ Reply to this item at:

[sr #110149] No access right to CVS website repo

Update of sr #110149 (project administration): Status:None => Done Open/Closed:Open => Closed ___ Follow-up Comment #8: I am very

[sr #110155] Can not "git fetch upstream" public repos

Update of sr #110155 (project administration): Status:None => In Progress Assigned to:None => rwp ___ Follow-up Comment #3: Gack!

[sr #110154] wallchanger Project Homepage does not work

Update of sr #110154 (project administration): Status:None => Confirmed ___ Follow-up Comment #1: No time for more this moment than confirming the problem.

Re: [sr #110155] Can not "git fetch upstream" public repos

Hello Bob, Its definitely fine! Works like a charm now, I would say even faster than before:) Thank you for quick response Burak 2019-12-06 20:15 GMT+01:00, Bob Proulx : > Update of sr #110155 (project administration): > > Status:None => In Progress > >