Re: upstream field in package description

2005-06-04 Thread Christian Schoenebeck
Es geschah am Mittwoch 01 Juni 2005 21:58 als Chris Waters schrieb: > On Wed, Jun 01, 2005 at 04:08:54PM +0200, Christian Schoenebeck wrote: > > Because if it would get part of the policy to be mandatory , then > > developers would get stressed or at least noticed/pointed to by

Re: upstream field in package description

2005-06-01 Thread Christian Schoenebeck
Es geschah am Mittwoch 01 Juni 2005 15:12 als Bill Allombert schrieb: > On Wed, Jun 01, 2005 at 01:31:27AM +0200, Christian Schoenebeck wrote: > > Es geschah am Mittwoch 01 Juni 2005 01:33 als Bill Allombert schrieb: > > > 1) Debian Policy mandate the information in the copy

Re: upstream field in package description

2005-05-31 Thread Christian Schoenebeck
Es geschah am Mittwoch 01 Juni 2005 01:33 als Bill Allombert schrieb: > 1) Debian Policy mandate the information in the copyright file already: > > 12.5. Copyright information > --- > ... > > In addition, the copyright file must say where the upstream sources > (if

Re: upstream field in package description

2005-05-31 Thread Christian Schoenebeck
Es geschah am Freitag 13 Mai 2005 22:15 als Adeodato Simó schrieb: > * Christian Schoenebeck [Fri, 13 May 2005 21:41:46 +0200]: > > IMO at least the upstream source field should become mandatory for Debian > > packages in future. On some packages it's really not that easy t

Re: upstream field in package description

2005-05-13 Thread Christian Schoenebeck
Es geschah am Freitag 13 Mai 2005 22:15 als Adeodato Simó schrieb: > That if a package does not contain those two bits of information in > the copyright file (author and where to get the source), you should > file a serious bug against the package, since the Debian Policy §12.5 > mandates t

upstream field in package description

2005-05-13 Thread Christian Schoenebeck
opyright or README.Debian file. What do you think? Best regards Christian Schoenebeck -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]