Hi Noah,
First of all many thanks for the new images and for the help with this
bug report.
Regarding removing libnss-resolve, that's good to know. I figured doing
bullseye->bookworm was not a good strategy long-term anyways, so I
decided to look further for a solution, which I found by
On Wed, Apr 03, 2024 at 09:39:40PM -0700, Flavio Veloso Soares wrote:
> Hi Noah - I guess I'll be doing bullseye->bookworm installs in the meantime,
> until 12.6 so I can fill bug reports (if any).
It should be plenty to start with the bookworm images and simply remove
the libnss-resolve package.
Hi Noah - I guess I'll be doing bullseye->bookworm installs in the
meantime, until 12.6 so I can fill bug reports (if any).
Appreciate the reply. Thanks for bringing me awareness of the issue in GH.
On 2024-04-03 20:01, Noah Meyerhans wrote:
Control: tags -1 + pending
On Wed, Apr 03, 2024 at
Control: tags -1 + pending
On Wed, Apr 03, 2024 at 06:48:56PM -0700, Flavio Veloso Soares wrote:
> Is this the correct forum to report issues/ask question about the official
> Debian images on AWS?
The BTS isn't really the correct forum to ask questions about any Debian
topics, but it is the
Hi,
Any update on this?
Is this the correct forum to report issues/ask question about the
official Debian images on AWS?
On 2024-02-18 13:09, Flavio Veloso Soares wrote:
> Hello,
>
> Bookworm's release notes clearly states that "systemd-resolved was
> not, and still is not, the default DNS
Package: cloud.debian.org
Severity: important
X-Debbugs-Cc: flavi...@magnux.com
Hello,
Bookworm's release notes clearly states that "systemd-resolved was
not, and still is not, the default DNS resolver in Debian"
6 matches
Mail list logo
