GNU bug report logs -
#26502
[PATCH] gnu: racket: Update to 6.8.
Previous Next
Reported by: Arun Isaac <arunisaac <at> systemreboot.net>
Date: Fri, 14 Apr 2017 20:26:01 UTC
Severity: normal
Tags: patch
Done: Arun Isaac <arunisaac <at> systemreboot.net>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Sun, 16 Apr 2017 02:53:08 +0530
with message-id <58c349c7.AEMAJOUepUQAAAAAAAAAAAO1L9sAAAACwQwAAAAAAAW9WABY8o9J <at> mailjet.com>
and subject line Re: bug#26502: [PATCH] gnu: racket: Update to 6.8.
has caused the debbugs.gnu.org bug report #26502,
regarding [PATCH] gnu: racket: Update to 6.8.
to be marked as done.
(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)
--
26502: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=26502
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
* gnu/packages/scheme.scm (racket): Update to 6.8.
---
gnu/packages/scheme.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gnu/packages/scheme.scm b/gnu/packages/scheme.scm
index 1ccf62586..f6aee005c 100644
--- a/gnu/packages/scheme.scm
+++ b/gnu/packages/scheme.scm
@@ -392,7 +392,7 @@ implementation techniques and as an expository tool.")
(define-public racket
(package
(name "racket")
- (version "6.6")
+ (version "6.8")
(source (origin
(method url-fetch)
(uri (list (string-append "http://mirror.racket-lang.org/installers/"
@@ -402,7 +402,7 @@ implementation techniques and as an expository tool.")
version "/racket/racket-" version "-src-unix.tgz")))
(sha256
(base32
- "1kzdi1n6h6hmz8zd9k8r5a5yp2ryi4w3c2fjm1k6cqicn18cwaxz"))))
+ "1l9z1a0r5zydr50cklx9xjw3l0pwnf64i10xq7112fl1r89q3qgv"))))
(build-system gnu-build-system)
(arguments
'(#:phases
--
2.12.2
[Message part 3 (message/rfc822, inline)]
Pushed!
Marius Bakke writes:
> LGTM. Trivial changes like these are generally OK to push without going
> through this list as outlined in HACKING.
>
> Just be mindful about the amount of rebuilds it will cause. If `guix
> refresh -l <package>` prints more than ~300 dependents, it should go
> through the "staging" or "core-updates" branch. See this thread for the
> branching strategy:
>
> https://lists.gnu.org/archive/html/guix-devel/2016-10/msg00933.html
Sure, will keep that in mind!
This bug report was last modified 8 years and 124 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.