Callahan Kovacs

Making this fix has some concerning side effects with overlays in craft-parts. We have some upstream documentation and design work to do before this can be completed (https://github.com/canonical/craft-parts/issues/766).

I see 2 things here: 1. ``` architectures: - build-on: [amd64, arm64] build-for: [arm64] - build-on: [amd64, armhf] build-for: [armhf] ``` giving strange progress and logs. This line ``` Building...

We've made many improvements to the remote-builder that shoudl address problems like Launchpad reporting the wrong architectures. Other behaviors here, such as using `--build-for` while `architectures` are defined in the...

Ah, I can reproduce this and can confirm it is a problem with how errors percolate from the managed (inner) snapcraft instance. Here's what happens: 1. The manager (outer) snapcraft...

We may be able to do something akin to https://medium.com/geekculture/exception-propagation-from-another-process-bb09894ba4ce. This would probably be best implemented in craft-application.

Hi @ifrguy, Building your snap, I get the same error: ```shell > snapcraft pack ... 2024-02-28 07:08:34.511 :: 2024/02/28 07:08:33.871928 container.go:215: in snap "hello": path "bin" does not exist 2024-02-28...

I'm going to close this as a duplicate because we have this bug and the work to resolve it described in #4499. If you have more to discuss, the bug...

This is a good idea, but it may become moot when #4879 is implemented, where we will not allow combinations like `base: core22, build-base: core24` in a `snapcraft.yaml`. With #4879,...

Snapcraft 8 supports `--ua-token` for core20 and core22 snaps. We're still working on this story for core24, where Pro LXD containers may be a replacement (https://github.com/canonical/craft-providers/compare/main...feature/pro-sources).

Yes, that is how I understand it. The design is still in-progress, so it may change.