All autopkgtests for the newly accepted linux-meta (5.15.0.140.135) for jammy have finished running. The following regressions have been reported in tests triggered by the package:
acpi-call/unknown (arm64, ppc64el, s390x) adv-17v35x/unknown (amd64, arm64, ppc64el, s390x) apparmor/unknown (arm64, ppc64el, s390x) apparmor-profiles-extra/unknown (arm64, ppc64el, s390x) backport-iwlwifi-dkms/unknown (arm64, ppc64el, s390x) bbswitch/unknown (arm64) casper/unknown (arm64, ppc64el, s390x) cross-toolchain-base/unknown (arm64, s390x) dahdi-linux/unknown (arm64, ppc64el, s390x) ddcci-driver-linux/unknown (amd64, arm64, ppc64el, s390x) digimend-dkms/unknown (amd64, ppc64el) dm-writeboost/unknown (amd64, ppc64el, s390x) dpdk-kmods/unknown (amd64, ppc64el) evdi/unknown (amd64, ppc64el, s390x) fwts/unknown (amd64, ppc64el, s390x) glibc/unknown (amd64, ppc64el, s390x) gost-crypto/unknown (s390x) initramfs-tools/unknown (s390x) iptables-netflow/unknown (amd64) ipu6-drivers/unknown (amd64) ivsc-driver/unknown (amd64) jool/unknown (amd64) langford/unknown (amd64) librem-ec-acpi/unknown (amd64) libvirt/unknown (amd64, s390x) libvpoll-eventfd/unknown (amd64) lime-forensics/unknown (amd64, ppc64el, s390x) linux-apfs-rw/unknown (ppc64el, s390x) lttng-modules/unknown (ppc64el, s390x) lxc/unknown (ppc64el, s390x) nat-rtsp/unknown (s390x) openafs/unknown (s390x) r8125/unknown (ppc64el) r8168/unknown (amd64, ppc64el) rtl8812au/unknown (amd64) rtl8821ce/unknown (amd64, ppc64el) snapd/unknown (amd64) sysdig/unknown (amd64) systemd/249.11-0ubuntu3.15 (s390x) systemd/unknown (amd64) tp-smapi/unknown (amd64) ubuntu-drivers-common/unknown (amd64) v4l2loopback/unknown (amd64) virtualbox/unknown (amd64) west-chamber/unknown (amd64) wireguard/unknown (amd64) wireguard-linux-compat/unknown (amd64) xtables-addons/unknown (amd64) xtrx-dkms/unknown (amd64) zfs-linux/unknown (amd64, arm64) 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#linux-meta [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp