[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#642255: marked as done (lintian does not handle AGPL license)

Your message dated Thu, 17 Nov 2011 13:17:18 +0100
with message-id <4EC4FB4E.7050009@thykier.net>
and subject line Re: Bug#642255: lintian does not handle AGPL license
has caused the Debian Bug report #642255,
regarding lintian does not handle AGPL license
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 owner@bugs.debian.org
immediately.)


-- 
642255: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642255
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: lintian
Version: 2.5.3
Severity: normal

I am working on packaging configshell which is licensed under the AGPL-3
license.

This license does not seem to be covered by lintian. I get the following
error when running lintian.

E: python-configshell: copyright-should-refer-to-common-license-file-for-gpl

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages lintian depends on:
ii  binutils                       2.21.53.20110910-1
ii  bzip2                          1.0.5-7           
ii  diffstat                       1.54-1            
ii  file                           5.08-1            
ii  gettext                        0.18.1.1-4        
ii  intltool-debian                0.35.0+20060710.1 
ii  libapt-pkg-perl                0.1.24+b2         
ii  libclass-accessor-perl         0.34-1            
ii  libdpkg-perl                   1.16.0.3          
ii  libemail-valid-perl            0.185-1           
ii  libipc-run-perl                0.90-1            
ii  libparse-debianchangelog-perl  1.2.0-1           
ii  libtimedate-perl               1.2000-1          
ii  liburi-perl                    1.59-1            
ii  locales                        2.13-21           
ii  man-db                         2.6.0.2-2         
ii  patchutils                     0.3.2-1           
ii  perl [libdigest-sha-perl]      5.12.4-4          
ii  unzip                          6.0-5             

lintian recommends no packages.

Versions of packages lintian suggests:
ii  binutils-multiarch     <none>               
ii  dpkg-dev               1.16.0.3             
ii  libhtml-parser-perl    3.68-1+b1            
ii  libtext-template-perl  1.45-2               
ii  man-db                 2.6.0.2-2            
ii  xz-utils               5.1.1alpha+20110809-2

-- no debconf information

--- End Message ---
--- Begin Message --- 
On 2011-09-21 20:52, Jakub Wilk wrote:
> * Ritesh Raj Sarraf <rrs@debian.org>, 2011-09-21, 03:33:
>>> Thanks for the bug report. I'd tad easier for us to reproduce the
>>> problem if you attached the actual copyright file. (lintian already
>>> tries to detect AGPL-3, but maybe it doesn't try hard enough...)
>> I've attached the copyright file I'm using. The file does not carry the
>> full AGPL-3 license, just part of it. I'll have to change that because
>> base-files package currently does not carry AGPL-3 license.
> 
> I believe that the false positive
> copyright-should-refer-to-common-license-file-for-gpl will go away once
> you quote full AGPL in your copyright file.
> 

Hey,

I just added a test containing the entire AGPL-3 and it does not (on its
own) trigger any tags.  So I am taking the liberty of closing this as
"not a bug".  If you can reproduce the issue with the full AGPL-3 in the
copyright, please attach the related copyright file.

~Niels

--- End Message ---
Reply to: