ubuntu/jammy: new_upstream_snapshot refresh patches to fix daily build recipe

debian/README.source

@@ -0,0 +1,30 @@
+=== General Info ===
+Packaging branches for the Ubuntu development release are maintained in
+upstream git under ubuntu/devel branch.
+
+   git clone git://git.launchpad.net/cloud-init -b ubuntu/devel
+
+Stable release branches are also available in ubuntu/<codename>
+   $ git clone git://git.launchpad.net/cloud-init
+   $ cd cloud-init
+   $ git branch -r
+   origin/HEAD -> origin/master
+   origin/master
+   origin/ubuntu/devel
+   origin/ubuntu/precise
+   origin/ubuntu/trusty
+   origin/ubuntu/xenial
+
+Patches in debian/patches are stored un-applied.
+
+== New snapshot ==
+Upstream maintains a script to handle new upstream snapshots at:
+  https://github.com/cloud-init/qa-scripts/
+Its usage is like:
+ new-upstream-snapshot master
+
+== Cherry Pick ==
+To cherry pick an upstream commit:
+ ./debian/cherry-pick <hash>
+
+That will add a patch to debian/patches/ and debian/patches/series.

debian/apport-general-hook.py

@@ -0,0 +1,12 @@
+"""General Apport hook for all reports that are using cloud-init."""
+
+from cloudinit.apport import general_add_info
+
+
+def add_info(report, ui) -> None:
+    """Entry point for Apport.
+
+    Add a subset of non-sensitive cloud-init data from
+    /run/cloud/instance-data.json that will be helpful for debugging.
+    """
+    general_add_info(report, ui)

debian/apport-launcher.py

@@ -0,0 +1,7 @@
+"""Wrapper for cloudinit apport interface"""
+
+from cloudinit.apport import add_info as cloudinit_add_info
+
+
+def add_info(report, ui):
+    return cloudinit_add_info(report, ui)