From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: Nicolas Dandrimont <nicolas@dandrimont.eu>
Cc: swh-devel@inria.fr, 36931@debbugs.gnu.org,
Jesse Gibbons <jgibbons2357@gmail.com>
Subject: bug#36931: [swh-devel] bug#36931: guile-bash repository no longer exists?
Date: Tue, 27 Aug 2019 17:27:05 +0200 [thread overview]
Message-ID: <87a7bupr1y.fsf__12041.1454745167$1566920727$gmane$org@inria.fr> (raw)
In-Reply-To: <20190826142435.beivr3d7ydo2rxmb@werner.olasd.eu> (Nicolas Dandrimont's message of "Mon, 26 Aug 2019 16:24:35 +0200")
Hello,
Nicolas Dandrimont <nicolas@dandrimont.eu> skribis:
> We've recently moved the Software Heritage Vault to different infrastructure.
> In doing so, the existing bundles were scrapped; however, the old cache entries
> in the database hadn't been invalidated.
Oh I see.
> I've now made sure that pre-migration cache entries have been invalidated. I've
> also scheduled cooking of objects that had been accessed recently, including
> the one you've referenced, and they should now be available for download (or
> at least trickling in).
It’s much nicer now. I guess we have a good test case. :-)
Thanks for explaining!
Ludo’.
next prev parent reply other threads:[~2019-08-27 15:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 14:18 bug#36931: guile-bash repository no longer exists? Jesse Gibbons
2019-08-05 14:38 ` Ricardo Wurmus
2019-08-05 20:39 ` Björn Höfling
2019-08-23 16:30 ` Ludovic Courtès
2019-08-23 16:32 ` Ludovic Courtès
2019-08-26 11:20 ` Björn Höfling
[not found] ` <87imqn4zfq.fsf@gnu.org>
2019-08-26 14:24 ` bug#36931: [swh-devel] " Nicolas Dandrimont
[not found] ` <20190826142435.beivr3d7ydo2rxmb@werner.olasd.eu>
2019-08-27 15:27 ` Ludovic Courtès [this message]
2019-08-06 1:23 ` Jesse Gibbons
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='87a7bupr1y.fsf__12041.1454745167$1566920727$gmane$org@inria.fr' \
--to=ludovic.courtes@inria.fr \
--cc=36931@debbugs.gnu.org \
--cc=jgibbons2357@gmail.com \
--cc=nicolas@dandrimont.eu \
--cc=swh-devel@inria.fr \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).