Control: tags -1 + upstream Control: forwarded 506859 https://bugs.python.org/issue27451 Control: forwarded 507943 https://bugs.python.org/issue27450
On Mon, Jul 04, 2016 at 04:05:54PM +0200, Matthias Klose wrote: > Control: tags -1 + wontfix > > so you don't reply for about seven years, and then just re-open the issue > without any other action? Sorry, but please file this upstream. This is > nothing to fix in Debian, and I assume upstream will reject that as well at > least for 2.7. I had reopened these issues after carefully checking the current versions of both python2.7 and python3.5 to confirm that they still exist in those versions. (I should have included a comment to that effect in the bts invocation.) Several of the other bugs closed had long since been forwarded to upstream, fixed, and included in Debian; I checked those too, and didn't reopen them. I was already planning to file these upstream today and mark them forwarded, and I had appreciated the reminder that I'd lost track of these. I've now forwarded these upstream as https://bugs.python.org/issue27450 and https://bugs.python.org/issue27451 . I've tagged and forwarded the BTS bugs accordingly for reference, though I haven't reopened them to avoid playing ping-pong. (Personally, I prefer to track things consistently in the Debian BTS, rather than a thousand different upstream bug trackers, but that's your call as the maintainer.)
