On Thu, Sep 08, 2005 at 12:14:03PM -0400, Joey Hess wrote:
> Adrian Bunk wrote:
> > you closed this bug with
> > close -1 1.5
> >
> > Could you or someone who knows the semantics of version tracking please
> > explain how to implement the following:
> > - this bug is fixed in unstable/testing
> > - it is most likely present in stable (Ubuntu has already issued a
> > security advisory)
> > - I haven't checked whether oldstable might be affected
> > - this bug mustn't be archived until it is fixed in stable (and perhaps
> > oldstable)
> >
> > Without version tracking I'd have simply done:
> > reopen 326898
> > tags 326898 woody sarge
> >
> > Is there an equivalent syntax for doing the same with version tracking
> > including preventing the bug becoming archived, or was your closing of
> > the bug wrong and it should be reopened?
>
> tag 326898 woody sarge
>
> As explained in the docs, the release tags now keep a bug from being
> archived. The version tracking keeps the bug open for queries for bugs
I did what you suggested, and it doesn't seem to work:
Resolved bugs -- Grave (1 bug)
* #326898: gnumeric: Gnumeric embeds copy of vulnerable PCRE code
Package: gnumeric (fixed: gnumeric 1.5); Severity: grave; Reported
by: Moritz Muehlenhoff <[EMAIL PROTECTED]>; Tags: sarge, security,
woody
Done: Joey Hess <[EMAIL PROTECTED]>; Will be archived in 28 days.
> in woody and sarge, and you'll save me a lot of time chasing whether
> security bugs are fixed or not if you just use Closes: in the changelog
> and let the version tracking do its thing.
>...
IOW the version tracking isn't so dumb that that it would close bugs
when uploads to stable, oldstable or t-p-u contain Closes: lines in the
changelog, but handles them correctly by removing release tags?
> see shy jo
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
