all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: muradm <mail@muradm.net>
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 18:32:04 +0200	[thread overview]
Message-ID: <bd50388de568089b14c6f76982e3e7fef326b800.camel@telenet.be> (raw)
In-Reply-To: <87o7ykbztl.fsf@muradm.net>

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

muradm schreef op wo 22-06-2022 om 16:14 [+0300]:
> 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

My comment was on the v2, not the v3.  You wrote that:

> >   * 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.

... which would seem to be somehow a bug in "guix lint" or an incorrect
use of "guix lint".  Basically, I don't understand how you didn't get
any warnings.

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

      parent reply	other threads:[~2022-06-22 16:33 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
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         ` Maxime Devos [this message]

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=bd50388de568089b14c6f76982e3e7fef326b800.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=56136@debbugs.gnu.org \
    --cc=liliana.prikler@ist.tugraz.at \
    --cc=mail@muradm.net \
    /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.