From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 44723@debbugs.gnu.org
Subject: bug#44723: Latest binary tarball & Hurd qcow2 image unavailable (502)
Date: Thu, 19 Nov 2020 09:05:30 +0100 [thread overview]
Message-ID: <878saxixf9.fsf@gnu.org> (raw)
In-Reply-To: <CAJ3okZ3fawBARjyc+0q-hG468MooXEk2Gy5c38YG89VqErhM7A@mail.gmail.com> (zimoun's message of "Wed, 18 Nov 2020 18:50:03 +0100")
Hi,
zimoun <zimon.toutoune@gmail.com> skribis:
> On Wed, 18 Nov 2020 at 18:46, Ludovic Courtès <ludo@gnu.org> wrote:
>
>> I guess it’s OK for Guix System ISO images because a fresh one gets
>> built at each evaluation, roughly, but perhaps the Hurd images are not
>> rebuilt frequently enough and the changes that they’re GC’d are higher.
>>
>> I don’t have a good solution for that, we’re consuming storage space too
>> quickly with all these images currently. :-/
>
> Does it make sense to only keep the latest? And GC all the older one
> except the stable one (pinned).
We could change ‘cleanup-cuirass-roots’ (the mcron job I showed) to keep
at least one ‘hurd-barebones.qcow2’ root. Help welcome!
Ludo’.
next prev parent reply other threads:[~2020-11-19 8:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 16:39 bug#44723: Latest binary tarball & Hurd qcow2 image unavailable (502) Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-11-18 17:45 ` Ludovic Courtès
2020-11-18 17:50 ` zimoun
2020-11-18 19:16 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-11-18 20:13 ` Bengt Richter
2020-11-19 8:05 ` Ludovic Courtès [this message]
2020-11-19 8:43 ` zimoun
2020-11-19 9:14 ` Mathieu Othacehe
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=878saxixf9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=44723@debbugs.gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).