All autopkgtests for the newly accepted systemd (249.11-0ubuntu3.8) for jammy have finished running. The following regressions have been reported in tests triggered by the package:
linux-intel-iotg/5.15.0-1027.32 (amd64) linux-lowlatency/5.15.0-68.75 (arm64, amd64) systemd/249.11-0ubuntu3.8 (arm64, ppc64el) openrazer/3.2.0+dfsg-3 (i386) multipath-tools/0.8.8-1ubuntu1.22.04.1 (s390x) netplan.io/0.105-0ubuntu2~22.04.1 (amd64) fwupd/1.7.9-1~22.04.1 (armhf) udisks2/2.9.4-1ubuntu2 (amd64) zfs-linux/unknown (s390x) dbus/1.12.20-2ubuntu4.1 (s390x) linux-ibm/5.15.0-1027.30 (amd64) samba/unknown (s390x) tang/11-1 (arm64) gvfs/1.48.2-0ubuntu1 (arm64) php8.1/unknown (s390x) linux-nvidia/5.15.0-1018.18 (amd64) csync2/2.0-25-gc0faaf9-1 (s390x) tinyssh/20190101-1ubuntu1 (s390x) mosquitto/2.0.11-1ubuntu1 (amd64) casync/2+20201210-1build1 (ppc64el) linux-gke/5.15.0-1029.34 (arm64, amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/2009502 Title: Enable /dev/sgx_vepc access for the group 'sgx' Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Committed Bug description: [ Impact ] On systems where Intel SGX is available, access to a specific device node (/dev/sgx_vepc) must be enforced, with a specific permission (0660) and group (sgx). This allows KVM-based virtual machines to use such feature (the SGX "enclaves") in a proper fashion. Without this, a manual udev rule needs to be created. [ Test Plan ] As the patch itself only tailors the permissions/group to the device node, in a system with Intel-SGX enabled, merely `ls -la` against the device node should show if the permissions and group are seen as expected. [ Where problems could occur ] N/A. This seems to be a very straightforward inclusion, very specific to access enablement to the SGX reserved memory used for hosting enclaves. [ Other Info ] N/A. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2009502/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
