unofficial mirror of bug-guix@gnu.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: Thu, 15 Oct 2020 21:38:02 +0200	[thread overview]
Message-ID: <868sc71dr9.fsf@gmail.com> (raw)
In-Reply-To: <87sgi9lr77.fsf@devup.no> (Marius Bakke's message of "Sun, 15 Mar 2020 13:48:12 +0100")

Dear,

On Sun, 15 Mar 2020 at 13:48, Marius Bakke <mbakke@fastmail.com> wrote:
> The source URI for 'trilios-serial-xyce' serves a 404 page.  Following
> download links from the home page only leads to the git repository.
>
> This package should probably be changed to download a tagged git
> revision instad of attempting to fetch a defunct tarball.
>
> ci.guix.gnu.org has a copy of the previous source tarball so it's not
> very urgent (anyone coming here can add "--fallback" to their guix
> invokation to get it).

The commit 74cb33c22818b25d1b9c6d576352fc8249832d34 [1] transitioned
from ’url-fetch’ to ’git-fetch’ for missing upstream (even disappeared
one).   I am proposing similar strategy:

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.


WDYT?

1: <http://issues.guix.gnu.org/issue/43426>


All the best,
simon




  reply	other threads:[~2020-10-15 19:39 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 [this message]
2022-10-18 15:37   ` zimoun
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

  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=868sc71dr9.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 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).