unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Christopher Howard <christopher@librehacker.com>
Cc: 56537-done@debbugs.gnu.org
Subject: bug#56537: sushi: build failure, bad URI
Date: Wed, 13 Jul 2022 08:45:55 -0400	[thread overview]
Message-ID: <87a69d2nb0.fsf@gmail.com> (raw)
In-Reply-To: <Ys663qtMx/EOtzHZ@nightshade> (Christopher Howard's message of "Wed, 13 Jul 2022 04:30:22 -0800")

Hi Christopher,

Christopher Howard <christopher@librehacker.com> writes:

> Hello, I am trying to do a system reconfigure to update my system, but eventually gnome dependency "sushi" tries to build and fails. I believe the problem is that Guix is trying to download https://download.gnome.org/sources/sushi/42.0/sushi-42.0.tar.xz but the path is actually https://download.gnome.org/sources/sushi/42/sushi-42.0.tar.xz.

Indeed.  Fixed with this:

--8<---------------cut here---------------start------------->8---
modified   gnu/packages/gnome.scm
@@ -1588,7 +1588,7 @@ (define-public sushi
     (source (origin
               (method url-fetch)
               (uri (string-append "mirror://gnome/sources/" name "/"
-                                  (version-major+minor version) "/"
+                                  (version-major version) "/"
                                   name "-" version ".tar.xz"))
               (sha256
                (base32
--8<---------------cut here---------------end--------------->8---

Pushed to master as 6d5b3df7afefa6b038c8430ae3e1650af986ad1e.

Sorry for the breakage, and thank you for reporting it!

Maxim




      reply	other threads:[~2022-07-13 12:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-13 12:30 bug#56537: sushi: build failure, bad URI Christopher Howard
2022-07-13 12:45 ` Maxim Cournoyer [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=87a69d2nb0.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=56537-done@debbugs.gnu.org \
    --cc=christopher@librehacker.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).