On Tue, 13/11/2018 at 10:41 -0800, Diane Trout wrote:
On Tue, 2018-11-13 at 18:44 +0100, Daniel Dupont wrote:
Hi,
On Tue, 2018-11-13 at 09:19 -0800, Diane Trout wrote:
I thought they weren't supposed to be changing things in stable. I
don't suppose you could try the version in unstable?
Though honestly I need to fix a couple of bugs to release 0.17. If
I
can get that working maybe I can make a stretch backport for it.
Thank you for your message.
First of all, I would like:
- to confirm my analysis
- to identify the reason for this bug
- to identify the possible consequences
I have two production servers affected by this bug and I would
prefer
not to try unstable packages.
I wouldn't really call any version of dnssec-trigger stable. It's just
that 0.13 was bug free enough to make it into stretch.
It's not terribly surprising to me that a change in libnm might break
the python bindings. We had to make some changes in 0.15 because of
changes in libnm.
I had two ideas, either try downgrading to gir1.2-networkmanager-
1.0/libnm-glib4 1.6.2-3+debu9u2? (That's the stable version as opposed
to the version from stretch proposed updates, and it might require
downgrading some other network manager parts as well.
These two packages are stable stretch version and, unless I'm mistaken,
there is no version for stretch-updates or stretch-proposed-updates.
dldt@emt-g1:~$ dpkg -l|grep "\(gir1\.2-networkmanager-1\.0\|libnm-glib4\)"
ii gir1.2-networkmanager-1.0:amd64 1.6.2-3+deb9u2 amd64
GObject introspection data for NetworkManager
ii libnm-glib4:amd64 1.6.2-3+deb9u2 amd64
network management framework (GLib shared library)
--
Daniel Dupont
