all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Giovanni Biscuolo <g@xelera.eu>
To: 63551@debbugs.gnu.org
Cc: hub.lombard@free.fr, help-guix@gnu.org,
	Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>,
	Vagrant Cascadian <vagrant@debian.org>
Subject: cpp-mustache-4.1 build fails
Date: Wed, 17 May 2023 12:44:58 +0200	[thread overview]
Message-ID: <877ct7jkyd.fsf@xelera.eu> (raw)
In-Reply-To: <20230515144856.26b5d1e4@primary_laptop>

[-- Attachment #1: Type: text/plain, Size: 1931 bytes --]

Hello 

thank you very much Hubert for your report: errors like the one you
found (packages build failures) are bugs, next time please report them
to bug-guix@gnu.org; better to close a non-bug than to miss an actual
one ;-)

As you can see I've now filed a new bug: bug#63551

Thank you also to Vagrant and Denis for the heads up, please submit
further comments or patches to 63551@debbugs.gnu.org

Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> writes:

[...]

> There are several approaches here and I've patches for two of them if
> needed (I've attached them):
> (1) backport some upstream patches:
>     - There are 2 catch2 updates, they can be squashed into 1 patch
>     - We also need a patch for fixing unused variables.
> (2) Update cpp-mustache: There is an upstream commit
>     (https://github.com/kainjow/Mustache/commit/4ed8c0b5a2a43d59394bd6900dc04e738dbf8c02)
>     that change some version string. I've asked upstream if that was
>     the 5.0.0 release but so far I got no answer.
>     https://github.com/kainjow/Mustache/issues/65
>
> (1) is 0001-gnu-cpp-mustache-fix-build-with-newer-glibc.patch
> (2) is 0001-bug-reported-upstream-for-release-info-gnu-cpp-musta.patch
>
> I didn't share the patches yet because I was waiting on upstream to
> clarify the situation with the lack of 5.0.0 tag.

Please do not wait for an official upstream "release" (git tag,
actually) for cpp-mustache, I guess upstream just forgot to tag it: Guix
is full of "not officially" released or properly tagged packages,
sources are often taken from carefully selected git commits (I've
recently proposed a patch for dia, that is in a very similar situation)

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

My two cents.

[...]

Happy hacking! Gio'

-- 
Giovanni Biscuolo

Xelera IT Infrastructures

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]

  parent reply	other threads:[~2023-05-17 10:45 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
2023-05-16  6:06           ` hub.lombard
2023-05-17 10:44       ` Giovanni Biscuolo [this message]
2023-05-17 12:07         ` cpp-mustache-4.1 build fails 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=877ct7jkyd.fsf@xelera.eu \
    --to=g@xelera.eu \
    --cc=63551@debbugs.gnu.org \
    --cc=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.