Hi Axel,
On Thu, Apr 07, 2016 at 12:01:42AM +0200, Axel Beckert wrote:
On Mon, Apr 04, 2016 at 03:50:04PM +0200, Joel Brunenberg wrote:
I just now submitted a debian bug for this because I hope that it gets
fixed in Debian stable,
[...]
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819976
Bugs of severity "normal" usually don't get fixed/backported to
stable. The risk that the fix breaks something else and makes the
situation even worse in stable is too high.
I understand. I do not like hearing that very much but it makes sense.
Even though this is a tiny incision, I do not feel comfortable
projecting all possible effects on the strangest of scenarios this
software is run in.
But that being said, the tiny size of this change makes me confident to
maintain this change locally for the time being. Effects of this change
being removed or overwritten by an update are implicitly monitored
really really well. :)
But we will very likely fix this in Unstable/Testing and hence for the
next Debian Stable release dubbed "Stretch" (Debian 9).
That is very good news. Another question would be if this is fixed in
the package or in the prrovided script in upstream. Even though that
does not really matter from an end user perspective, I would be
interested to know how that works.
Thanks for the effort,
Joel
--
Joel Brunenberg - Troisdorf
PGP: 0xAD25981C