Re: Modifying upstream source

2006-10-21 Thread Martin Kelly
I just changed the install command in the rules file and it works nicely now... thanks :). Martin Kelly Nelson A. de Oliveira wrote: Hi Martin! On 10/21/06, Martin Kelly <[EMAIL PROTECTED]> wrote: I have a package called pyecm where the upstream distributes a pyecm.py file but in Debian I'd

Re: Modifying upstream source

2006-10-21 Thread shaulka
On Sunday, October 22, 2006 3:34 am, Martin Kelly wrote: > I have a question about modifying the upstream source of a package > for debianization. > options mentioned deleted. > Which of these should I do in order to comply with standards and > good practice? > There are also the dpatc

Re: Modifying upstream source

2006-10-21 Thread Nelson A. de Oliveira
Hi Martin! On 10/21/06, Martin Kelly <[EMAIL PROTECTED]> wrote: I have a package called pyecm where the upstream distributes a pyecm.py file but in Debian I'd like it to be called pyecm as that's a much better command name (it's being used as a shell script and not a module). If pyecm will be

Modifying upstream source

2006-10-21 Thread Martin Kelly
I have a question about modifying the upstream source of a package for debianization. I have a package called pyecm where the upstream distributes a pyecm.py file but in Debian I'd like it to be called pyecm as that's a much better command name (it's being used as a shell script and not a modu

Re: Lintian Warnings and Modifying Upstream Source

2006-01-30 Thread Justin Pryzby
On Thu, Jan 26, 2006 at 07:46:58AM +0100, Michelle Konzack wrote: > Am 2006-01-21 13:44:28, schrieb Russ Allbery: > > > The error message isn't about its presence in the source package but > > rather its presence in the generated binary package. In general, in > > Debian, you should never install

Re: Lintian Warnings and Modifying Upstream Source

2006-01-30 Thread Michelle Konzack
Am 2006-01-21 13:44:28, schrieb Russ Allbery: > The error message isn't about its presence in the source package but > rather its presence in the generated binary package. In general, in > Debian, you should never install additional copies of the GPL, the LGPL, > or other common licenses; instead

Re: Lintian Warnings and Modifying Upstream Source

2006-01-21 Thread Paul Wise
On Sat, 2006-01-21 at 13:15 -0800, Cameron Dale wrote: > W: torrentflux: extra-license-file var/www/torrentflux/adodb/license.txt Other people have pointed out the solution to this, however, it indicates to me that torrentflux includes a copy of adodb. Please don't install that copy, unless the t

Re: Lintian Warnings and Modifying Upstream Source

2006-01-21 Thread Cameron Dale
On 1/21/06, Russ Allbery <[EMAIL PROTECTED]> wrote: > The first four you're probably going to have to just live with unless > upstream repackages their source better. (The first two aren't even > really problems in my opinion; the I: level of lintian output is just > informational and isn't someth

Re: Lintian Warnings and Modifying Upstream Source

2006-01-21 Thread Cameron Dale
On 1/21/06, Stan Vasilyev <[EMAIL PROTECTED]> wrote: > Just remove var/www/torrentflux/adodb/license.txt after the installation. You > definitely want to keep this file in the source package. You can then add a > reference to LGPL in debian/copyright like this: > > On Debian systems, the complete t

Re: Lintian Warnings and Modifying Upstream Source

2006-01-21 Thread Russ Allbery
Cameron Dale <[EMAIL PROTECTED]> writes: > I'm trying to create a new package for Debian, and I have some Lintian > warnings that I'm not sure how to deal with. I know I could fix all of > them by removing some files from the upstream source, but I'm not sure > if this is justified. I read the "Be

Re: Lintian Warnings and Modifying Upstream Source

2006-01-21 Thread Daniel Leidert
Am Samstag, den 21.01.2006, 13:15 -0800 schrieb Cameron Dale: > I'm trying to create a new package for Debian, and I have some Lintian > warnings that I'm not sure how to deal with. [..] > > W: torrentflux: extra-license-file var/www/torrentflux/adodb/license.txt > > The first 4 are easily fixed

Re: Lintian Warnings and Modifying Upstream Source

2006-01-21 Thread Stan Vasilyev
On Saturday 21 January 2006 01:15 pm, Cameron Dale wrote: > > The first 4 are easily fixed by removing the files. The last one is a > little more problematic, but I asked on debian-legal, and as the > license file is for the LGPL, then the package can redistribute it > under the GPL, and I think th

Lintian Warnings and Modifying Upstream Source

2006-01-21 Thread Cameron Dale
I'm trying to create a new package for Debian, and I have some Lintian warnings that I'm not sure how to deal with. I know I could fix all of them by removing some files from the upstream source, but I'm not sure if this is justified. I read the "Best Packaging Practices" section of the Developer's