[Touch-packages] [Bug 1752722] Re: systemd 237 reports incorrect state when drop-in present

2018-03-02 Thread Brian Moyles
It looks like this was fixed upstream and it would be fantastic if this could make it into Bionic before anything is frozen. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/17

[Touch-packages] [Bug 1752722] Re: systemd 237 reports incorrect state when drop-in present

2018-03-01 Thread Brian Moyles
This does not appear to affect Artful and systemd 234. Example session: ~# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=17.10 DISTRIB_CODENAME=artful DISTRIB_DESCRIPTION="Ubuntu 17.10" ~# uname -a Linux ip-100-65-137-86 4.13.0-36-generic #40-Ubuntu SMP Fri Feb 16 20:07:48 UTC 2018 x86

[Touch-packages] [Bug 1752722] [NEW] systemd 237 reports incorrect state when drop-in present

2018-03-01 Thread Brian Moyles
Public bug reported: Raised this upstream: https://github.com/systemd/systemd/issues/8328 In short, in systemd 237 as it ships with Bionic, if a unit has a drop- in present but has been masked, systemctl is-enabled and systemctl list- unit-files report incorrect state, showing the units as enable

[Touch-packages] [Bug 1651278] Re: systemd-sysv-generator does not fully translate facilities to targets

2016-12-19 Thread Brian Moyles
If at all possible, I'd love to see this fix backported to Xenial. Given that the bug appears to have existed as long as the sysv-generator has, the biggest risk is to those who may be erroneously depending on the incorrect behavior (whether explicitly or otherwise). I've attached a very basic sys

[Touch-packages] [Bug 1651278] [NEW] systemd-sysv-generator does not fully translate facilities to targets

2016-12-19 Thread Brian Moyles
Public bug reported: See the bug raised here: https://github.com/systemd/systemd/issues/4762 and fixed upstream here: https://github.com/systemd/systemd/commit/e932f5407ef5ad05d25d7dfefa4cda0fe81cc346 In short, given a sysv-init script with valid LSB headers, one of which defines Required-Start:

[Touch-packages] [Bug 1503382] Re: unable to install python3.4 dev on fresh ubuntu cloud image

2015-10-06 Thread Brian Moyles
We encountered the same and were able to overcome it by force-downgrading python3.4, python3.4-minimal, libpython3.4-stdlib, and libpython3.4-minimal to the current version available in the repositories with apt-get install -y \ python3.4=3.4.0-2ubuntu1.1 \ python3.4-minimal=3.4.0-2ubuntu1.1