all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 40074@debbugs.gnu.org
Subject: bug#40074: trilinos-serial-xyce source disappeared
Date: Tue, 18 Oct 2022 17:37:02 +0200	[thread overview]
Message-ID: <86ilkhywgx.fsf@gmail.com> (raw)
In-Reply-To: <868sc71dr9.fsf@gmail.com> (zimoun's message of "Thu, 15 Oct 2020 21:38:02 +0200")

Hi,

On Thu, 15 Oct 2020 at 21:38, zimoun <zimon.toutoune@gmail.com> wrote:
> On Sun, 15 Mar 2020 at 13:48, Marius Bakke <mbakke@fastmail.com> wrote:

> First patch, replace ’url-fetch’ by ’git-fetch’ with creating a Git repo
> from the build farm tarball and falling back to SWH.  This does not
> change the integrity checksum.  And it avoids the “pressure“ on the
> build farm.
>
> Second patch, update the upstream source to the new good ’git-fetch’.
> And this change the integrity checksum.  Maybe upstream released a new
> version.

Commit b729be989f137749430779499b8c0dd1d54f2a18 did the replacement by
’git-fetch’ using the upstream repo.

It is hard to compare the both sources but it does not really matter
since the new one is the official upstream one.

Well, what remains is the guarantee that ’guix time-machine’ will still
work even if the Guix project looses the tarball.

This case should be covered by Disarchive and SWH.  Well, is it worth to
keep open this issue when the question about the time-machine coverage
is bigger than just this example.

Closing?

Cheers,
simon




  reply	other threads:[~2022-10-18 16:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-15 12:48 bug#40074: trilinos-serial-xyce source disappeared Marius Bakke
2020-10-15 19:38 ` zimoun
2022-10-18 15:37   ` zimoun [this message]
2022-11-03  9:55     ` zimoun

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=86ilkhywgx.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=40074@debbugs.gnu.org \
    --cc=mbakke@fastmail.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 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.