From: "Ludovic Courtès" <ludo@gnu.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: Julien Lepiller <julien@lepiller.eu>,
57581-done@debbugs.gnu.org,
Maxim Cournoyer <maxim.cournoyer@gmail.com>,
zimoun <zimon.toutoune@gmail.com>
Subject: bug#57581: Failing to build the website
Date: Tue, 13 Sep 2022 16:41:10 +0200 [thread overview]
Message-ID: <87y1un2v7d.fsf@gnu.org> (raw)
In-Reply-To: <87o7vr2lk7.fsf@pelzflorian.de> (pelzflorian@pelzflorian.de's message of "Wed, 07 Sep 2022 18:31:20 +0200")
Hi,
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:
> zimoun <zimon.toutoune@gmail.com> writes:
>> The culprit seems the package ’qtserialport’ in ’packages-builder’ from
>> (apps packages builder). Maybe introduced by commit
>> 1ef04fb2288dade3ad2883026ae286a68ef13a1e.
>
> This was a first failing commit for me too, but the reason the website
> does not build appears to be the license field of qtshadertools in
> commit 1d65ff8fdeb20cc2db956093f0ecb1f3f72afc0e (Cc to Maxim). I could
> make a patch but not today. Maxim, would you fix it?
Fixed in e61c581805b2338ea8feaac86617c5d7bff41c41, thanks for the
investigation!
> I don’t know if there is a way to catch such mistakes early. Field
> sanitizers?
Yes, we should do that. We can arrange to have most checks done at
compile time, similar to how the ‘synopsis’ and ‘description’ sanitizers
work (well, with extra macro magic).
Ludo’.
next prev parent reply other threads:[~2022-09-13 14:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-04 15:18 bug#57581: Failing to build the website Julien Lepiller
2022-09-05 8:35 ` zimoun
2022-09-05 10:27 ` Julien Lepiller
2022-09-05 11:57 ` zimoun
2022-09-05 10:59 ` pelzflorian (Florian Pelz)
2022-09-05 12:04 ` zimoun
2022-09-05 12:50 ` Julien Lepiller
2022-09-05 14:35 ` zimoun
2022-09-07 16:31 ` pelzflorian (Florian Pelz)
2022-09-07 17:07 ` zimoun
2022-09-07 17:14 ` Julien Lepiller
2022-09-08 8:00 ` zimoun
2022-09-13 14:41 ` Ludovic Courtès [this message]
2022-09-14 6:37 ` zimoun
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=87y1un2v7d.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=57581-done@debbugs.gnu.org \
--cc=julien@lepiller.eu \
--cc=maxim.cournoyer@gmail.com \
--cc=pelzflorian@pelzflorian.de \
--cc=zimon.toutoune@gmail.com \
/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).