On Mon, Aug 29, 2005 at 08:16:36PM +0200, Florian Weimer wrote: > Would it be possible to include such information in the bug-specific > page as well, or at least a link to obtain it?
Well, anything's possible. The versioning checks are somewhat slow and
cumbersome at the moment; so they're only done when /specifically/
requested, which is only possible for pkgreport listings atm. I guess
what you mean is you'd like something like:
* Bug applies to testing only!
somewhere obvious in the bugreport page.
> | Outstanding bugs -- Grave; Unclassified (1 bug)
> | * #324167: OpenVPN 2.0-1 vulnerabilities
> | Package: openvpn (openvpn 2.0-1; fixed: openvpn 2.0.2-1);
> | Severity: grave; Reported by: Daniel Lehmann <[EMAIL PROTECTED]>;
> | Tags: fixed-upstream, security
> | Done: Alberto Gonzalez Iniesta <[EMAIL PROTECTED]>;
> | Will be archived in 28 days.
> Does this mean that the bug will be archived even though it's not
> fixed in sarge?
Hrm. Yes it does, and yes you should manually tag it +sarge if you
don't want that behaviour.
Technically, that can be changed -- expiry isn't actually reimplemented
yet; and I guess it wouldn't be impossible to say "don't expire bugs
that are open in stable and have either <sarge> or <security> tags".
I'd kind-of hope it wouldn't be an issue in practice -- security bugs
that're fixed in unstable ought to have the fix for stable uplaoded
within 28 days anyway, shouldn't they?
Cheers,
aj
signature.asc
Description: Digital signature
