Paul Gevers <elb...@debian.org> writes: > This bug will trigger auto-removal when appropriate. As with all new > bugs, there will be at least 30 days before the package is auto-removed.
That sounds appropriate in this case. Unstable is how we found out about the upstream bug (https://debbugs.gnu.org/71891), which I'd imagined might be fixed by now, but it's not. While I'd still imagine it may be fixed "soon", we can't count on that. > Normally I would closed this bug with the version in unstable, so if > that version or a later version migrates, this bug will no longer affect > testing. However because this is also reporting the FTBFS, I decided to > not do that. I have tagged this bug to only affect sid and trixie, so it > doesn't affect (old-)stable. If possible, I think the best outcome, when it's time, would just be for unstable to revert to the version in trixie. Also fine (from my perspective) for that to happen sooner if it helps. Thanks for the help -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
