On Fri, 24 Nov 2017 at 09:24:22 +0100, Tim Rühsen wrote:
> On 11/23/2017 03:37 PM, Helmut Grohne wrote:
> > The bug is
> > supposedly fixed upstream, so I expected it to be fixed with a new
> > upstream release rather than applying my patch.
>
> If it helps, I can make up a new upstream release.
> Let me know if there is something that should be applied before.
I don't think anything special needs to be done upstream now: I've changed
the Debian packaging to refresh the gtk-doc files before build, which
(if accepted by the libidn Debian maintainers) will decouple libidn from
the version of gtk-doc used when the upstream release was prepared. This is
a bit better from the point of view of ensuring Debian is self-contained
and built from "the real source code" anyway.
For future libidn releases, it might be helpful to other downstream
distributions if you could prepare the release (make dist) on a system
with gtk-doc-tools >= 1.26.
Regards,
smcv
