From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: python-updates
Date: Thu, 04 Aug 2016 22:56:51 +0200 [thread overview]
Message-ID: <87oa58s164.fsf_-_@gnu.org> (raw)
In-Reply-To: <20160711155047.GA4630@jasmine> (Leo Famulari's message of "Mon, 11 Jul 2016 11:50:47 -0400")
[-- Attachment #1: Type: text/plain, Size: 738 bytes --]
Hello!
Leo Famulari <leo@famulari.name> skribis:
> On Mon, Jul 11, 2016 at 10:29:48AM +0200, Ludovic Courtès wrote:
>> The ‘python-updates’ branch would seem right to me.
>
> The brand new python-updates branch is now ready for more Python-related
> commits!
The build farm is almost idle now, apart from a long list of mips64el
builds. So I think it’s time to merge master in python-updates and get
it built! Thoughts?
I think it’s a good idea to upgrade Guile 2.0 at the same time, since
that’s a safe upgrade. The patch below does that, but note that it does
not change ‘guile-2.0/fixed’, which is the Guile we use in all the
derivations; that one we’ll upgrade in core-updates.
Ludo’.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 1582 bytes --]
diff --git a/gnu/packages/guile.scm b/gnu/packages/guile.scm
index f50605a..f39e768 100644
--- a/gnu/packages/guile.scm
+++ b/gnu/packages/guile.scm
@@ -130,14 +130,14 @@ without requiring the source code to be rewritten.")
(define-public guile-2.0
(package
(name "guile")
- (version "2.0.11")
+ (version "2.0.12")
(source (origin
(method url-fetch)
(uri (string-append "mirror://gnu/guile/guile-" version
".tar.xz"))
(sha256
(base32
- "1qh3j7308qvsjgwf7h94yqgckpbgz2k3yqdkzsyhqcafvfka9l5f"))
+ "1sdpjq0jf1h65w29q0zprj4x6kdp5jskkvbnlwphy9lvdxrqg0fy"))
(patches (search-patches "guile-arm-fixes.patch"))))
(build-system gnu-build-system)
(native-inputs `(("pkgconfig" ,pkg-config)))
@@ -199,7 +199,17 @@ without requiring the source code to be rewritten.")
(define-public guile-2.0/fixed
;; A package of Guile 2.0 that's rarely changed. It is the one used
;; in the `base' module, and thus changing it entails a full rebuild.
- guile-2.0)
+ (package
+ (inherit guile-2.0)
+ (version "2.0.11")
+ (source (origin
+ (method url-fetch)
+ (uri (string-append "mirror://gnu/guile/guile-" version
+ ".tar.xz"))
+ (sha256
+ (base32
+ "1qh3j7308qvsjgwf7h94yqgckpbgz2k3yqdkzsyhqcafvfka9l5f"))
+ (patches (search-patches "guile-arm-fixes.patch"))))))
(define-public guile-next
(package (inherit guile-2.0)
next prev parent reply other threads:[~2016-08-04 20:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-03 1:10 [PATCH 0/6] Pytest update Leo Famulari
2016-07-03 1:10 ` [PATCH 1/6] gnu: python-virtualenv: Disable tests Leo Famulari
2016-07-03 1:10 ` [PATCH 2/6] gnu: python-pip: " Leo Famulari
2016-07-03 1:10 ` [PATCH 3/6] gnu: python-scripttest: " Leo Famulari
2016-07-03 1:10 ` [PATCH 4/6] gnu: python-pytest: Update to 2.9.2 Leo Famulari
2016-07-03 1:10 ` [PATCH 5/6] gnu: python-pytest-runner: Update to 2.8 Leo Famulari
2016-07-03 1:10 ` [PATCH 6/6] gnu: python-cryptopgraphy: Update to 1.4 Leo Famulari
2016-07-03 5:58 ` [PATCH 0/6] Pytest update Efraim Flashner
2016-07-03 20:15 ` Leo Famulari
2016-07-07 1:13 ` Leo Famulari
2016-07-11 8:29 ` Ludovic Courtès
2016-07-11 15:50 ` Leo Famulari
2016-07-11 16:05 ` Leo Famulari
2016-07-12 9:14 ` python-updates! Ludovic Courtès
2016-07-16 21:23 ` python-updates! Christopher Allan Webber
2016-08-04 20:56 ` Ludovic Courtès [this message]
2016-08-04 21:23 ` python-updates Leo Famulari
2016-08-04 21:54 ` python-updates Leo Famulari
2016-08-05 12:13 ` python-updates Andreas Enge
2016-08-05 15:06 ` python-updates Leo Famulari
2016-08-05 15:43 ` python-updates Leo Famulari
2016-08-05 21:42 ` python-updates Andreas Enge
2016-08-05 21:57 ` python-updates Mark H Weaver
2016-08-05 23:03 ` python-updates Leo Famulari
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=87oa58s164.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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).