Re: [Bug 1761994] Re: Shift of conntrackd to systemd notification causes upgrade issues from Xenial

2018-04-18 Thread Mark Shuttleworth
Ah, elegant approach, BUT we'll need to maintain that patch carefully if it doesn't get upstreamed, a lazy future merge will just cause the problem to resurface. Mark -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1761994] Re: Shift of conntrackd to systemd notification causes upgrade issues from Xenial

2018-04-16 Thread Launchpad Bug Tracker
This bug was fixed in the package conntrack-tools - 1:1.4.4+snapshot20161117-6ubuntu2 --- conntrack-tools (1:1.4.4+snapshot20161117-6ubuntu2) bionic; urgency=medium * d/p/enable-runtime-systemd.patch: Enable systemd runtime support by default since the package is compiled with

[Bug 1761994] Re: Shift of conntrackd to systemd notification causes upgrade issues from Xenial

2018-04-16 Thread Corey Bryant
Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895826 ** Bug watch added: Debian Bug tracker #895826 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895826 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1761994] Re: Shift of conntrackd to systemd notification causes upgrade issues from Xenial

2018-04-16 Thread Corey Bryant
Just to be clear, the new version of the package patches the conntrackd code to default to 'Systemd on', as opposed to requiring 'Systemd on' in /etc/conntrackd/conntrackd.conf. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1761994] Re: Shift of conntrackd to systemd notification causes upgrade issues from Xenial

2018-04-16 Thread Corey Bryant
I've uploaded conntrack-tools 1:1.4.4+snapshot20161117-6ubuntu2 to bionic. This version of the package defaults to using 'Systemd on' for conntrackd config. I tested upgrades from xenial to bionic with the following in the bionic config /etc/conntrackd/conntrackd.conf: 1) 'Systemd on'

[Bug 1761994] Re: Shift of conntrackd to systemd notification causes upgrade issues from Xenial

2018-04-16 Thread Corey Bryant
Since the package is built with --enable-systemd I don't see why we wouldn't default the config to 'Systemd on'. I'm going to look into patching this. ** Changed in: conntrack (Ubuntu) Status: New => Triaged ** Changed in: conntrack (Ubuntu) Importance: Undecided => High -- You

Re: [Bug 1761994] Re: Shift of conntrackd to systemd notification causes upgrade issues from Xenial

2018-04-13 Thread Mark Shuttleworth
Yes, the issue is on upgrade, where if you don't add the 'Systemd on' config, it fails. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761994 Title: Shift of conntrackd to systemd notification

[Bug 1761994] Re: Shift of conntrackd to systemd notification causes upgrade issues from Xenial

2018-04-12 Thread Corey Bryant
Hi Mark, Thanks for reporting this. Does this look like the error that you hit? https://paste.ubuntu.com/p/4bv3PGBfMF/ I wasn't able to reproduce this using the default package config when upgrading conntrackd from xenial to bionic, however if I remove "Systemd on" from the bionic config file

[Bug 1761994] Re: Shift of conntrackd to systemd notification causes upgrade issues from Xenial

2018-04-08 Thread Hans Joachim Desserud
** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761994 Title: Shift of conntrackd to systemd notification causes upgrade issues from Xenial To manage notifications about