Adam I'm not sure what's going on or whats my role role in Debian. Please
if someone could tell me what is happening I deciphered
Pubian on March 5 2020 I tried to send you a message from
rhetoricb...@gmail.com and the profile says Pete Y. My emails are being
erased so if you don't get this I'm not surprised but if you could you send
a text or call 5045038792.
Thank you, Mark Reddin
On Wed, Jul 1, 2020 at 7:00 AM Adam D. Barratt <a...@adam-barratt.org.uk>
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
>
>
