From: swedebugia <swedebugia@riseup.net>
To: 33932@debbugs.gnu.org
Subject: bug#33932: Artanis fails to build - 0.3.1 is out
Date: Sun, 30 Dec 2018 22:52:33 +0100 [thread overview]
Message-ID: <3a50ddf2-c212-aa80-987e-c1b4074ae0b6@riseup.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 902 bytes --]
Hi
We should upgrade.
I earlier tried building 0.2.5 but failed, see def. below.
(define-public artanis
(package
(name "artanis")
;; The 0.2.5 tarball does not build. See upstream bugreport at
;;
https://lists.gnu.org/archive/html/bug-artanis/2018-11/msg00000.html
(version "0.2.5.af624e50")
(source (origin
(method git-fetch)
(uri (git-reference
(url "https://git.savannah.gnu.org/git/artanis.git")
(commit "af624e508e9997bd2e20c8c7063d986694f11209")))
(file-name (string-append name "-" version "-checkout"))
(sha256
(base32
"0y1rx09jljdx6g6nq6y635f8svm8kazib7n4bgivi3yiy2c5v7ck"))
--
Cheers Swedebugia
[-- Attachment #2: Type: text/html, Size: 2037 bytes --]
next reply other threads:[~2018-12-30 21:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-30 21:52 swedebugia [this message]
2018-12-31 12:33 ` bug#33932: Artanis fails to build - 0.3.1 is out Ricardo Wurmus
2019-01-02 21:50 ` swedebugia
2019-01-02 22:50 ` bug#33932: [PATCH] gnu: artanis: Move to web.scm and update to 0.3.1. (was: Re: bug#33932: Artanis fails to build - 0.3.1 is out) swedebugia
2019-01-03 11:39 ` Ricardo Wurmus
2019-01-03 16:17 ` bug#33932: [PATCH] gnu: artanis: Move to web.scm and update to 0.3.1 swedebugia
2019-01-03 19:19 ` bug#33932: [PATCH] gnu: artanis: Move to web.scm and update to 0.3.1. (was: Re: bug#33932: Artanis fails to build - 0.3.1 is out) Christopher Baines
2019-01-03 21:39 ` bug#33932: [PATCH] gnu: artanis: Move to web.scm and update to 0.3.1 swedebugia
2019-01-04 20:58 ` swedebugia
[not found] ` <871s5st5f3.fsf@elephly.net>
2019-01-06 21:04 ` swedebugia
2019-01-28 14:22 ` Ricardo Wurmus
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=3a50ddf2-c212-aa80-987e-c1b4074ae0b6@riseup.net \
--to=swedebugia@riseup.net \
--cc=33932@debbugs.gnu.org \
/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).