Re: Changelogs (Re: Bug#193497: marked as done (svtools: svsetup uses bashism "echo -e"))

2003-06-02 Thread John Hasler
mdz writes: > When I open a Debian changelog, I expect to see changes which are > pertinent to Debian development. This obviously includes changes which > affect the status of Debian bug reports. >From Debian-Policy 3.5.10.0: Debian Policy Manual - Source packages (from old Packaging Manual)

Re: Changelogs (Re: Bug#193497: marked as done (svtools: svsetup uses bashism "echo -e"))

2003-06-02 Thread Matt Zimmerman
On Mon, Jun 02, 2003 at 07:06:12PM -0500, John Hasler wrote: > mdz writes: > > When I open a Debian changelog, I expect to see changes which are > > pertinent to Debian development. This obviously includes changes which > > affect the status of Debian bug reports. > > >From Debian-Policy 3.5.10.

Re: Changelogs (Re: Bug#193497: marked as done (svtools: svsetup uses bashism "echo -e"))

2003-06-16 Thread Manoj Srivastava
On Mon, 16 Jun 2003 08:36:20 +1000, Herbert Xu <[EMAIL PROTECTED]> said: > Manoj Srivastava <[EMAIL PROTECTED]> wrote: >> >>> Even if the bug is for upstream fixing a typo in a comment? :) >> >> If it caused a Debian bug to be closed, that is a significant >> change in status for the Debian packa

Re: Changelogs (Re: Bug#193497: marked as done (svtools: svsetup uses bashism "echo -e"))

2003-06-16 Thread Colin Watson
On Sun, Jun 15, 2003 at 11:42:44PM -0500, Manoj Srivastava wrote: > On Mon, 16 Jun 2003 08:36:20 +1000, Herbert Xu <[EMAIL PROTECTED]> said: > > Manoj Srivastava <[EMAIL PROTECTED]> wrote: > >> If it caused a Debian bug to be closed, that is a significant > >> change in status for the Debian packa

Re: Changelogs (Re: Bug#193497: marked as done (svtools: svsetup uses bashism "echo -e"))

2003-06-16 Thread Herbert Xu
Colin Watson <[EMAIL PROTECTED]> wrote: > On Sun, Jun 15, 2003 at 11:42:44PM -0500, Manoj Srivastava wrote: > >> > What if the bug was reported after the new Debian package was >> > uploaded? Why does it suddenly stop being a significant change? This is meant to be a rhetorical question. > My a

Re: Changelogs (Re: Bug#193497: marked as done (svtools: svsetup uses bashism "echo -e"))

2003-06-16 Thread Matt Zimmerman
On Mon, Jun 16, 2003 at 07:51:07PM +1000, Herbert Xu wrote: > Which just proves that listing things in the changelog on the basis of bug > reports is meaningless. No, it only shows that it is not possible under some circumstances: specifically, when there was no bug report at the time. To say th

Re: Changelogs (Re: Bug#193497: marked as done (svtools: svsetup uses bashism "echo -e"))

2003-06-16 Thread Manoj Srivastava
On Mon, 16 Jun 2003 19:51:07 +1000, Herbert Xu <[EMAIL PROTECTED]> said: > Colin Watson <[EMAIL PROTECTED]> wrote: >> On Sun, Jun 15, 2003 at 11:42:44PM -0500, Manoj Srivastava wrote: >> >>> > What if the bug was reported after the new Debian package was >>> > uploaded? Why does it suddenly stop

Re: Changelogs (Re: Bug#193497: marked as done (svtools: svsetup uses bashism "echo -e"))

2003-06-16 Thread Manoj Srivastava
On Mon, 16 Jun 2003 09:36:24 +0100, Colin Watson <[EMAIL PROTECTED]> said: > On Sun, Jun 15, 2003 at 11:42:44PM -0500, Manoj Srivastava wrote: >> On Mon, 16 Jun 2003 08:36:20 +1000, Herbert Xu >> <[EMAIL PROTECTED]> said: >> > Manoj Srivastava <[EMAIL PROTECTED]> wrote: >> >> If it caused a Debia

Re: Changelogs (Re: Bug#193497: marked as done (svtools: svsetup uses bashism "echo -e"))

2003-06-16 Thread Colin Watson
On Mon, Jun 16, 2003 at 04:04:55PM -0500, Manoj Srivastava wrote: > On Mon, 16 Jun 2003 09:36:24 +0100, Colin Watson <[EMAIL PROTECTED]> said: > > On Sun, Jun 15, 2003 at 11:42:44PM -0500, Manoj Srivastava wrote: > >> Good point. Shall we mandate that all bug closures be adequately > >> documented

Re: Changelogs (Re: Bug#193497: marked as done (svtools: svsetup uses bashism "echo -e"))

2003-06-16 Thread Joey Hess
Manoj Srivastava wrote: > >> Good point. Shall we mandate that all bug closures be adequately > >> documented in the ChangeLog? I would be quite happy with that. > I do think bug closures be documented in the ChangeLog (I > shall attempt to do so from now on for every real bug that is close