Package: cloud-init / 22.4.2-1+deb12u2

Metadata

Package Version Patches format
cloud-init 22.4.2-1+deb12u2 3.0 (quilt)

Patch series

view the series file
Patch File delta Description
fix sysvinit dependencies.patch | (download)

sysvinit/debian/cloud-config | 4 2 + 2 - 0 !
sysvinit/debian/cloud-final | 2 1 + 1 - 0 !
sysvinit/debian/cloud-init-local | 2 1 + 1 - 0 !
3 files changed, 4 insertions(+), 4 deletions(-)

 fix sysv-init dependencies.

cloud init before chronyd.patch | (download)

systemd/cloud-init.service.tmpl | 1 1 + 0 - 0 !
1 file changed, 1 insertion(+)

 cloud-init before chronyd

Bug-Debian: https://bugs.debian.org/910801
0009 Drop all unused extended version handling.patch | (download)

tools/read-version | 45 3 + 42 - 0 !
1 file changed, 3 insertions(+), 42 deletions(-)

 drop all unused extended version handling
0012 Fix message when a local is missing.patch | (download)

tools/Z99-cloud-locale-test.sh | 36 4 + 32 - 0 !
1 file changed, 4 insertions(+), 32 deletions(-)

 fix message when a local is missing.


0001 config Support APT automated mirror selection.patch | (download)

cloudinit/config/cc_apt_configure.py | 22 21 + 1 - 0 !
cloudinit/config/schemas/schema-cloud-config-v1.json | 5 5 + 0 - 0 !
tests/unittests/config/test_apt_configure_mirrorlists_v3.py | 68 68 + 0 - 0 !
3 files changed, 94 insertions(+), 1 deletion(-)

 [patch] config: support apt automated mirror selection
networkd_Add_support_for_multiple_Route_sections.patch | (download)

cloudinit/net/networkd.py | 51 45 + 6 - 0 !
tests/unittests/net/test_networkd.py | 57 56 + 1 - 0 !
2 files changed, 101 insertions(+), 7 deletions(-)

 [patch] networkd: add support for multiple [route] sections (#1868)

Networkd supports multiple [Route] sections within the same file.
Currently all [Route] section tags are squashed into one and if there
is a default gateway it means defining a device route is not possible
as the target is set to the default gateway.

This patch adds support for multiple [Route] sections allowing us to
support device routes. This is done by tracking each route in the route
list individually and ensuring the key-value pairs are maintained within
their respective [Route] section. This both maintains backwards
compatibility with previous behavior and allows the specification of
routes with no destination IP, causing the destination to be added with
a device target.