-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sat, 26 Jul 2008 04:56:05 +0100
Source: debian-bts-applet
Binary: debian-bts-applet
Architecture: source all
Version: 0.3
Distribution: unstable
Urgency: low
Maintainer: Chris Lamb [EMAIL PROTECTED]
Changed-By: Chris Lamb [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 18 Mar 2008 03:13:11 +
Source: debian-bts-applet
Binary: debian-bts-applet
Architecture: source all
Version: 0.2
Distribution: unstable
Urgency: low
Maintainer: Chris Lamb [EMAIL PROTECTED]
Changed-By: Chris Lamb [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 24 Jan 2008 19:21:13 +
Source: debian-bts-applet
Binary: debian-bts-applet
Architecture: source all
Version: 0.1
Distribution: unstable
Urgency: low
Maintainer: Chris Lamb [EMAIL PROTECTED]
Changed-By: Chris Lamb [EMAIL
Hi, I am a student from the University Putra Malaysia. Now i am doing a
study about Debian in my final year project. i am interested about Debian's
bugs tracking system.
http://www.debian.org/doc/developers-reference/ch-resources
after i have go through above page, i think is better i ask if
On 07/01/2008, PoayHua wrote:
after i have go through above page, i think is better i ask if there
have any statistical analysis or anything related to Debian's bugs?
if there has any of it, it maybe a big help for my project.
Christian Perrier posted some figures [1,2] on [3] yesterday. Some
As a maintainer and a user, I have often wondered lately if the practice of
tracking numerous upstream bugs in the Debian BTS is something that should
be ended.
Please don't.
I always ask my downstream DDs to forward bugs to me together with the
Debian bug number, and to leave the bug open
This morning I reported two bugs (using reportbug), which have not been
acknowledged by BTS. Now I've just received an update on a bug which was
CC:'ed to my personal email. I've answered, but http//bugs.debian.org
has not been updated and the update wasn't ack'ed either.
Is there a maintenance
On Sat, 29 Apr 2006, Yves-Alexis Perez wrote:
This morning I reported two bugs (using reportbug), which have not been
acknowledged by BTS. Now I've just received an update on a bug which was
CC:'ed to my personal email. I've answered, but http//bugs.debian.org
has not been updated and the
On Mon, Oct 24, 2005 at 11:50:11PM +0900, Osamu Aoki wrote:
On Sat, Oct 22, 2005 at 05:14:20PM -0700, Steve Langasek wrote:
On Sun, Oct 23, 2005 at 09:41:15AM +1000, Brian May wrote:
Brian == Brian May [EMAIL PROTECTED] writes:
Along similar lines, if a have a closes: #nnn in my
On Sat, Oct 22, 2005 at 05:14:20PM -0700, Steve Langasek wrote:
On Sun, Oct 23, 2005 at 09:41:15AM +1000, Brian May wrote:
Brian == Brian May [EMAIL PROTECTED] writes:
Along similar lines, if a have a closes: #nnn in my changelog for
package X, but the bug is for package Y, is this going
Brian == Brian May [EMAIL PROTECTED] writes:
Brian What is the preferred way of closing bugs that are not bugs
Brian (e.g. mistake by the submitter)? -- Brian May
Brian [EMAIL PROTECTED]
Has the reassign command changed? What versions apply if you
reassign a bug to another package
On Sun, Oct 23, 2005 at 09:41:15AM +1000, Brian May wrote:
Brian == Brian May [EMAIL PROTECTED] writes:
Brian What is the preferred way of closing bugs that are not bugs
Brian (e.g. mistake by the submitter)? -- Brian May
Brian [EMAIL PROTECTED]
Has the reassign command
On Fri, Oct 21, 2005 at 02:08:17AM +0200, Pierre THIERRY wrote:
It seems. I did it for #297927: after sending a 'close 297927' to
[EMAIL PROTECTED], the BTS informed me that it was deprecated. I sent
another mail to [EMAIL PROTECTED] with 'Version: 0.9.23-1', and it is
now in the BTS as
Scribit Stefano Zacchiroli dies 19/10/2005 hora 11:06:
1) once a bug as been closed - erroneously I would say - mailing
[EMAIL PROTECTED] without the Version: pseudo header, is
there a way to push the version information to the bts?
It seems. I did it for #297927: after sending a 'close
Joey == Joey Hess [EMAIL PROTECTED] writes:
Joey 2. If you forget a changelog entry, or find out about a
Joey fix (such as a fix for a security hole) after your upload,
Joey send mail to [EMAIL PROTECTED] as before, but
Joey include a Version: pseudo-header[2].
What is the
On Wed, Oct 19, 2005 at 05:56:47PM +1000, Brian May wrote:
Joey == Joey Hess [EMAIL PROTECTED] writes:
Joey 2. If you forget a changelog entry, or find out about a
Joey fix (such as a fix for a security hole) after your upload,
Joey send mail to [EMAIL PROTECTED] as before, but
On Wed, Oct 19, 2005 at 01:44:38AM -0700, Steve Langasek wrote:
Closing without a version header retains the traditional semantics of
marking the bug closed in all versions.
Two questions:
1) once a bug as been closed - erroneously I would say - mailing
[EMAIL PROTECTED] without the Version:
On Wed, Oct 19, 2005 at 11:06:14 +0200, Stefano Zacchiroli wrote:
On Wed, Oct 19, 2005 at 01:44:38AM -0700, Steve Langasek wrote:
Closing without a version header retains the traditional semantics of
marking the bug closed in all versions.
Two questions:
1) once a bug as been closed -
Hi Joey
Joey Hess wrote:
In the process of my work on the testing security team, I've noticed
that many developers still seem to be unfamiliar with how to use the new
version tracking features[1] of the Debian BTS.
...
I thought I'd conclude with an example of how to do it right, and wrong
I rarely announce software, but this could be useful to DDs.
Whenever I wanted to add tags or something to a bug report, I'd start my
browser to http://www.debian.org/ - Bug Reports - Developers'
information on manipulating bugs by email. Just to get the syntac
right.
So I wrote debian-bts
On Tue, Sep 14, 1999 at 12:03:42PM -0700, Darren Benham wrote:
Well, we did it.
The software used by Debian for it's bug tracking, debbugs, was pacakged for
distribution several months ago and resides in Potato. Last weekend, Debian
upgraded it's bug server (bugs.debian.org) to the save
21 matches
Mail list logo
