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 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. Of course this is all still in beta and I imagine it might still have some bugs that keep it from behaving as expected. -- see shy jo
signature.asc
Description: Digital signature
