Bug#1021326: marked as done (wiki.debian.org: Incorrect ami id on Cloud/AmazonEC2Image/Stretch)
Your message dated Thu, 6 Oct 2022 08:33:25 -0700
with message-id <Yz71RcvVUoPhlHRn@doom.morgul.net>
and subject line Re: Bug#1021326: wiki.debian.org: Incorrect ami id on Cloud/AmazonEC2Image/Stretch
has caused the Debian Bug report #1021326,
regarding wiki.debian.org: Incorrect ami id on Cloud/AmazonEC2Image/Stretch
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
1021326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021326
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: wiki.debian.org
On https://wiki.debian.org/Cloud/AmazonEC2Image/Stretch arm64 ami id is indicated as ami-0d78ea9dc521d7ed3 for both region ca-central-1 and eu-central-1.
The ami id seems to be correct for eu-central-1, but does not exist in ca-central-1. The correct ami id for ca-central-1 seems to be ami-0bd9e6cecc0099058 based of the documented ami name and AWS account ID documented on the same wiki page.
--- End Message ---
--- Begin Message ---
On Wed, Oct 05, 2022 at 04:44:59PM -0400, Boyuan Yang wrote:
> > On https://wiki.debian.org/Cloud/AmazonEC2Image/Stretch arm64 ami id is
> > indicated as ami-0d78ea9dc521d7ed3 for both region ca-central-1 and eu-
> > central-1.
> >
> > The ami id seems to be correct for eu-central-1, but does not exist in ca-
> > central-1. The correct ami id for ca-central-1 seems to be ami-
> > 0bd9e6cecc0099058 based of the documented ami name and AWS account ID
> > documented on the same wiki page.
>
> Forwarding your issue to Debian Cloud Team.
This is fixed, thank you.
--- End Message ---
Reply to: