The backport is quite complicated due to several changes that made the
DNS code in nm-1-12 diverge from nm-1-10. The th/policy-and-mdns
branch [1] alone changed:
so, unless we decide to also backport that branch, the backport of the
fix requires reimplementing several non-trivial patches on top of
1.10, with the high risk of breaking things.
If we also backport the th/policy-and-mdns branch, we would need to
backport a total of 30+ commits, including mDNS support and related
libnm API.
Any opinions? This latter approach seems doable, but it is a big
change for a minor release.
The backport is quite complicated due to several changes that made the
DNS code in nm-1-12 diverge from nm-1-10. The th/policy-and-mdns
branch [1] alone changed:
src/dns/ nm-dns- dnsmasq. c | 330 +++++++ ++++++- ------- ------- ----- nm-dns- manager. c | 581 +++++++ +++++++ +++++++ +++++++ +++++-- ------- ------- ------- -- nm-dns- systemd- resolved. c | 219 +++++++ +++++++ ------- -
src/dns/
src/dns/
so, unless we decide to also backport that branch, the backport of the
fix requires reimplementing several non-trivial patches on top of
1.10, with the high risk of breaking things.
If we also backport the th/policy-and-mdns branch, we would need to
backport a total of 30+ commits, including mDNS support and related
libnm API.
Any opinions? This latter approach seems doable, but it is a big
change for a minor release.
[1] https:/ /cgit.freedeskt op.org/ NetworkManager/ NetworkManager/ log/?qt= range&q= 5eea9be983bd95f 5a482e483a438a1 00b80c716f