From: muradm <mail@muradm.net>
To: Maxime Devos <maximedevos@telenet.be>
Cc: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>,
56136@debbugs.gnu.org
Subject: [bug#56136] [PATCH] gnu: freedesktop: Add basu 0.2.0.
Date: Wed, 22 Jun 2022 16:14:07 +0300 [thread overview]
Message-ID: <87o7ykbztl.fsf@muradm.net> (raw)
In-Reply-To: <1f1adb50a6b31ab7762a2779d48a53284579dc80.camel@telenet.be>
[-- Attachment #1: Type: text/plain, Size: 1328 bytes --]
For v3 with lint I got only this:
gnu/packages/freedesktop.scm:726:14: basu@0.2.0: no period allowed
at the end of the synopsis
v4 has no lint warnings.
--
muradm
Maxime Devos <maximedevos@telenet.be> writes:
> [[PGP Signed Part:Undecided]]
> muradm schreef op wo 22-06-2022 om 15:07 [+0300]:
>> > * pkg-config is almost surely needs to be native-inputs
>> > (it's
>> > like a
>> > (cross-) compiler). "./pre-inst-env guix lint basu"
>> > probably would
>> > report this.
>> Didn't see any warning or else.
>
> Can't reproduce:
>
> $ guix lint -L . basu # (*)
> ./a.scm:24:5: basu@0.2.0: ‘pkg-config’ zou waarschijnlijk
> inheemse voer moeten zijn
> ./a.scm:25:14: basu@0.2.0: geen punt toegestaan aan het einde
> van de synopsis
> fetching CVE database for 2022...
> fetching CVE database for 2021...
> fetching CVE database for 2020...
> [...]
>
> (i.e.: the translation for 'native' is in retrospect confusing,
> pkg-config should
> probably be a native-input instead and a synopsis may not end
> with a period)
>
> (*): I put the package definition into a separate file, hence
> the -L .. In your case,
> that would be './pre-inst-env guix lint basu' instead
>
> Greetings,
> Maxime.
>
> [[End of PGP Signed Part]]
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2022-06-22 13:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 8:40 [bug#56136] [PATCH] gnu: freedesktop: Add basu 0.2.0 muradm
2022-06-22 10:02 ` Maxime Devos
2022-06-22 10:32 ` [bug#56136] [PATCH v2] " muradm
2022-06-22 11:54 ` [bug#56136] [PATCH] " Maxime Devos
2022-06-22 12:00 ` [bug#56136] [PATCH v3] " muradm
2022-06-22 12:07 ` [bug#56136] [PATCH] " muradm
2022-06-22 13:08 ` Maxime Devos
2022-06-22 13:14 ` muradm [this message]
2022-06-22 13:21 ` [bug#56136] [PATCH v4] " muradm
2022-06-22 19:36 ` bug#56136: " Liliana Marie Prikler
2022-06-22 16:32 ` [bug#56136] [PATCH] " Maxime Devos
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=87o7ykbztl.fsf@muradm.net \
--to=mail@muradm.net \
--cc=56136@debbugs.gnu.org \
--cc=liliana.prikler@ist.tugraz.at \
--cc=maximedevos@telenet.be \
/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).