* bug#27316: [PATCH] gnu: Fix libgxps origin uri.
@ 2017-06-10 19:13 nee
2017-06-11 0:18 ` nee
0 siblings, 1 reply; 2+ messages in thread
From: nee @ 2017-06-10 19:13 UTC (permalink / raw)
To: 27316
[-- Attachment #1: Type: text/plain, Size: 48 bytes --]
There is a slash missing in the uri of libgxps.
[-- Attachment #2: 0001-gnu-Fix-libgxps-origin-uri.patch --]
[-- Type: text/x-patch, Size: 954 bytes --]
From 0b5155822f92d0e48b57a09148026053b94dfb03 Mon Sep 17 00:00:00 2001
From: nee <nee.git@cock.li>
Date: Sat, 10 Jun 2017 20:55:19 +0200
Subject: [PATCH] gnu: Fix libgxps origin uri.
* gnu/packages/gnome.scm (libgxps)[src]: Fix origin uri.
---
gnu/packages/gnome.scm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gnu/packages/gnome.scm b/gnu/packages/gnome.scm
index 293df870e..d3f734450 100644
--- a/gnu/packages/gnome.scm
+++ b/gnu/packages/gnome.scm
@@ -294,7 +294,7 @@ access the common Google services, and has full asynchronous support.")
(version "0.2.5")
(source (origin
(method url-fetch)
- (uri (string-append "mirror://gnome/sources" name "/"
+ (uri (string-append "mirror://gnome/sources/" name "/"
(version-major+minor version) "/"
name "-" version ".tar.xz"))
(sha256
--
2.13.1
^ permalink raw reply related [flat|nested] 2+ messages in thread
* bug#27316: [PATCH] gnu: Fix libgxps origin uri.
2017-06-10 19:13 bug#27316: [PATCH] gnu: Fix libgxps origin uri nee
@ 2017-06-11 0:18 ` nee
0 siblings, 0 replies; 2+ messages in thread
From: nee @ 2017-06-11 0:18 UTC (permalink / raw)
To: 27316-done
duplicate of bug#27313 which is already pushed
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-06-11 0:19 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-06-10 19:13 bug#27316: [PATCH] gnu: Fix libgxps origin uri nee
2017-06-11 0:18 ` nee
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).