From: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
To: hub.lombard@free.fr
Cc: help-guix@gnu.org, Vagrant Cascadian <vagrant@debian.org>
Subject: Re: 1 dependencies couldn't be built. cpp-mustache-4.1
Date: Tue, 16 May 2023 01:19:42 +0200 [thread overview]
Message-ID: <20230516011942.365f9980@primary_laptop> (raw)
In-Reply-To: <322365109.713816747.1684174646633.JavaMail.root@zimbra49-e8.priv.proxad.net>
[-- Attachment #1: Type: text/plain, Size: 496 bytes --]
On Mon, 15 May 2023 20:17:26 +0200 (CEST)
hub.lombard@free.fr wrote:
> Hi Denis!
Hi,
> Thank you for your answer :) I have downloaded the 2 patches
>
> and I plan to apply it when I have time...
Note that I didn't send them to Guix yet.
So if a Guix maintainer (or someone else with good ideas) could tell me
what is the best approach here, I would know which one to send.
Or should I send both in the same patch serie and make the maintainers
choose between both?
Denis.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-05-15 23:20 UTC|newest]
Thread overview: 13+ 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 [this message]
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
2023-05-17 13:35 ` bug#63551: " hub.lombard
2023-05-17 10:06 Giovanni Biscuolo
2023-11-23 16:41 ` bug#63551: (no subject) Denis 'GNUtoo' Carikli
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230516011942.365f9980@primary_laptop \
--to=gnutoo@cyberdimension.org \
--cc=help-guix@gnu.org \
--cc=hub.lombard@free.fr \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.