Bug#1064235:

2024-04-29 Thread Noah Meyerhans
On Thu, Apr 18, 2024 at 10:17:27AM +0200, Arthur LUTZ wrote: >A small heads up on this issue, we have some minor impacts : >* sudo commands show a warning > > sudo: unable to resolve host example: Name or service not known Thanks for the report. This is resolved with the 20240429 images

Bug#1064235:

2024-04-18 Thread Noah Meyerhans
On Thu, Apr 18, 2024 at 10:17:27AM +0200, Arthur LUTZ wrote: >Hi, >A small heads up on this issue, we have some minor impacts : >* sudo commands show a warning > > sudo: unable to resolve host example: Name or service not known > >On a more problematic side (but not breaking) we

Bug#1064235:

2024-04-18 Thread Arthur LUTZ
Hi, A small heads up on this issue, we have some minor impacts : * sudo commands show a warning sudo: unable to resolve host example: Name or service not known On a more problematic side (but not breaking) we have filebeat that generates a lot of logs with warnings related to the change : *

Bug#1064235: cloud.debian.org: systemd-resolved et al. status (bookworm)

2024-04-15 Thread Flavio Veloso Soares
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 remo

Bug#1064235: cloud.debian.org: systemd-resolved et al. status (bookworm)

2024-04-11 Thread Noah Meyerhans
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.

Bug#1064235: cloud.debian.org: systemd-resolved et al. status (bookworm)

2024-04-03 Thread Flavio Veloso Soares
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

Bug#1064235: cloud.debian.org: systemd-resolved et al. status (bookworm)

2024-04-03 Thread Noah Meyerhans
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 righ

Bug#1064235: cloud.debian.org: systemd-resolved et al. status (bookworm)

2024-04-03 Thread Flavio Veloso Soares
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 re

Bug#1064235: cloud.debian.org: systemd-resolved et al. status (bookworm)

2024-02-18 Thread Flavio Veloso Soares
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" (https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.en.html