[Touch-packages] [Bug 1883447] Re: nspawn on some 32-bit archs blocks _time64 syscalls, breaks upgrade to focal in containers

2021-03-18 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 237-3ubuntu10.45 --- systemd (237-3ubuntu10.45) bionic; urgency=medium [ Ioanna Alifieraki ] * d/p/lp1911187-systemctl-do-not-shutdown-immediately-on-scheduled-shutdo.patch: Do not shutdown immediately when scheduled shutdown fails

[Touch-packages] [Bug 1883447] Re: nspawn on some 32-bit archs blocks _time64 syscalls, breaks upgrade to focal in containers

2021-03-09 Thread Dan Streetman
root@test:~/f# dpkg -l|grep systemd-container ii systemd-container 237-3ubuntu10.44armhf systemd container/nspawn tools root@test:~/f# systemd-nspawn Spawning container f on /root/f. Press ^] three times within 1s to kill container. root@f:~# python3 Fatal

[Touch-packages] [Bug 1883447] Re: nspawn on some 32-bit archs blocks _time64 syscalls, breaks upgrade to focal in containers

2021-03-08 Thread Steve Dodd
LGTM! -- 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/1883447 Title: nspawn on some 32-bit archs blocks _time64 syscalls, breaks upgrade to focal in containers Status in

[Touch-packages] [Bug 1883447] Re: nspawn on some 32-bit archs blocks _time64 syscalls, breaks upgrade to focal in containers

2021-03-08 Thread Ɓukasz Zemczak
Hello Steve, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.45 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://

[Touch-packages] [Bug 1883447] Re: nspawn on some 32-bit archs blocks _time64 syscalls, breaks upgrade to focal in containers

2021-03-03 Thread Dan Streetman
** Description changed: [impact] nspawn fails on armhf [test case] - TBD + setup a bionic armhf system, and get a focal img/filesystem to use with + systemd-nspawn, e.g. + + $ wget https://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-armhf-root.tar.xz + $ mkdir f +

[Touch-packages] [Bug 1883447] Re: nspawn on some 32-bit archs blocks _time64 syscalls, breaks upgrade to focal in containers

2021-02-22 Thread Dan Streetman
** Description changed: + [impact] - Recent Linux kernels introduced a number of new syscalls ending in _time64 to fix Y2038 problem; it appears recent glibc, including the version in focal, test for the existence of these. systemd-nspawn in bionic (237-3ubuntu10.38) doesn't know about these

[Touch-packages] [Bug 1883447] Re: nspawn on some 32-bit archs blocks _time64 syscalls, breaks upgrade to focal in containers

2020-10-01 Thread Dan Streetman
@anarchetic could you update the description with the SRU template: https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template and in particular having a clearly documented reproducer in the [test case] section will help. thanks! -- You received this bug notification because you are a member

[Touch-packages] [Bug 1883447] Re: nspawn on some 32-bit archs blocks _time64 syscalls, breaks upgrade to focal in containers

2020-08-06 Thread Balint Reczey
This commit is already present in Focal and later releases. ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Released ** Changed in: systemd (Ubuntu Focal) Status: New => Fix Released ** Al

[Touch-packages] [Bug 1883447] Re: nspawn on some 32-bit archs blocks _time64 syscalls, breaks upgrade to focal in containers

2020-08-06 Thread Steve Dodd
This bug also seems to generate "Assertion 'clock_gettime(map_clock_id(clock_id), &ts) == 0' failed at src/basic /time-util.c:55, function now(). Aborting" in various places if you try to boot an existing 20.04 container on bionic with systemd-nspawn. -- You received this bug notification because