On 7/1/20 1:56 PM, Adam D. Barratt wrote: > On Tue, 2020-06-30 at 17:45 -0700, Noah Meyerhans wrote: >> Control: retitile -1 buster-pu: package cloud-init/20.2-2+deb10u1 >> Control: tags + >> patch > > I'm not sure that tagging pu bugs "patch" makes much sense, fwiw. Any > pu bug that doesn't have a patch attached is by definition incomplete. > >> Let's try to finally get something done with this cloud-init update. >> The request is to update to upstream version 20.2 in buster. This >> version is currently in both testing and buster-backports. It has >> been tested by the cloud team and others in common cloud environments >> including Microsoft Azure, AWS, and OpenStack. It contains fixes for >> bugs including #936030, and implements support for the IMDSv2 API in >> Amazon EC2. >> >> It backports cleanly from testing to buster, with no changes beyond >> the debian/changelog update. > > Have the changes been tested on buster using this proposed package, or > just with the unstable/testing/backports versions? > > What does a binary debdiff between the current stable package and the > proposed package look like? > >> Full debdiff against buster's 18.3-6 is attached. > > fwiw, that debdiff was large enough (even compressed) that the mail > didn't make it to debian-release. > > +cloud-init (20.2-2+deb10u1) buster; urgency=medium > > The version needs to be /lower/ than the package in unstable, so a > backported version is 20.2-2~deb10u1, similarly to bpo. > > Regards, > > Adam >
FYI, I tested cloud-init 20.2-2 on OpenStack (on a cloud running the Buster release of OpenStack: Rocky), and it all works well. I haven't seen any problems in the cloud-init logs. I didn't run the official backport: I just did my own backport, then took the Debian official OpenStack raw image, mounted it, and upgraded cloud-init in the mounted chroot. I then recompressed the image into qcow2 and started. All went well... Cheers, Thomas Goirand (zigo)
