On Mon, Jul 18, 2005 at 08:35:45AM -0600, Rob Sims wrote:
> On Mon, Jul 18, 2005 at 12:06:29PM +0100, Colin Watson wrote:
> > A number of changes have been made to [EMAIL PROTECTED] [1] to
> > support this. Firstly, the 'close' and 'reassign' commands now take
> > extra version arguments, as follows:
> >
> > close 1234567 1.1
> > reassign 1234567 example-package 2.0-1
>
> How is a bug that's fixed in more than one version handled? For
> example, a security bug fixed in foo 1.1-sarge1 and foo 1.3. Assume 1.1
> and 1.2 have the bug.
So, foo 1.1-sarge1's changelog will look like this:
foo (1.1-sarge1) stable; urgency=high
* fix security bug in sarge (closes: #NNNNNN)
-- Security Team <[EMAIL PROTECTED]> DATE
foo (1.1) unstable; urgency=low
* last upload before sarge
-- Maintainer <[EMAIL PROTECTED]> DATE
... while foo 1.3's changelog will look like this:
foo (1.3) unstable; urgency=high
* fix security bug (closes: #NNNNNN)
-- Maintainer <[EMAIL PROTECTED]> DATE
foo (1.2) unstable; urgency=low
* add a feature
-- Maintainer <[EMAIL PROTECTED]> DATE
foo (1.1) unstable; urgency=low
* last upload before sarge
-- Maintainer <[EMAIL PROTECTED]> DATE
The BTS records that bug #NNNNNN was fixed in 1.1-sarge1 and 1.3, and
let's say the bug was found in version 1.1. Since it has the changelogs
(it gets these from ftp-master), it can build up a tree of which package
versions are based on which other package versions, which in this case
looks like this:
1.1 ------> 1.1-sarge1
\
----> 1.2 ------> 1.3
Given that, it's easy to deduce that the bug affects both 1.1 and 1.2,
but doesn't affect 1.1-sarge1, 1.3, or any version based on those
(unless more information shows up, e.g. the bug recurs for some reason).
If you ask for bugs in an affected version, or in a distribution that
contains an affected version (let's say 1.2 is in testing and you ask
for http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=foo&dist=testing),
the bug shows up as open; if you ask for bugs in an unaffected version,
or in a distribution that contains an unaffected version, the bug shows
up as closed.
Obviously, this is a fairly simple case and it can get a lot more
complicated than that in practice ...
Cheers,
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
