|
From: | GNU bug Tracking System |
Subject: | bug#38446: closed (Guix pull broken (502 error)) |
Date: | Mon, 02 Dec 2019 23:34:02 +0000 |
Your message dated Tue, 03 Dec 2019 00:32:54 +0100 with message-id <address@hidden> and subject line Re: bug#38446: Guix pull broken has caused the debbugs.gnu.org bug report #38446, regarding Guix pull broken (502 error) to be marked as done. (If you believe you have received this mail in error, please contact address@hidden.) -- 38446: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=38446 GNU Bug Tracking System Contact address@hidden with problems
--- Begin Message ---Subject: Guix pull broken Date: Sun, 01 Dec 2019 19:15:22 +0100 User-agent: mu4e 1.2.0; emacs 26.3 https://git.savannah.gnu.org/cgit/guix.git/log/ returns 502 error. Reproducible 9 times out of 10.
--- End Message ---
--- Begin Message ---Subject: Re: bug#38446: Guix pull broken Date: Tue, 03 Dec 2019 00:32:54 +0100 User-agent: mu4e 1.2.0; emacs 26.3 Hi Ricardo, Ricardo Wurmus <address@hidden> writes: > For the time being you can do > > git clone https://guix.gnu.org/git/guix > > which is a read-only copy of my clone of the repository. I’d like to > make it automatically sync up with the repo on Savannah, but I ran out > of time. Great! Thank you very much, Clément PS: I'm closing the bug, since it doesn't really depend on us and we have a workaround.
--- End Message ---
[Prev in Thread] | Current Thread | [Next in Thread] |