On Fri, May 10, 2019 at 03:37:51PM +0200, Andreas Beckmann wrote: > The bug is now again in the bts-is-confused state: found+fixed in the > same version (which is treated as not-fixed and wont-be-archived). My > intention was to close it as invalid (found with version, fixed without > version) + unreproducible, since it is unclear which package actually > fixed it (such that a reassign+affects could be used).
I don't think "found with version, fixed without version" is a good idea. Anyway, I finally managed to close the bug. If you agree we can keep it that way and let it to be archived. Thanks.
