package/systemd: bump to version 249
PATCH v2 1/1 package/systemd: bump to version 249
Add new host-python3-jinja2 dependency.
---
Changes v1 -> v2:
- add host-python3-jinja2 host-systemd dependency
--- package/systemd/systemd.hash | 4 ++-- package/systemd/systemd.mk | 6 ++++-- 2 files changed, 6 insertions(+), 4 deletions(-)
package/systemd/systemd.hash +2 -2
@@ -1,6 +1,6 @@ # sha256 locally computed -sha256 2869986e219a8dfc96cc0dffac66e0c13bb70a89e16b85a3948876c146cfa3e0 systemd-247.3.tar.gz +sha256 0d9d45140e95f2d0ee79005ccf867f2706976c30391b932a8c3b9b198a801fad systemd-249.tar.gz sha256 ab15fd526bd8dd18a9e77ebc139656bf4d33e97fc7238cd11bf60e2b9b8666c6 LICENSE.GPL2 sha256 dc626520dcd53a22f727af3ee42c770e56c97a64fe3adb063799d8ab032fe551 LICENSE.LGPL2.1 -sha256 6f22d19d35b00f35e0444e0bc9139e6d3bdf7277978f89c4e175e37b18c43f3d README +sha256 f5645b4b846479859d6618fa7a5a1722681aa7fc43c1e45f8bf8e1fe5738d618 README sha256 83bb6bd9ccd2cf5230cb1807ed16258289768dc4d9cb80069a814e04415a1275 tools/chromiumos/LICENSE
package/systemd/systemd.mk +4 -2
@@ -4,7 +4,7 @@ # ################################################################################ -SYSTEMD_VERSION = 247.3 +SYSTEMD_VERSION = 249 SYSTEMD_SITE = $(call github,systemd,systemd-stable,v$(SYSTEMD_VERSION)) SYSTEMD_LICENSE = LGPL-2.1+, GPL-2.0+ (udev), Public Domain (few source files, see README), BSD-3-Clause (tools/chromiumos) SYSTEMD_LICENSE_FILES = LICENSE.GPL2 LICENSE.LGPL2.1 README tools/chromiumos/LICENSE
@@ -14,6 +14,7 @@ SYSTEMD_DEPENDENCIES = \ $(BR2_COREUTILS_HOST_DEPENDENCY) \ $(if $(BR2_PACKAGE_BASH_COMPLETION),bash-completion) \ host-gperf \ + host-python3-jinja2 \ kmod \ libcap \ util-linux-libs \
@@ -717,7 +718,8 @@ HOST_SYSTEMD_DEPENDENCIES = \ host-util-linux \ host-patchelf \ host-libcap \ - host-gperf + host-gperf \ + host-python3-jinja2 HOST_SYSTEMD_NINJA_ENV = DESTDIR=$(HOST_DIR)
Signature · 1 line
2.25.1
PATCH v2 1/1 package/systemd: bump to version 249
Am Do., 8. Juli 2021 um 14:41 Uhr schrieb James Hilliard <[email protected]>:
Quoted 57 lines
Add new host-python3-jinja2 dependency.
Signed-off-by James Hilliard <[email protected]>---
Changes v1 -> v2:
- add host-python3-jinja2 host-systemd dependency--- package/systemd/systemd.hash | 4 ++-- package/systemd/systemd.mk | 6 ++++-- 2 files changed, 6 insertions(+), 4 deletions(-)package/systemd/systemd.hash +2
-2@@ -1,6 +1,6 @@ # sha256 locally computed -sha256 2869986e219a8dfc96cc0dffac66e0c13bb70a89e16b85a3948876c146cfa3e0 systemd-247.3.tar.gz +sha256 0d9d45140e95f2d0ee79005ccf867f2706976c30391b932a8c3b9b198a801fad systemd-249.tar.gz sha256 ab15fd526bd8dd18a9e77ebc139656bf4d33e97fc7238cd11bf60e2b9b8666c6 LICENSE.GPL2 sha256 dc626520dcd53a22f727af3ee42c770e56c97a64fe3adb063799d8ab032fe551 LICENSE.LGPL2.1 -sha256 6f22d19d35b00f35e0444e0bc9139e6d3bdf7277978f89c4e175e37b18c43f3d README +sha256 f5645b4b846479859d6618fa7a5a1722681aa7fc43c1e45f8bf8e1fe5738d618 README sha256 83bb6bd9ccd2cf5230cb1807ed16258289768dc4d9cb80069a814e04415a1275 tools/chromiumos/LICENSEpackage/systemd/systemd.mk +4
-3@@ -4,7 +4,7 @@ # ################################################################################ -SYSTEMD_VERSION = 247.3 +SYSTEMD_VERSION = 249 SYSTEMD_SITE = $(call github,systemd,systemd-stable,v$(SYSTEMD_VERSION)) SYSTEMD_LICENSE = LGPL-2.1+, GPL-2.0+ (udev), Public Domain (few source files, see README), BSD-3-Clause (tools/chromiumos) SYSTEMD_LICENSE_FILES = LICENSE.GPL2 LICENSE.LGPL2.1 README tools/chromiumos/LICENSE@@ -14,6 +14,7 @@ SYSTEMD_DEPENDENCIES = \ $(BR2_COREUTILS_HOST_DEPENDENCY) \ $(if $(BR2_PACKAGE_BASH_COMPLETION),bash-completion) \ host-gperf \ + host-python3-jinja2 \ kmod \ libcap \ util-linux-libs \@@ -717,7 +718,8 @@ HOST_SYSTEMD_DEPENDENCIES = \ host-util-linux \ host-patchelf \ host-libcap \ - host-gperf + host-gperf \ + host-python3-jinja2 HOST_SYSTEMD_NINJA_ENV = DESTDIR=$(HOST_DIR) --
Quoted 2 lines
2.25.1
Hi James,
Two points:
v248 came with 2 new options: oomd and sysext, those should be disabled for the host build and probably configurable for the target.
v249 supports creating transient user/groups with password, this requires adaption in nsswitch.conf:
@@ -581,6 +581,8 @@ endef
define SYSTEMD_INSTALL_NSSCONFIG_HOOK
$(SED) '/^passwd:/ {/systemd/! s/$$/ systemd/}' \
-e '/^group:/ {/systemd/! s/$$/ [SUCCESS=merge] systemd/}' \
+ -e '/^shadow:/ {/systemd/! s/$$/ systemd/}' \
+ -e '/^gshadow:/ {/systemd/! s/$$/ systemd/}' \
$(if $(BR2_PACKAGE_SYSTEMD_RESOLVED), \
-e '/^hosts:/ s/[[:space:]]*mymachines//' \
-e '/^hosts:/ {/resolve/! s/files/filesresolve [!UNAVAIL=return]/}' ) \
Other than that, looks fine. But TBH I usually wait a couple point releases before
using systemd in production.
Norbert