Callahan Kovacs

> I believe this bug is solved by https://github.com/canonical/craft-application/pull/437 Indeed, the error now recommends adjusting the `platforms` key in the project file. ``` No build matches the current execution environment....

Thanks for the report! I can reproduce this with pyelftools. ### Reproducer with pyelftools 1.Build the snap to create the problematic binary (or use the base64 encoded copy of it...

Thanks, @sevaa!

We've rewritten our documentation to [describe this behavior](https://canonical-snapcraft.readthedocs-hosted.com/en/stable/common/craft-parts/explanation/lifecycle/) (pull runs on all parts before further steps).

We have 2 other reports of this bug at https://bugs.launchpad.net/snapcraft/+bug/1992557 and https://bugs.launchpad.net/snapcraft/+bug/2007789 and an internal issue, CRAFT-1640. The problem is that the core18|20 implementation of remote-build (the legacy remote builder)...

We are planning to fix this. The scope of work is: 1. add `build-for` to `schema/snapcraft.yaml` 2. in the legacy codebase, ensure `build-for` and `run-on` are mutually exclusive and the...

Hi @lgp171188, There was a similar issue with charmcraft [here](https://github.com/canonical/snapcraft/issues/4266). Can you try removing `python3-pip` as a `stage-package` in your `snapcraft.yaml`?

Implemented as a prototype in a feature branch via #4914.

Oddly, I can't reproduce this on 8.3.2 and or latest/edge: | version | reproducible? | |--|--| | 8.2.12 | yes | | 8.3.0 | yes | | 8.3.1 | yes...

No longer reproducible with: ```yaml name: hello-core22 base: core22 version: '0.1' summary: hello description: hello grade: devel confinement: devmode architectures: - amd64 - arm64 parts: my-part: plugin: nil override-build: |...