On Tue, 31 Jul 2018 at 15:24:33 +0200, Laurent GUERBY wrote:
> I get this bug on my debian stretch, any reason not not backport
> and release gdm3 again with the one liner for the obvious C thinko?
As usual in a volunteer project, the reason is: Because so far, none of
the maintainers has had the time or energy to do the necessary testing
in a stretch environment to make sure that this gdm3 change will not
cause regressions, and write a summary of the bug that justifies to the
stable release managers why it is sufficiently important that the SRMs
should accept the risk of regressions from including an updated package
in stable.
smcv
