From: Kei Kebreau <kkebreau@posteo.net>
To: Martin Becze <mjbecze@riseup.net>
Cc: 44902@debbugs.gnu.org
Subject: [bug#44902] [PATCH] gnu: loko: Update to 0.7.0
Date: Fri, 27 Nov 2020 15:56:49 -0500 [thread overview]
Message-ID: <87360utt66.fsf@posteo.net> (raw)
In-Reply-To: <20201127145444.16805-1-mjbecze@riseup.net> (Martin Becze's message of "Fri, 27 Nov 2020 08:54:44 -0600")
[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]
Hi Martin!
Thanks for submitting this patch. I noticed a section of the
loko-scheme package mentions that some R7RS tests failed as of version
0.6.0. Are these tests fixed and runnable as of version 0.7.0?
Kei
Martin Becze <mjbecze@riseup.net> writes:
> * gnu/packages/loko.scm (loko-scheme): Update to 0.7.0
> ---
> gnu/packages/loko.scm | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/gnu/packages/loko.scm b/gnu/packages/loko.scm
> index f6699877f7..737f7250fa 100644
> --- a/gnu/packages/loko.scm
> +++ b/gnu/packages/loko.scm
> @@ -29,7 +29,7 @@
> (define-public loko-scheme
> (package
> (name "loko-scheme")
> - (version "0.6.0")
> + (version "0.7.0")
> (source
> (origin
> (method git-fetch)
> @@ -37,7 +37,7 @@
> (url "https://gitlab.com/weinholt/loko")
> (commit (string-append "v" version))))
> (sha256
> - (base32 "019jlh3lywy912cfz689c9fxgf4bi5700i9k04g7sl5w5gchj36m"))
> + (base32 "1441aarw3vy14zdxyab495ag2fch04v4j89krhbqnqfkz6mdi0vy"))
> (file-name (git-file-name name version))))
> (build-system gnu-build-system)
> (arguments
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-11-27 20:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 14:54 [bug#44902] [PATCH] gnu: loko: Update to 0.7.0 Martin Becze
2020-11-27 20:56 ` Kei Kebreau [this message]
2020-11-28 15:27 ` Martin Becze
2020-11-29 4:37 ` bug#44902: " Kei Kebreau
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=87360utt66.fsf@posteo.net \
--to=kkebreau@posteo.net \
--cc=44902@debbugs.gnu.org \
--cc=mjbecze@riseup.net \
/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).