** No longer affects: init-system-helpers (Ubuntu)
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1616422
Title:
[trusty SRU/FFE] Add systemd binary package fo
This bug was fixed in the package systemd - 204-5ubuntu20.20
---
systemd (204-5ubuntu20.20) trusty-proposed; urgency=medium
* Build systemd binary package.
Drop installation of /etc/* aside from systemd's own config files. This
avoids a package conflict with systemd-services
This bug was fixed in the package init-system-helpers - 1.14ubuntu1
---
init-system-helpers (1.14ubuntu1) trusty; urgency=medium
* script/deb-systemd-invoke: Replace with /bin/true. systemd as pid 1 and
for /lib/systemd/system/ is not supported in Ubuntu 14.04. It will only
Forgot to mention that the apparmor, libapparmor-perl, libapparmor1
packages are from Thomas' ppa as well.
Verification step 7,8,9 are all good for the 4.4 hwe kernel on Trusty.
And I check with 3.13 kernel again, it works with apparmor package
installed from Thomas' paa too.
As a result, I will
Oh OK!
As this bug was tagged with "verification-needed-trusty", I thought this
one needs to be tested with Trusty 3.13 kernel.
Today I tried with 14.04.5 server image with the proposed
4.4.0-49-generic #70 hwe kernel. It works.
The apparmor error is a good hint, the apparmor package needs to be
> ubuntu@ubuntu:~$ uname -a
> Linux ubuntu 3.13.0-102-generic #149-Ubuntu SMP Wed Nov 9 21:52:08 UTC 2016
> x86_64 x86_64 x86_64 GNU/Linux
This shows that you are running the trusty release kernel. snapd will
only be supported on trusty with the xenial hwe kernel. This probably
explains your app
snapd is not completely ready for trusty yet, as it needs quite a lot of
adjustments to work in that old environment:
https://github.com/snapcore/snapd/pull/2128 .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Hello Martin,
hello world does not work as well, but core snap can be installed
without any problem.
ubuntu@ubuntu:~$ snap list
Name Version Rev Developer Notes
core 16.04.1 394 canonical -
ubuntu@ubuntu:~$ uname -a
Linux ubuntu 3.13.0-102-generic #149-Ubuntu SMP Wed Nov 9 21:52:08 UTC 20
Thanks Po-Hsu. This is clearly a bug within test-snapd-tools, possibly
fixed by bug 1641243. Is there a simpler "hello world" type snap that
has a service that can be used to verify this without running into the
apparmor profile issue?
Steps 7 to 9 can be done independently.
--
You received this
Hello,
I tried to verify this with trusty server image on a laptop, everything
act as expected before step 6 (except that stuff like desktop startup,
suspend on lid close can't be tested with server image). After that it
failed with:
ubuntu@ubuntu:~$ sudo snap install test-snapd-tools
error: cann
Hello Martin, or anyone else affected,
Accepted systemd into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/204-5ubuntu20.20 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:/
Hello Martin, or anyone else affected,
Accepted init-system-helpers into trusty-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source/init-
system-helpers/1.14ubuntu1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new p
I discussed the current status with Thomas today, and he says that i-s-h
and systemd are good to go. I uploaded those to the trusty-proposed SRU
review queue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
** Description changed:
Rationale: For backporting snapd to 14.04 LTS, we need to provide
systemd's service manager (not just logind and auxiliary services like
logind or timesyncd). upstart will continue to do the actual booting,
and systemd will act as a "deputy init" which by default do
I uploaded that init-system-helpers fix to
https://launchpad.net/~pitti/+archive/ubuntu/systemd . Once that gets
uploaded to -proposed, I will add a versioned Breaks: to the new systemd
binary.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
** Description changed:
Rationale: For backporting snapd to 14.04 LTS, we need to provide
systemd's service manager (not just logind and auxiliary services like
logind or timesyncd). upstart will continue to do the actual booting,
and systemd will act as a "deputy init" which by default do
Thomas discovered another problem:
# apt-get remove colord
Removing colord (1.0.6-1) ...
Failed to issue method call: Unit colord.service not loaded.
dpkg: error processing package colord (--remove):
subprocess installed pre-removal script returned error exit status 5
Failed to issue method call:
** Also affects: init-system-helpers (Ubuntu)
Importance: Undecided
Status: New
** Changed in: init-system-helpers (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
git/PPA updated to 204-5ubuntu20.19pitti4 which now also fixes the hang
during dist-upgrading to 16.04 LTS. "reboot -f" after the upgrade is
still needed, though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
** Description changed:
Rationale: For backporting snapd to 14.04 LTS, we need to provide
systemd's service manager (not just logind and auxiliary services like
logind or timesyncd). upstart will continue to do the actual booting,
and systemd will act as a "deputy init" which by default do
** Description changed:
Rationale: For backporting snapd to 14.04 LTS, we need to provide
systemd's service manager (not just logind and auxiliary services like
logind or timesyncd). upstart will continue to do the actual booting,
and systemd will act as a "deputy init" which by default do
Status update:
> linked units from /etc/systemd/system are still being read. This needs
a bigger hammer.
Fixed in git.
> reboot is hanging
This was due to /lib/lsb/init-functions.d/40-systemd which diverted SysV
init scripts to systemctl which then ignored those as we want to disable
SysV suppo
> Status: Current git now removes/ignores /lib/systemd/system/
Not entirely yet, linked units from /etc/systemd/system are still being
read. This needs a bigger hammer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
Status: Current git now removes/ignores /lib/systemd/system/ and only
reads /lib/systemd/upstart/, where it ships the *.target's and journal
services. It also adjusts the dbus.service shim and cleans this up.
Remaining known problem is that reboot is hanging. I haven't tested
dist-upgrade to 16.04
> This also does not start systemd right after package installation.
Fixed in git.
Another issue: reboot hangs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1616422
Title:
[trusty SRU/FFE] Add sys
The code for this is in https://git.launchpad.net/~ubuntu-core-dev/+git
/systemd-trusty (I started with an import of the current trusty
version). A corresponding package is in
https://launchpad.net/~pitti/+archive/ubuntu/systemd .
This still does not match all the requirements from above: while it
26 matches
Mail list logo
