openembedded-core.git/meta/recipes-core/systemd, branch master-next2 Mirror of openembedded-core systemd: make vconsole a PACKAGECONFIG option 2017-03-31T11:24:53+00:00 Enrico Jorns ejo@pengutronix.de 2017-03-29T09:07:33+00:00 396e9dcf308a2a6660a84eb36c5ff29f8a0d08de Allowing to remove the systemd-vconsole-setup package without specifying the --disable-vconsole configure option for systemd will make the system boot with the failure prompt | systemd-udevd[142]: failed to execute '/lib/systemd/systemd-vconsole-setup' '/lib/systemd/systemd-vconsole-setup': No such file or directory | systemd-udevd[96]: Process '/lib/systemd/systemd-vconsole-setup' failed with exit code 2. as the 90-vconsole.rules will still be installed with having a RUN+="/lib/systemd/systemd-vconsole-setup" in it that attempts to execute a non-existing binary. Signed-off-by: Enrico Jorns <ejo@pengutronix.de> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Allowing to remove the systemd-vconsole-setup package without specifying
the --disable-vconsole configure option for systemd will make the system
boot with the failure prompt

| systemd-udevd[142]: failed to execute '/lib/systemd/systemd-vconsole-setup' '/lib/systemd/systemd-vconsole-setup': No such file or directory
| systemd-udevd[96]: Process '/lib/systemd/systemd-vconsole-setup' failed with exit code 2.

as the 90-vconsole.rules will still be installed with having a
RUN+="/lib/systemd/systemd-vconsole-setup" in it that attempts to
execute a non-existing binary.

Signed-off-by: Enrico Jorns <ejo@pengutronix.de>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
systemd: Do not add libnss_* to systemd package 2017-03-21T22:43:00+00:00 Amarnath Valluri amarnath.valluri@intel.com 2017-01-24T10:08:46+00:00 46046880e42ae924548eb5c0ec53f9448f6f932e libnss_* files should be part of corresponding sub-packages, the split happens by do_package_split(). By adding ${libdir}/libnss_* to FILES_${PN}, those files end up in the systemd package when ${libdir} == ${base_libdir}. Signed-off-by: Amarnath Valluri <amarnath.valluri@intel.com> 
libnss_* files should be part of corresponding sub-packages, the split happens
by do_package_split(). By adding ${libdir}/libnss_* to FILES_${PN}, those files
end up in the systemd package when ${libdir} == ${base_libdir}.

Signed-off-by: Amarnath Valluri <amarnath.valluri@intel.com>
systemd: check "ldconfig" distro feature when setting PACKAGECONFIG 2017-03-04T23:18:09+00:00 Andre McCurdy armccurdy@gmail.com 2017-01-27T22:29:11+00:00 faff19f046e881f546c1ad397e101c000c9bba3d Avoid trying to call ldconfig at run-time in distros which don't provide ldconfig on the target. Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
Avoid trying to call ldconfig at run-time in distros which don't
provide ldconfig on the target.

Signed-off-by: Andre McCurdy <armccurdy@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
recipes: Make use of the new bb.utils.filter() function 2017-03-01T11:17:22+00:00 Peter Kjellerstedt peter.kjellerstedt@axis.com 2017-02-27T13:02:50+00:00 0a1427bf9aeeda6bee2cc0af8da4ea5fd90aef6f Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
systemd: Add PACKAGE_WRITE_DEPS for postinst 2017-01-19T22:51:08+00:00 Jussi Kukkonen jussi.kukkonen@intel.com 2017-01-19T08:11:13+00:00 f186b0c59e707b9a3bff8fcf3b51dbcef5573298 Qemu is used to run udevadm in postinstall. Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> 
Qemu is used to run udevadm in postinstall.

Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com>
systemd-compat-units: Add PACKAGE_WRITE_DEPS for postinst 2017-01-19T22:51:06+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2017-01-19T17:01:10+00:00 279fec228282749f4ff6c95f79295c1e8b3db76d The postinstall needs systemd-systemctl-native, mark the dependency Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
The postinstall needs systemd-systemctl-native, mark the dependency

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
systemd: point to correct resolv.conf when resolved is enabled 2016-12-22T08:46:34+00:00 Khem Raj raj.khem@gmail.com 2016-12-16T22:07:31+00:00 99d1199fd0961f94732a1a533d66472ca17cf6f5 latest systemd has changed the resolved defaults which points to 127.0.0.53 port 53 on local network. If someone wants to use host-local IP address then it can be pointed to copy in /lib/systemd Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
latest systemd has changed the resolved defaults which points to
127.0.0.53 port 53 on local network. If someone wants to use
host-local IP address then it can be pointed to copy in /lib/systemd

Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
meta: remove True option to getVar calls 2016-12-16T08:30:03+00:00 Joshua Lock joshua.g.lock@intel.com 2016-12-14T21:13:04+00:00 7c552996597faaee2fbee185b250c0ee30ea3b5f getVar() now defaults to expanding by default, thus remove the True option from getVar() calls with a regex search and replace. Search made with the following regex: getVar ?\(( ?[^,()]*), True\) Signed-off-by: Joshua Lock <joshua.g.lock@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
getVar() now defaults to expanding by default, thus remove the True
option from getVar() calls with a regex search and replace.

Search made with the following regex: getVar ?\(( ?[^,()]*), True\)

Signed-off-by: Joshua Lock <joshua.g.lock@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
systemd: disable 'libdir' QA check 2016-12-16T08:30:02+00:00 Mark Asselstine mark.asselstine@windriver.com 2016-12-12T19:36:48+00:00 422077ff91c4147f08108fe8510b238730f2367c When building systemd with multilib support enabled in your build you will get the following QA warnings (if the 'libdir' QA check is enabled.) WARNING: systemd-1_232-r0 do_package_qa: QA Issue: systemd-dbg: found \ library in wrong location: /lib/systemd/.debug/libsystemd-shared-232.so systemd: found library in wrong location: /lib/systemd/libsystemd-shared.so systemd: found library in wrong location: /lib/systemd/libsystemd-shared-232.so [libdir] Since systemd 231 upstream has included an 'internal' library which they explicitly place in the application specific /lib/systemd directory. You can see some of the discussion about this placement here https://github.com/systemd/systemd/issues/3810 This placement is being picked up by the QA checker since when multilibs are enabled it expects all libraries to be in lib32 or lib64. Since the systemd and systemd-dbg packages don't contain any other libraries we can respect the upstream placement and skip this QA check for these packages. Unfortunately the QA mechanism doesn't allow us to specify individual files so this approach is the best we can do. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
When building systemd with multilib support enabled in your build you
will get the following QA warnings (if the 'libdir' QA check is
enabled.)

WARNING: systemd-1_232-r0 do_package_qa: QA Issue: systemd-dbg: found \
 library in wrong location: /lib/systemd/.debug/libsystemd-shared-232.so
systemd: found library in wrong location: /lib/systemd/libsystemd-shared.so
systemd: found library in wrong location: /lib/systemd/libsystemd-shared-232.so [libdir]

Since systemd 231 upstream has included an 'internal' library which
they explicitly place in the application specific /lib/systemd
directory. You can see some of the discussion about this placement
here https://github.com/systemd/systemd/issues/3810

This placement is being picked up by the QA checker since when
multilibs are enabled it expects all libraries to be in lib32 or
lib64. Since the systemd and systemd-dbg packages don't contain any
other libraries we can respect the upstream placement and skip this QA
check for these packages. Unfortunately the QA mechanism doesn't allow
us to specify individual files so this approach is the best we can do.

Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
systemd: Backport cgroup fix from 233 to 232 2016-12-13T22:47:32+00:00 Jason Wessel jason.wessel@windriver.com 2016-12-09T17:16:20+00:00 d212e97aeae502cd0d11cb922f7711aee5c1ace0 There is a critical regression in the default behavior with systemd 232 which prevents lxc, docker, and opencontainers from working properly out of the box. The change was already committed to the systemd 233 code stream. The failure looks like what is shown below. % lxc-start -n container -F lxc-start: cgfsng.c: parse_hierarchies: 825 Failed to find current cgroup for controller 'name=systemd' lxc-start: cgfsng.c: all_controllers_found: 431 no systemd controller mountpoint found lxc-start: start.c: lxc_spawn: 1082 failed initializing cgroup support lxc-start: start.c: __lxc_start: 1332 failed to spawn 'container' lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. Commit 843d5baf6aad6c53fc00ea8d95d83209a4f92de1 from the systemd git has been backported and can be dropped in a future uprev. Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
There is a critical regression in the default behavior with systemd
232 which prevents lxc, docker, and opencontainers from working
properly out of the box.  The change was already committed to the
systemd 233 code stream.

The failure looks like what is shown below.

% lxc-start -n container -F
lxc-start: cgfsng.c: parse_hierarchies: 825 Failed to find current cgroup for controller 'name=systemd'
lxc-start: cgfsng.c: all_controllers_found: 431 no systemd controller mountpoint found
lxc-start: start.c: lxc_spawn: 1082 failed initializing cgroup support
lxc-start: start.c: __lxc_start: 1332 failed to spawn 'container'
lxc-start: lxc_start.c: main: 344 The container failed to start.
lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options.

Commit 843d5baf6aad6c53fc00ea8d95d83209a4f92de1 from the systemd git
has been backported and can be dropped in a future uprev.

Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>