From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: 32836@debbugs.gnu.org
Cc: Pierre Neidhardt <mail@ambrevar.xyz>
Subject: bug#32836: emacs-magit is broken (and probably others) due to package renaming
Date: Tue, 25 Sep 2018 15:54:42 +0200 [thread overview]
Message-ID: <20180925155442.6cfb1c06@alma-ubu> (raw)
[-- Attachment #1: Type: text/plain, Size: 960 bytes --]
Commit
5c8031ff7382ec9079040d08ae5a05b4dd2352b7
mass-renamed emacs-packages from "foo" to "emacs-foo". Unfortunately,
some package definitions use the package-name for building the URL.
That is for example the case in emacs-magit:
(define-public emacs-magit
(package
(name "emacs-magit")
(version "2.13.0")
(source (origin
(method url-fetch)
(uri (string-append
"https://github.com/magit/magit/releases/download/"
version "/" name "-" version ".tar.gz"))
Thus, it can no longer be built:
Starting download of /gnu/store/h01ag9sr8nxiqbnlblmxplnv43a2005j-emacs-magit-2.13.0.tar.gz
From https://github.com/magit/magit/releases/download/2.13.0/emacs-magit-2.13.0.tar.gz...
ERROR: download failed "https://github.com/magit/magit/releases/download/2.13.0/emacs-magit-2.13.0.tar.gz" 404 "Not Found"
Pierre, could you have a look into it?
Thanks
Björn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next reply other threads:[~2018-09-25 13:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 13:54 Björn Höfling [this message]
2018-09-25 15:04 ` bug#32836: emacs-magit is broken (and probably others) due to package renaming Pierre Neidhardt
2018-09-25 19:29 ` Taylan Kammer
2018-09-25 17:58 ` Pierre Neidhardt
2018-09-26 9:38 ` Ludovic Courtès
2018-09-26 22:37 ` Björn Höfling
2018-09-25 22:23 ` Alex Kost
2018-09-26 16:21 ` Nils Gillmann
2018-09-26 17:05 ` Pierre Neidhardt
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=20180925155442.6cfb1c06@alma-ubu \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=32836@debbugs.gnu.org \
--cc=mail@ambrevar.xyz \
/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.