** Summary changed: - [SRU] 2.76.2 + [SRU] 2.76.3
** Description changed: - New Snapd release 2.76.2 is required for Jammy, Noble, Resolute and + New Snapd release 2.76.3 is required for Jammy, Noble, Resolute and Stonking - Snapd 2.76.2 is the latest upstream minor release. It follows the previous Ubuntu release snapd 2.76. + Snapd 2.76.3 is the latest upstream minor release. It follows the previous Ubuntu release snapd 2.76. Note: 2.76.1 was a security release. The Snapd package deviates from the standard SRU process. The following special SRU process was followed: <link to relevant SRU process doc> Release preparation: <link to release PR> - Release preparation test results: <link to test workflow results in GitHub> + Release preparation test results: <link to test workflow results in GitHub> Failure analysis: <link to comment on PR explaining failures> Release notes: <link to NEWS.md file from PR> Please refer to snapd release notes documentation (https://github.com/canonical/snapd/blob/master/RELEASE.md) for details on how this is assembled. Launchpad bugs addressed: https://launchpad.net/snapd/+milestone/<version> Content overview: - - TPM/FDE: Updated secboot to allow preinstall check to proceeding without HW root of trust - - TPM/FDE: Re-enable setting PIN/Passphrase during install - - TPM/FDE: Support keyboard configuration at install-time for first-boot - - selinux: Use init_named_socket_activation() for allowing systemd to start snapd through socket activation + - TPM/FDE: Updated secboot to allow preinstall check to proceeding without HW root of trust + - TPM/FDE: Re-enable setting PIN/Passphrase during install + - TPM/FDE: Support keyboard configuration at install-time for first-boot + - selinux: Use init_named_socket_activation() for allowing systemd to start snapd through socket activation Areas of potential regressions: The changes are focused mostly around very specific functionality the works together to allow TPM/FDE without HW root of trust. The PIN/Passphrase functionality was removed and now added again, so not completely new. The secboot changes is very specific and was thoroughly tested on the relevant HW. - Keyboard configuration is important for a subset keyboards that is not that common, and regardless it was also thoroughly tested. Selinux change is not applicable to Ubuntu. + Keyboard configuration is important for a subset keyboards that is not that common, and regardless it was also thoroughly tested. Selinux change is not applicable to Ubuntu. So overall the risk is low, and limited to a small TPM/FDE installation and and firstboot. Source packages on `ppa:snappy-dev/image` for upload to -proposed: <list short name releases and the link for their deb packages> Validation already completed: - Release preparation test results: <link to release PR run results> - QA Beta validation <link to beta validation Jira ticket> - Certification validation: <link to test observer results> (need VPN) Verification required: - Verify LP bugs for <list of short name target releases> - Perform release upgrades from <short name of earliest supported target release> to <short name of latest supported release> -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2158301 Title: [SRU] 2.76.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2158301/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
