Merge ~enr0n/ubuntu/+source/systemd:ubuntu-jammy-sru into ~ubuntu-core-dev/ubuntu/+source/systemd:ubuntu-jammy
Status: | Merged | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Merge reported by: | Lukas Märdian | ||||||||||||||||
Merged at revision: | 9e36277515a58976eeb46cf40b4f5b1816bc62c2 | ||||||||||||||||
Proposed branch: | ~enr0n/ubuntu/+source/systemd:ubuntu-jammy-sru | ||||||||||||||||
Merge into: | ~ubuntu-core-dev/ubuntu/+source/systemd:ubuntu-jammy | ||||||||||||||||
Diff against target: |
506 lines (+442/-0) 10 files modified
debian/changelog (+22/-0) debian/patches/lp2000880-network-create-stacked-netdevs-after-the-underlying-link-.patch (+33/-0) debian/patches/lp2002445/sd-netlink-add-a-test-for-rtnl_set_link_name.patch (+81/-0) debian/patches/lp2002445/sd-netlink-do-not-swap-old-name-and-alternative-name.patch (+54/-0) debian/patches/lp2002445/sd-netlink-restore-altname-on-error-in-rtnl_set_link_name.patch (+64/-0) debian/patches/lp2002445/udev-attempt-device-rename-even-if-interface-is-up.patch (+63/-0) debian/patches/lp2002445/udev-net-allow-new-link-name-as-an-altname-before-renamin.patch (+36/-0) debian/patches/lp2004478-network-dhcp4-accept-local-subnet-routes-from-DHCP.patch (+54/-0) debian/patches/lp2009502-Enable-dev-sgx_vepc-access-for-the-group-sgx.patch (+27/-0) debian/patches/series (+8/-0) |
||||||||||||||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Lukas Märdian | Approve | ||
Review via email:
|
Description of the change
Built in this PPA: https:/
autopkgtest results:
systemd 249.11-
systemd 249.11-
systemd 249.11-
systemd 249.11-
systemd 249.11-
The amd64 failure is in the upstream tests, which can be flaky (the amd64 tests passed for me locally).
Thank you for providing a test build and autopkgtest results and for confirming that the amd64 test passes for you locally.
This LGTM (thanks for making use of the "Gbp-Pq: Topic ..." header)!
Are the fixes/SRU for bug #2004478 & bug #2002445 for Kinetic and/or Lunar already in the pipeline? Those will block this SRU migrating to jammy-updates, but I think we can still go ahead and get it into -proposed for verification already. Generally, I feel it is the better approach to do SRUs from newer to older (Lunar -> ... -> Focal), but I know in this case we had some urgency to get the Focal SRU out and tested, so we'll work around this situation a bit.
I've rebased your work on the (very) recent security update "249.11-0ubuntu3.7" and picked the next free revision for your upload: "249.11- 0ubuntu3. 8".