From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: Andy Tai <atai@atai.org>,
guix-devel@gnu.org, Ricardo Wurmus <rekado@elephly.net>
Subject: Re: issues.guix.gnu.org seems stop updating
Date: Sat, 09 Dec 2023 12:05:14 +0100 [thread overview]
Message-ID: <87msuj63h1.fsf@gnu.org> (raw)
In-Reply-To: <87msukgwg6.fsf@gmail.com> (Maxim Cournoyer's message of "Fri, 08 Dec 2023 17:29:13 -0500")
Hi,
Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
> Andy Tai <atai@atai.org> writes:
>
>> https://issues.guix.gnu.org/recent, for example, only shows issues up to Dec 6.
>>
>> Not sure if this is due to some data services stopping running or such...
>
> Perhaps the machine was restarted and the manual rsync job not
> restarted? We still don't have a service for it (bug #59180).
No, apparently it was a problem at debbugs.gnu.org, now resolved.
Many thanks to Tobias, Felix, and others who’ve been discussing with the
folks over at #savannah to figure it out!
Ludo’.
next prev parent reply other threads:[~2023-12-09 11:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 19:42 issues.guix.gnu.org seems stop updating Andy Tai
2023-12-08 22:12 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-12-08 22:29 ` Maxim Cournoyer
2023-12-09 0:53 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-12-09 11:05 ` Ludovic Courtès [this message]
2024-02-03 20:34 ` Issues with issues.guix.gnu.org (502 Bad Gateway) Christina O'Donnell
2024-02-03 20:34 ` bug#68920: " Christina O'Donnell
2024-02-04 5:33 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-02-04 10:56 ` Christina O'Donnell
2024-02-04 10:56 ` bug#68920: " Christina O'Donnell
2024-02-06 14:22 ` Maxim Cournoyer
2024-02-06 15:55 ` Andreas Enge
2024-02-07 1:31 ` Maxim Cournoyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87msuj63h1.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=atai@atai.org \
--cc=guix-devel@gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=rekado@elephly.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.