On Sun, 2018-03-18 at 01:50 +, Chris Lamb wrote:
> I am unsure that a debian/ directory plus the upstream source really
> creates a derived work.
It definitely does when there are patches to the upstream code in
debian/, which is the case I'm talking about with this feature request.
> A
Processing commands for cont...@bugs.debian.org:
> tags 893326 + moreinfo
Bug #893326 [lintian] lintian: check that patch licenses are compatible with
licenses of files they modify
Added tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
893326:
tags 893326 + moreinfo
thanks
Hi Paul,
> It is often the case that the Debian packager just puts debian/ under
> the GNU GPL, which can often be incompatible with code licenses.
I am unsure that a debian/ directory plus the upstream source really
creates a derived work. (I am ignoring the cases
Package: lintian
Version: 2.5.79
Severity: wishlist
For packages with a machine-readable debian/copyright file and patches,
please check that the license for the debian/patches/* files are
compatible with the licenses for the files that they are modifying.
It is often the case that the Debian
This is an automated email from the git hooks/post-receive script.
pabs pushed a change to branch master
in repository lintian.
from 7f31cec Look under all of /usr/share/doc (not just
/usr/share/doc/$pkg) when looking for installed examples and update tag
description to match.
This is an automated email from the git hooks/post-receive script.
pabs pushed a commit to branch master
in repository lintian.
commit be4e01880f90a38eaa57bdaafc70b727f21b364a
Author: Paul Wise
Date: Sat Mar 17 18:08:19 2018 +0800
spelling: Add several corrections
---
6 matches
Mail list logo