On Fri, Jul 29, 2016 at 03:32:50PM +0200, Andreas Beckmann wrote: > Control: reassign -1 staden 2.0.0+b10-5 > Control: fixed -1 2.0.0+b11-1 > Control: affects -1 + spin > > On 2016-07-27 05:53, tony mancill wrote: > > package spin > > close 826684 6.4.5+dfsg-1 > > thanks > > > > Trying once again with the version of spin found in the archive. > > This bug was closed by the upload of staden/2.0.0+b11-1. > > Nope, marking bugs as found and fixed in the same version confuses the > BTS (and the bug is considered to be *not fixed*). > Reassigning to staden, since there is no action needed on the spin side. Hi Andreas,
Thank you for looking into this and taking the time to respond. I'm still a little confused, because that control message you reference above did in fact appear to do trick. I infer this because spin transitioned from unstable to testing the next morning [1]. Perhaps someone took some other direct action that's not visible? Reconstructing a bit of history... This bug had already been closed in in a new sourceful upload of staden with version 2.0.0+b11-2 - thank you to Andreas Tille! - so I'm not sure what your reassignment accomplishes because the bug was already closed for that source package. I think what might have caused things to get stuck is that the bug was originally opened against spin 6.4.5-1, but the upload of 6.4.5+dfsg-1 occurred in the meantime, replacing the version in unstable, so when staden was updated, the version of spin against which the bug was opened didn't exist in the archive. In any event, both spin and staden have migrated to testing an appear to be in the desired state [2,3]. Cheers, tony [1] https://tracker.debian.org/news/787138 [2] https://tracker.debian.org/pkg/spin [3] https://tracker.debian.org/pkg/staden
signature.asc
Description: Digital signature
