unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Jack Hill <jackhill@jackhill.us>
To: 65304@debbugs.gnu.org
Subject: bug#65304: refresh can't update profanity
Date: Tue, 15 Aug 2023 00:26:19 -0400 (EDT)	[thread overview]
Message-ID: <cbff816c-22d9-7014-4fcc-45e5ee568639@jackhill.us> (raw)

I'm using ./pre-inst-env guix from commit 
19a7a824c35eae56ce56e2a460042fb7e2129234. `guix refresh -u profanity` 
doesn't seem to be able to find the new tarball for download. However, if 
I do the update by hand, `guix build` knows how to download the tarball. 
The profanity source record looks like this:

"""
  (source
      (origin
        (method url-fetch)
        (uri
         (string-append 
"https://profanity-im.github.io/tarballs/profanity-"
                        version ".tar.gz"))
        (sha256
         (base32
          "14n45zwc6fxjargqhwqan8fyb7x0ql0hmw56rbjkjfkhpba2qmks"))))
""""

Here's refresh getting confused:

"""
$ ./pre-inst-env guix refresh -u profanity

Starting download of /tmp/guix-file.QV904d
From https:/tarballs/profanity-0.14.0.tar.gz...
In procedure connect*: Connection refused

Starting download of /tmp/guix-file.QV904d
From https://web.archive.org/web/20230815000443/https:/tarballs/profanity-0.14.0.tar.gz...
download failed "https://web.archive.org/web/20230815000443/https:/tarballs/profanity-0.14.0.tar.gz" 404 "NOT FOUND"
Trying to use Disarchive to assemble /tmp/guix-file.QV904d...
could not find its Disarchive specification
failed to download "/tmp/guix-file.QV904d" from "https:/tarballs/profanity-0.14.0.tar.gz"
guix refresh: warning: profanity: version 0.14.0 could not be downloaded and authenticated; not updating
"""

Best,
Jack




             reply	other threads:[~2023-08-15  4:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-15  4:26 Jack Hill [this message]
2023-08-21 20:37 ` bug#65304: refresh can't update profanity Maxim Cournoyer

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=cbff816c-22d9-7014-4fcc-45e5ee568639@jackhill.us \
    --to=jackhill@jackhill.us \
    --cc=65304@debbugs.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).