Bug#844059: debbugs: control server should reject fixed versions that do not exist and result in a no-op

Don Armstrong <[email protected]> Sat, 12 Nov 2016 16:01:49 -0800
Newsgroups gmane.linux.debian.devel.debbugs
Message-ID <20161113000149.b7mlomgyuyxj334w__37699.861257761$1478995601$gmane$org@qor.donarmstrong.com>
Control: tag -1 wontfix

On Sat, 12 Nov 2016, Johannes Schauer wrote:
> I naively expected, that the version passed to the "fixed" command is
> compared with a greater than or equal comparison. Thus, I indicated
> that a bug was fixed in upstream version X while the corresponding
> upload to Debian included the Debian revision and was thus version
> X-1. It seems that using version X had no effect as far as the bts was
> concerned and that only after I specified the actually uploaded
> version X-1 did the bts mark all later versions as fixed. I propose to
> either:
> 
>  - let the control server reject the versions that will result in a
>    no-op

It currently warns if you give it a version which it doesn't know about.
Since it's possible to close bugs before they're actually in the
archive, the BTS can't disallow versions which it doesn't know about.

>  - do a version comparison, marking all versions greater than or equal
>    to X as fixed

That won't work, because it's perfectly valid to have a bug which is
found in a version which is greater than the fixed version, but isn't on
the same path as the fixed version.

For example, if a bug is fixed by a security update in stable, that
doesn't mean it is fixed in unstable.