Bug#1072373: systemd: please implement restarting systemd using triggers

2024-06-01 Thread Aurelien Jarno
Package: systemd Version: 256~rc3-7 Severity: important Dear maintainer, To avoid issues like #1071462, please implement restarting systemd by declaring an interest on the "libc-upgrade" trigger, introduced in glibc 2.38-12. At some point this will allow us to drop the corresponding part of the

Bug#1071462: installing/upgrading libc6 does not work in sbuild when systemd is installed as ischroot declines

2024-05-20 Thread Aurelien Jarno
On 2024-05-20 10:40, Luca Boccassi wrote: > On Mon, 20 May 2024 at 10:37, Aurelien Jarno wrote: > > > > On 2024-05-20 10:22, Luca Boccassi wrote: > > > On Mon, 20 May 2024 at 10:20, Johannes Schauer Marin Rodrigues > > > wrote: > > > > > > >

Bug#1071462: installing/upgrading libc6 does not work in sbuild when systemd is installed as ischroot declines

2024-05-20 Thread Aurelien Jarno
md, sysv or any other system can then decide what to do instead of hardcoding that on the glibc side. That would also simplify the chrootless case a bit. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net

Bug#1071462: installing/upgrading libc6 does not work in sbuild when systemd is installed as ischroot declines

2024-05-20 Thread Aurelien Jarno
ochen also pointed out: telinit could be the component which > > checks > > what PID 1 actually is and only do its thing after it confirmed that it is > > indeed an init system like systemd that is providing PID 1? > > That's all legacy stuff and I really don't want to touch it anymore. > Going from the other side, maybe libc6.postinst could use something > more reliable than ischroot()? Is systemd-detect-virt able to figure > out the situation a bit better? Nope. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net

Bug#1058880: systemd-binfmt.service: unit fails to start when /proc/sys/fs/binfmt_misc is not mounted

2023-12-31 Thread Aurelien Jarno
On 2023-12-31 17:43, Michael Biebl wrote: > On Mon, 18 Dec 2023 01:47:51 +0100 Michael Biebl wrote: > > Am 17.12.23 um 13:44 schrieb Aurelien Jarno: > > > commit f74a7cb45c2458f90de6d37c70fa3afc1a3be279 > > > Author: Yu Watanabe > > > Date: Sat Dec 10 1

Bug#1058880: systemd-binfmt.service: unit fails to start when /proc/sys/fs/binfmt_misc is not mounted

2023-12-17 Thread Aurelien Jarno
Package: systemd Version: 252.19-1~deb12u1 Severity: normal Tags: upstream patch fixed-upstream X-Debbugs-Cc: d...@debian.org Dear maintainers, When /proc/sys/fs/binfmt_misc is not mounted (on purpose), systemd-binfmt.service fails to start: × systemd-binfmt.service - Set Up Additional Binary

Re: Bug#822733: tzdata: Drop /etc/timezone

2023-02-08 Thread Aurelien Jarno
Hi, On 2023-02-07 23:39, Michael Biebl wrote: > Hi > > Am 07.02.23 um 23:01 schrieb Aurelien Jarno: > > > 2022g-3. You probably want to change d-i to not create that file. > > Where specifically does d-i (i.e. which component) create /etc/timezone? This is do

Re: Bug#822733: tzdata: Drop /etc/timezone

2023-02-07 Thread Aurelien Jarno
> > > then consider removing this as well. > > > > > > > I would prefer, if all this is handled within tzdata. > > - It should stop creating /etc/timezone > > - It should delete /etc/timezone on upgrades as a one-time action Note that this means that newly installed systems will still have /etc/timezone, as they won't see the upgrade from versions older than 2022g-3. You probably want to change d-i to not create that file. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net

Bug#994006: libc6: NSS modules changes require a restart of systemd-logind, which is not possible

2021-09-09 Thread Aurelien Jarno
Package: libc6 Version: 2.32-1 Severity: serious X-Debbugs-Cc: pkg-systemd-maintain...@lists.alioth.debian.org The NSS modules provided by glibc 2.32 require new symbols, which are therefore not provided by libc6 2.31. This is why we require restarting daemons after the new libc6 is installed.

Bug#954312: systemd: FTBFS on riscv64: test-seccomp fails: Assertion 'name' failed at src/test/test-seccomp.c:49

2020-08-21 Thread Aurelien Jarno
On 2020-03-20 19:35, Michael Biebl wrote: > Am 20.03.20 um 19:21 schrieb Michael Biebl: > > Am 20.03.20 um 17:49 schrieb Aurelien Jarno: > >> So you were right that there are way more things to change than my > >> initial patch. I came up with the attach

Bug#954312: systemd: FTBFS on riscv64: test-seccomp fails: Assertion 'name' failed at src/test/test-seccomp.c:49

2020-04-04 Thread Aurelien Jarno
have a chance to be applied upstream. libseccomp releases are not really predictable, but it seems there are currently people working towards a release, so it might happens in the next months. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net ht

Bug#954312: systemd: FTBFS on riscv64: test-seccomp fails: Assertion 'name' failed at src/test/test-seccomp.c:49

2020-03-20 Thread Aurelien Jarno
no official > libseccomp release yet, which contains riscv64 support. Indeed, the patch has been merged upstream, but no version have been released yet. The Debian package contains a backport of the patch. -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net

Bug#954312: systemd: FTBFS on riscv64: test-seccomp fails: Assertion 'name' failed at src/test/test-seccomp.c:49

2020-03-20 Thread Aurelien Jarno
d the ping succeed. It looks like that I should also update the patch you pointed, I'll work on that and keep you updated. Thanks, Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net signature.asc Description: PGP signature

Bug#954312: systemd: FTBFS on riscv64: test-seccomp fails: Assertion 'name' failed at src/test/test-seccomp.c:49

2020-03-19 Thread Aurelien Jarno
Package: systemd Version: 245.2-1 Severity: normal Tags: patch Dear maintainer, The latest version of systemd enabled seccomp support on riscv64. Thanks for doing that. However it now fails to build due to the test test-seccomp failing: | 321/486 test-seccompFAIL

Bug#953878: libudev1-udeb: library wrongly shipped in the multiarch path

2020-03-14 Thread Aurelien Jarno
On 2020-03-14 14:55, Michael Biebl wrote: > Am 14.03.20 um 13:23 schrieb Aurelien Jarno: > > Package: systemd > > Version: 245-2 > > Severity: normal > > Tags: patch > > > > libudev1-udeb ships the libudev.so.1 in the multiarch path: > > > > | $

Bug#953878: libudev1-udeb: library wrongly shipped in the multiarch path

2020-03-14 Thread Aurelien Jarno
Package: systemd Version: 245-2 Severity: normal Tags: patch libudev1-udeb ships the libudev.so.1 in the multiarch path: | $ dpkg -c libudev1-udeb_245-2_amd64.udeb | drwxr-xr-x root/root 0 2020-03-12 12:55 ./ | drwxr-xr-x root/root 0 2020-03-12 12:55 ./lib/ | drwxr-xr-x root/root

Re: Comments regarding pci.ids_0.0~2019.06.30-1_amd64.changes

2019-09-06 Thread Aurelien Jarno
age would > have a way easier time just patching it, TBH. I fully agree with that. > BTW the current pciutils package (where pci.ids is shipped right now) > and the usb.ids source are pretty much in the same exact situation > (CCed Aurelien). Adding the systemd maintainers in

Bug#907409: casync: FTBFS with glibc 2.28, header mismatch wih new renameat2()

2018-11-29 Thread Aurelien Jarno
ync-2+20180321/debian/rules2018-08-27 09:50:17.0 -0700 > @@ -1,6 +1,7 @@ > #! /usr/bin/make -f > > export DEB_BUILD_MAINT_OPTIONS=hardening=+all > +export DEB_CFLAGS_MAINT_APPEND=-D_GNU_SOURCE > > export LC_ALL=C.UTF-8 glibc 2.28 is now in sid, therefore r