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>, 55827@debbugs.gnu.org
Subject: [bug#55827] [PATCH] gnu: Add kismet.
Date: Tue, 07 Jun 2022 10:06:30 +0200	[thread overview]
Message-ID: <bb3651e4103aafb1a05d196ed7e203bd0a648108.camel@telenet.be> (raw)
In-Reply-To: <DYTQMUydfrTj6_0ZVa_f2x-7yRzWANjbC0EXV50UqwCLyAt-OCA9eMiZ69CfErY-wu2Mk_x76YGD-C0zG2j_bo5DLyhIuD9Jmk-1GzzgPzQ=@protonmail.com>

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

phodina via Guix-patches via schreef op di 07-06-2022 om 07:41 [+0000]:
> +	(inputs (list openssl libpcap libusb protobuf protobuf-c
> libwebsockets sqlite zlib))
[...]
> +    (license license:gpl2+)))

libwebsockets is lgpl2.1 according to the package definition.
Its dependency openssl is asl2.0.  According to the FSF, asl2.0 and
gpl2.0 are incompatible.  So possibly asl2.0 and lgpl2.1 are
incompatible (though I haven't seen any reliable claim for
compatibility or incompatibility for _l_gpl, maybe it is compatible)
and hence libwebsockets needs to be removed from kismet and Guix.

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

Greetings,
Maxime.

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

  parent reply	other threads:[~2022-06-07  8:07 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 [this message]
2022-06-07  9:57   ` [bug#55827] [PATCH v2] " phodina via Guix-patches via
2022-06-07 11:04     ` Maxime Devos
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=bb3651e4103aafb1a05d196ed7e203bd0a648108.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.