On Wed, Jun 21, 2006 at 09:36:59AM +, Alan Baghumian wrote:
> * Package name: xfardic
First, it would be nice if the subject could contain the package's
name. Perhaps the m.d.n boilerplate could include it.
The big four tests:
* lintian:
I'm afraid there are four issues, all in
On Wed, Jun 21, 2006 at 10:31:46PM +0200, Adam Borowski wrote:
> On Wed, Jun 21, 2006 at 09:36:59AM +, Alan Baghumian wrote:
> > * Package name : xfardic
>
> First, it would be nice if the subject could contain the package's
> name. Perhaps the m.d.n boilerplate could include it.
Good h
On Wed, 2006-06-21 at 22:31 +0200, Adam Borowski wrote:
> * On the first upload, debian/changelog should have just one entry.
> This is somewhat clumsy if you have a history of this package in
> your private/local repository (like me with debs of kbtin on
> SourceForge), but I remember someon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christoph Haas wrote:
> On Wed, Jun 21, 2006 at 10:31:46PM +0200, Adam Borowski wrote:
>> On Wed, Jun 21, 2006 at 09:36:59AM +, Alan Baghumian wrote:
>>> * Package name : xfardic
>> First, it would be nice if the subject could contain the pack
On Thu, 22 Jun 2006, Thijs Kinkhorst wrote:
> I'm not sure about a specific incident, but in general I'd say that
> for an otherwise unreleased package, more than one changelog entry
> is quite redundant. There's no reason to bother people with the
> different versions that never left your hard dri
On Thu, Jun 22, 2006 at 05:55:11PM +0200, Thijs Kinkhorst wrote:
> On Wed, 2006-06-21 at 22:31 +0200, Adam Borowski wrote:
> > * On the first upload, debian/changelog should have just one entry.
> > This is somewhat clumsy if you have a history of this package in
> > your private/local reposito
* Thu 2006-06-22 Thijs Kinkhorst
* Message-Id: 1150991711.6266.11.camel AT darwin.os9.nl
> On Wed, 2006-06-21 at 22:31 +0200, Adam Borowski wrote:
>
>> * On the first upload, debian/changelog should have just one entry.
>> This is somewhat clumsy if you have a history of this package in
>> you
On Fri, 2006-06-30 at 11:49 +0300, Jari Aalto+mail.linux wrote:
> The history in package indicates that there has been work going on
> before the package was added to Debian. The history documents the
> changes and gives indication of overall activity and competence the
> package was previously han
Often, changelog entries explain why certain technical packaging
decisions were made (for instance, Build-Depend on "foo >= $version"
because of $reason). These entries are definitely useful, even if they
happened before the first release uploaded to the Debian archive.
--
Florent
--
To UNSUBS
On Friday 30 June 2006 20:43, Florent Rougon wrote:
> Often, changelog entries explain why certain technical packaging
> decisions were made (for instance, Build-Depend on "foo >= $version"
> because of $reason). These entries are definitely useful, even if they
> happened before the first release
10 matches
Mail list logo
