all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: phodina <phodina@protonmail.com>
Cc: 55827@debbugs.gnu.org
Subject: [bug#55827] [PATCH v2] gnu: Add kismet.
Date: Tue, 07 Jun 2022 13:04:44 +0200	[thread overview]
Message-ID: <9a7cf69098315734ebdd3cb37de76a224abb7865.camel@telenet.be> (raw)
In-Reply-To: <DPeYpZeNFQt0_ISxPLHDCHtMvLJCa0UKOdDduR44U2noBmFwMANhh5o8TuGCchEd76lvHvzxzJluBcEzypBRITlkCp1Q4pqPGOG-tqon6gQ=@protonmail.com>

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

phodina schreef op di 07-06-2022 om 09:57 [+0000]:
> I'm not a laywer so can't really say if they are compatible or not in
> this case. Therefore the websockets are now removed by configuration
> flag.
> 
> However, if I think the best approach would be to create issue/bring
> this issue to the developers of Kismet.

I don't think this is necessary, because of ...

> However, according to v4.0.0 in the changelog, [libwebsockets] is
> Expat (‘MIT’) licensed, so maybe all that's needed is correcting the
> license information?

(basically, the license information in the package definition and the
LICENSE file of libwebsockets do not seem to agree).

WDYT?

Greetings,
Maxime.

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

  reply	other threads:[~2022-06-07 12:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07  7:41 [bug#55827] [PATCH] gnu: Add kismet phodina via Guix-patches via
2022-06-07  7:50 ` Maxime Devos
2022-06-07  8:06 ` Maxime Devos
2022-06-07  9:57   ` [bug#55827] [PATCH v2] " phodina via Guix-patches via
2022-06-07 11:04     ` Maxime Devos [this message]
2022-06-10  8:44       ` phodina via Guix-patches via
2022-06-15 20:19         ` bug#55827: [PATCH] " Ludovic Courtès
2022-06-10 15:30 ` [bug#55827] " 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9a7cf69098315734ebdd3cb37de76a224abb7865.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=55827@debbugs.gnu.org \
    --cc=phodina@protonmail.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 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.