On Sat, 2007-06-23 at 00:46 -0400, Michael Gilbert wrote: > Package: bugs.debian.org > Severity: normal > > some bugs end up being listed as "outstanding" even after the version of > the package with the fix enters unstable. it should be expected that > the bug would be listed as "resolved" once the fixed version is > uploaded.
*and * built on all architectures, at least. > i think the problem is with the "Version:" tag. i think that what > happens is that for example if the [EMAIL PROTECTED] message > contains "Version: 0.6.0", but the next version to enter unstable is > 0.6.1, the bug will not get relisted as "resolved" because > 0.6.0 != 0.6.1, "fixed version != uploaded version". the resolved > test should check for "uploaded version >= fixed version". It's not quite that simple. The BTS parses the package's changelog to determine a tree of package versions from which the new version is descended. Do you have a particular example of a bug which you think should be marked as resolved which is isn't? Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
