unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 25638-done@debbugs.gnu.org
Subject: bug#25638: [Hunting]: linux libre 4.4.18 tarball has disappeared
Date: Wed, 16 Sep 2020 09:32:35 +0200	[thread overview]
Message-ID: <CAJ3okZ12iBb4RTUSDOJfKPt2Dsav8vvU2--6tWv-jiKT70DkuQ@mail.gmail.com> (raw)
In-Reply-To: <87d02mswud.fsf@gnu.org>

On Tue, 15 Sep 2020 at 20:45, Ludovic Courtès <ludo@gnu.org> wrote:

> It’s available from
> <https://ci.guix.gnu.org/file/linux-libre-4.4.18-gnu.tar.xz/sha256/0k8k17in7dkjd9d8zg3i8l1ax466dba6bxw28flxizzyq8znljps>
> now (found a copy at hydra.gnunet.org!).  (This URL is served by ‘guix
> publish’.)  There’s no GC root though.

Thank you for explaining.
I did not know about hydra.gnunet.org, cool! :-)


> > Is such version reachable with "guix time-machine"?  I guess no, so does
> > it make sense to keep the tarball?
>
> Good question, maybe not.

Well, Guix could keep all the tarballs until the Tarball Heritage is up. :-)


> > Such issue is discussed in #42162, especially the thread starting here:
> >
> >    <http://issues.guix.gnu.org/issue/42162#4>

[...]

> > Therefore, if the linux-libre 4.4.18 tarballs is substituable on
> > <ci.guix.gnu.org>, I suggest to close this bug.  WDYT?
>
> Yeah, we can probably close it.  The more general issue of tarballs in
> general, and linux-libre tarballs in particular, can be dealt with in
> the issue above.

I am closing.  Feel free to reopen if I am making a mistake.

All the best,
simon




      reply	other threads:[~2020-09-16  7:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-06 21:50 bug#25638: linux libre tarball has disappeared Ricardo Wurmus
2017-02-06 21:55 ` Ricardo Wurmus
2017-02-07 13:28 ` Ludovic Courtès
2020-09-15 16:29   ` bug#25638: [Hunting]: linux libre 4.4.18 " zimoun
2020-09-15 18:45     ` Ludovic Courtès
2020-09-16  7:32       ` zimoun [this message]

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=CAJ3okZ12iBb4RTUSDOJfKPt2Dsav8vvU2--6tWv-jiKT70DkuQ@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=25638-done@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    /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).