Your message dated Sun, 12 Jun 2016 02:54:52 +0900
with message-id <[email protected]>
and subject line Re: Bug#541819: GPL-licensed programs link to OpenSSL
has caused the Debian Bug report #541819,
regarding [general] GPL-licensed programs link to OpenSSL
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
541819: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541819
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: devscripts
Version: 2.10.53
Severity: serious
Justification: Policy 2.2.1
According to debian/copyright, uscan and dget are GPLv2+-licensed. They
are, however, linking (indirectly, via libcrypt-ssleay-perl to OpenSSL
which is incompatible with GPL.
--
Jakub Wilk
--- End Message ---
--- Begin Message ---
Hi,
On Sun, May 15, 2016 at 07:56:33PM +0200, Christoph Berg wrote:
> Re: Osamu Aoki 2016-05-05 <[email protected]>
> > As for https://bugs.debian.org/541819 , can we check if it is still
> > problem. In short, Jakub raises issue for uscan and bts.
> >
> > As for uscan, I see the changelog:
> > | devscripts (2.13.5) unstable; urgency=low
> > |
> > | [ James McCoy ]
> > | ...
> > | * uscan:
> > | ...
> > | + Require LWP::Protocol::https instead of Crypt::SSLeay to access
> > https
> > | sites. (Closes: #624317)
> > | ...
> > | -- James McCoy <[email protected]> Wed, 04 Dec 2013 22:27:45 -0500
> > LWP is provided by libwww-perl which is Artistic or GPL-1+.
> >
> >
> > As for bts, it uses Net::SMTP::SSL since 2008-06 and it is provided by
> > the libnet-smtp-ssl-perl package which is Artistic or GPL-1+.
> >
> > So as far as the direct dependency, both are OK even from Jakub's POV.
> >
> > Can anyone tip in to evaluate this situation?
>
> I'd think if this issue wasn't important enough to get fixed in the
> past 7 years, we can just close it now.
>
> > PS: I am more or less with Christoph's point that the license
> > incompatibility for SSLeay is not an issue for perl programs at all.
>
> I've never heard anything to the contrary, but IANAL.
Let's close this.
If anyone disagree, please feel free to reopen this bug citing evidence
to support your position stated previously by the reliable third party
such as the FTP master.
Osamu
--- End Message ---
_______________________________________________
devscripts-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/devscripts-devel
