Callahan Kovacs

Two more bug reports for this issue: - https://github.com/canonical/snapcraft/issues/4923 - https://github.com/canonical/snapcraft/issues/4548

Another bug report for this issue with an context of how it makes debugging CI builds very challenging: https://github.com/canonical/snapcraft/issues/4933

Another report where Launchpad builds on uncommon architectures (riscv64) produce unhelpful error messages: https://bugs.launchpad.net/snapcraft/+bug/2080728

Once snapd 2.66 is released, snapcraft will be able to show the stderr from snapd. Snapcraft will need to filter the stderr and only show the line that begins with...

Snapd 2.66 has been [released](https://forum.snapcraft.io/t/distribution-support-status/38524), so we can now fix this in Snapcraft. On a related note, we added some validation for common scenarios that used to fail when running...

Hi @skidoomanubuntu, We recently fixed that endless loop in snapcraft [7.5.4](https://github.com/snapcore/snapcraft/releases/tag/7.5.4). With that version, snapcraft should timeout and warn about network issues. This error occurs when the LXD container doesn't...

Hi @boukendesho, No we haven't had any progress on this. At our current pace, #5243 is likely to be completed first.

> I believe this is also an issue for `core22` snaps, and extending this to supporting those bases would also be nice. Can you double-check? The same yaml should work...

Closing this issue because of this functionality was added in core22 and newer bases and is an enhancement, not a bug, for core20. The effort required and risk of regressions...

Thanks for the report. Looks like this is failing for all craft applications as the issue is upstream in craft-parts ([source](https://github.com/canonical/craft-parts/blob/836a4fb7fbba405fc06e4da4d51117cdb99982b9/craft_parts/errors.py#L491)).