unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: 34717@debbugs.gnu.org
Subject: bug#34717: GPL and Openssl incompatibilities in u-boot and possibly others
Date: Sat, 09 Mar 2019 22:57:21 +0100	[thread overview]
Message-ID: <87h8cb4sou.fsf@gnu.org> (raw)
In-Reply-To: <87k1h9i3gl.fsf@ponder> (Vagrant Cascadian's message of "Fri, 08 Mar 2019 11:14:02 -0800")

Vagrant Cascadian <vagrant@debian.org> skribis:

> On 2019-03-08, Ludovic Courtès wrote:
>> Vagrant Cascadian <vagrant@debian.org> skribis:
>>> I'm not sure where it would be appropriate to add more comments
>>> regarding the GPL/Openssl incompatibilities; e.g. if someone were to
>>> propose adding one of the u-boot targets that requires it, they might
>>> just go ahead and re-add the openssl input...
>>
>> There’s always a risk.  I guess we’ll have to be careful when doing
>> reviews.
>
> Sure. I was thinking maybe putting a comment in the native-inputs where
> "openssl" was removed, but wasn't sure what the conventions might be.

Yeah that would have worked I guess.

>> In addition, we can add a ‘lint’ checker for this case, WDYT?
>
> Does the lint checker have a way to identify a confidence level,
> e.g. *maybe* it has this issue vs. *certainly*? Is there a way to
> override the lint checker issues for known false positives? Otherwise,
> it might just be annoying noise for packagers where it isn't
> appropriate.

No it doesn’t have that notion of a confidence level.

The warning could be triggered only when a package is GPL’d and has a
direct dependency on OpenSSL (we’d forget about indirect dependencies in
this case.)  The noise would be rather limited and justified in this
case, I think.  WDYT?

Thanks,
Ludo’.

  reply	other threads:[~2019-03-09 21:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-03  1:58 bug#34717: GPL and Openssl incompatibilities in u-boot and possibly others Vagrant Cascadian
2019-03-06 15:15 ` Ludovic Courtès
2019-03-06 18:12   ` Danny Milosavljevic
2019-03-08  9:59     ` Ludovic Courtès
2019-03-07  4:17   ` Vagrant Cascadian
2019-03-07 23:02     ` Vagrant Cascadian
2019-03-08 10:23       ` Ludovic Courtès
2019-03-08 19:14         ` Vagrant Cascadian
2019-03-09 21:57           ` Ludovic Courtès [this message]
2019-03-09 23:10             ` Vagrant Cascadian
2019-03-10  3:58               ` Jack Hill
2019-03-10 17:12               ` Ludovic Courtès
     [not found]         ` <87y26loa74.fsf@yucca>
     [not found]           ` <YXMgmR33gtyA8tgZ@jasmine.lan>
     [not found]             ` <87fsssoj6z.fsf@yucca>
2021-10-23  9:08               ` Maxime Devos
     [not found]           ` <87cznwoj2q.fsf@yucca>
     [not found]             ` <YXRmAoyt3X3DNTeX@jasmine.lan>
2021-10-24  8:50               ` Dr. Arne Babenhauserheide
2019-03-08 10:08     ` Ludovic Courtès
2019-03-08 10:16       ` Ludovic Courtès
2019-03-15 23:55     ` Adonay Felipe Nogueira

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=87h8cb4sou.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=34717@debbugs.gnu.org \
    --cc=vagrant@debian.org \
    /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).