Lintian warnings converting copyright to machine-readable

Hello!, I'm packaging gigalomania and want to convert copyright to machine-readable format but I'm having lintian warnings I don't know how to fix. The original copyright is here: http://gigalomania.sourceforge.net/#licences There are a lot of images with different authors embedded into single

Re: compiled binary file in source package

David Rabel writes: > On 09.02.2018 00:44, Ben Finney wrote: > > Is the compiled binary file generated entirely from sources that are > > all in the upstream source distribution? > > Yes, it's genereated from the sources. Allthough I cannot technically > verify that.

Re: compiled binary file in source package

On 09.02.2018 00:44, Ben Finney wrote: > David Rabel writes: > >> I am maintaining jugglinglab. The upstream source package contains a >> compiled binary file. What is the cleanest solution to get rid of it? > > Is the compiled binary file generated entirely from

Bug#887126: marked as done (RFS: ddupdate/0.5.3-1 [ITP] #886546)

Your message dated Fri, 09 Feb 2018 16:20:11 + with message-id and subject line closing RFS: ddupdate/0.5.3-1 [ITP] #886546 has caused the Debian Bug report #887126, regarding RFS: ddupdate/0.5.3-1 [ITP] #886546 to be marked as done. This means that you

Bug#889968: RFS: inotify-tools/3.14-4

Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "inotify-tools" * Package name : inotify-tools Version : 3.14-4 Upstream Author : Radu Voicilas * Url :

Re: compiled binary file in source package

Miroslav Kravec writes: > On Fri, Feb 9, 2018 at 9:38 AM, Paul Wise wrote: > > https://wiki.debian.org/EmbeddedCodeCopies > > And, is there any official recommendation to get software (development > tools) rather packaged, and used as build

Re: compiled binary file in source package

On Fri, Feb 9, 2018 at 9:38 AM, Paul Wise wrote: >> I got interested in this, as I want to use a tool, which isn't >> packaged in debian. And upstream considers it to be a good idea to >> include tool's sources into project, where it's used. I like more >> clean solution - get

Re: compiled binary file in source package

On Fri, Feb 9, 2018 at 4:14 PM, Miroslav Kravec wrote: > Could you please provide the name of the policy? I've just read it, > and I haven't found one. Debian Free Software Guidelines item 2: https://www.debian.org/social_contract#guidelines 2. Source Code The program must include source

Re: compiled binary file in source package

On Fri, Feb 9, 2018 at 5:14 AM, Ben Finney wrote: > A source package that contains a file that requires source not in Debian > is one of the reasons given by FTP masters for rejecting a source > package , as a > “serious