s/2.12/2.11+git20180213-1/
Apologies for the noise, I made the mistake of typing my previous e-mail before
my morning coffee.
I've tested the above 2.11 release from experimental on a few systems and don't
see anything abnormal. As before, if there's anything I can do to help
get this into
the stretch{,-backports}, I'd be more than willing.
Best,
Francis
On 25 February 2018 at 12:15, Debian Bug Tracking System
<ow...@bugs.debian.org> wrote:
> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
> Patrick Matthäi <pmatth...@debian.org>
>
> If you wish to submit further information on this problem, please
> send it to 859...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 859387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859387
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
