Re: Licence issue with sarg
On Mon, May 23, 2005 at 09:33:33AM +0200, Luigi Gangitano wrote: Il giorno lun, 23/05/2005 alle 01.57 +0200, Frank Lichtenheld ha scritto: On Mon, May 23, 2005 at 01:42:30AM +0200, Luigi Gangitano wrote: I need to upload a new orig.tar.gz and don't know how to do that for sarge. You will need to upload a fixed package to testing-proposed-updates since the version in unstable differs from the one in testing. Which part do you don't know how to do? How to upload 2.0.5 with a changed .orig.tar.gz or uploading to t-p-u? Just which was the right queue. Shall I retain the same version (2.0.5) with an epoch or upload the new upstream version? If the problem is that you have to remove material from the orig.tar.gz, then an epoch won't help you. Filenames in the package pool must be unique, and epochs are not part of the filename. So, please remove only the unlicensed material from 2.0.5, change the upstream version number (e.g., 2.0.5.dfsg), and upload to t-p-u. Thanks, -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: Licence issue with sarg
Il giorno sab, 21/05/2005 alle 21.12 -0700, Steve Langasek ha scritto: On Sun, May 22, 2005 at 12:15:20AM +0200, Luigi Gangitano wrote: Hi all, I need help solving a licence issue with sarg. Tonight I found that sarg upstream sources contain a font file that may not be free (Verdana.TTF). I've contacted upstream a few minutes ago. In the meanwhile I'm preparing a package that doesn't contain that file. A new orig.tgz is needed. How should I upload it? According to the guidelines in the freeze announcement. Sorry, you didn't tell us what package this is, so I can't be more specific without merely repeating myself. Sorry, I didn't make it clear that the package was 'sarg', which has version 2.0.5-2 in sarge and version 2.0.7-1 in sid. Both versions contain the file that is not freely licensed (modification is not allowed). Upcoming upstream version 2.0.8 will remove the file. I need to upload a new orig.tar.gz and don't know how to do that for sarge. Thanks, -- Luigi Gangitano -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] GPG: 1024D/924C0C26: 12F8 9C03 89D3 DB4A 9972 C24A F19B A618 924C 0C26 signature.asc Description: This is a digitally signed message part
Re: Licence issue with sarg
On Mon, May 23, 2005 at 01:42:30AM +0200, Luigi Gangitano wrote: I need to upload a new orig.tar.gz and don't know how to do that for sarge. You will need to upload a fixed package to testing-proposed-updates since the version in unstable differs from the one in testing. Which part do you don't know how to do? How to upload 2.0.5 with a changed .orig.tar.gz or uploading to t-p-u? Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Licence issue with sarg
Steve Langasek wrote: On Sun, May 22, 2005 at 12:15:20AM +0200, Luigi Gangitano wrote: Hi all, I need help solving a licence issue with sarg. Tonight I found that sarg upstream sources contain a font file that may not be free (Verdana.TTF). I've contacted upstream a few minutes ago. In the meanwhile I'm preparing a package that doesn't contain that file. A new orig.tgz is needed. How should I upload it? According to the guidelines in the freeze announcement. Sorry, you didn't tell us what package this is, so I can't be more specific without merely repeating myself. The package is called 'sarg'... My first reaction was that he had misspelled sarge as well. :) Travis signature.asc Description: OpenPGP digital signature
