Yeah, relatively recent in its very visible form, but a relatively old problem
in its cause.
Fixed in upstream git for a while, but thanks to diverting branches
(abi-breakfree unstable and abi-breaking experimental) it hasn't reached a
(non-experimental) release yet:
http://anonscm.debian.org/cgit/apt/apt.git/commit/?id=2a884c612b10b27f4be2cc6dd689bfe448d9361a
It is written as an abi break, but could be rewritten to not require one
with some care (at least binary compatible, technically source
compatibility breaks and theoretically its still a behavior change). I
just decided against it at the time it was clear we would have to keep
the diversion a little longer than originally planed and backported just
the "absolutely needed" stuff. We could do it now, but I guess the time
is better spent in stopping to semi-maintain two branches. Hence setting
"fix commited" in anticipation of "fix released" soon [all while
realizing that I might very well be the biggest blocker in this process
with my perfectionism]
** Changed in: apt (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1464950
Title:
output flushing error causing ugly output for autoremove
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1464950/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
