[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: BTS version tracking

On Tue, Jul 19, 2005 at 10:34:23PM -0700, Brian Nelson wrote:
> Colin Watson <cjwatson@debian.org> writes:
> > The 'reopen' command takes an optional submitter argument, so it was
> > difficult to get a version in here unambiguously. Instead, we've
> > introduced a new 'found' command, which says "I've found the bug in this
> > version of the package". You can use this whether the bug is open or
> > closed; if the bug's closed and you give a version more recent than the
> > last recorded fixed version, the bug will be considered open again.
> >
> >   found 1234567 1.3-2
> Shouldn't that be, "you give a version more recent than *or equal to*
> the last recorded fixed version..."?

Mm, right, that's what I meant to say.

> What if the maintainer uploads a version, say 1.3-2 (which is still the
> most recent version), which supposedly fixes bug 1234567.  However, I
> test it and find that it's actually not fixed.  Presumably, I would do:
>   found 1234567 1.3-2
> However, since 1.3-2 is equal to the current version, the BTS would
> erroneously think that the bug is fixed.  That does seem to match
> reality:
>   http://bugs.debian.org/316089

Yes, this is a bug in version tracking: it's a canonicalisation problem
between various internal representations of versions in debbugs,
reported as bug #319037. Fortunately I don't think it's *too* hard to
solve ...

Colin Watson                                       [cjwatson@debian.org]

Reply to: