From: hub.lombard@free.fr
To: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Cc: Vagrant Cascadian <vagrant@debian.org>,
Giovanni Biscuolo <g@xelera.eu>,
63551@debbugs.gnu.org, help-guix@gnu.org
Subject: bug#63551: cpp-mustache-4.1 build fails
Date: Wed, 17 May 2023 15:35:19 +0200 (CEST) [thread overview]
Message-ID: <1500510256.722667843.1684330519587.JavaMail.root@zimbra49-e8.priv.proxad.net> (raw)
Message-ID: <20230517133519.iZhoarXBV0pRXmC42knlij5BQh1y9CH0MkT2jZV90k0@z> (raw)
In-Reply-To: <20230517140722.4e47f582@primary_laptop>
Hi,
----- Mail original -----
De: "Denis 'GNUtoo' Carikli" <GNUtoo@cyberdimension.org>
À: "Giovanni Biscuolo" <g@xelera.eu>
Cc: 63551@debbugs.gnu.org, "hub lombard" <hub.lombard@free.fr>, help-guix@gnu.org, "Vagrant Cascadian" <vagrant@debian.org>
Envoyé: Mercredi 17 Mai 2023 14:07:22
Objet: Re: cpp-mustache-4.1 build fails
On Wed, 17 May 2023 12:44:58 +0200
Giovanni Biscuolo <g@xelera.eu> wrote:
> Since commit 4ed8c0b is setting version to 5.0.0 and that version
> works (does it?), I'd go for an "update to 5.0.0" patch
It at least builds fine.
Thanks a lot for the advises.
>>> Good to know, thxs! Will investigate and report advices.
Denis.
next prev parent reply other threads:[~2023-05-18 6:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2074528809.707359788.1684054259894.JavaMail.root@zimbra49-e8.priv.proxad.net>
2023-05-14 8:55 ` 1 dependencies couldn't be built. cpp-mustache-4.1 hub.lombard
2023-05-14 15:16 ` Vagrant Cascadian
2023-05-14 15:42 ` hub.lombard
2023-05-15 12:49 ` Denis 'GNUtoo' Carikli
2023-05-15 18:17 ` hub.lombard
2023-05-15 23:19 ` Denis 'GNUtoo' Carikli
2023-05-16 6:06 ` hub.lombard
2023-05-17 10:44 ` cpp-mustache-4.1 build fails Giovanni Biscuolo
2023-05-17 12:07 ` Denis 'GNUtoo' Carikli
2023-05-17 13:35 ` hub.lombard [this message]
2023-05-17 13:35 ` bug#63551: " hub.lombard
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=1500510256.722667843.1684330519587.JavaMail.root@zimbra49-e8.priv.proxad.net \
--to=hub.lombard@free.fr \
--cc=63551@debbugs.gnu.org \
--cc=GNUtoo@cyberdimension.org \
--cc=g@xelera.eu \
--cc=help-guix@gnu.org \
--cc=vagrant@debian.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.
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).