On Tue, 18 Feb 2020 at 22:33:03 +0100, Andreas Henriksson wrote:
> There's a new upstream release of avahi available now, see:
> https://alioth-lists.debian.net/pipermail/pkg-utopia-maintainers/2020-February/027450.html
I've taken your changes from https://salsa.debian.org/ah/avahi,
reverted everything that would need a trip through NEW for now, and
made it available as
https://salsa.debian.org/utopia-team/avahi/-/merge_requests/1.
It seems to work. I also applied some fixes from upstream git
(which hopefully fix #876107), and proposed a patch to undo a Python 3
regression caused by that change.
The new upstream release includes local-only services via the loopback
interface (#909564).
https://salsa.debian.org/utopia-team/avahi/-/merge_requests/2 follows
up on that by disabling the Python 2 binding and enabling the Python 3
binding (#853239, #936173). This needs a trip through NEW.
I think the best plan for releasing this is probably to release 0.8-1
with Python 2 bindings to get some testing, and then a 0.8-2 that goes
through NEW and switches to Python 3.
I'm not sure whether to enable the libevent main loop binding as part
of that same trip through NEW, or keep it disabled until/unless someone
actually asks for it. Unless anyone knows of a potential user, I think
it might be a bit better to decouple Avahi from other package ecosystems
by leaving the libevent integration disabled until it's needed (and by
similar logic, I don't intend to enable the Qt 5 main loop integration
unless someone asks for it).
smcv
