Callahan Kovacs
Callahan Kovacs
I agree that this is would be a very useful enhancement but I don't believe there is a precedence. For example, snapcraft doesn't check if remote sources have been modified...
This is a good idea. We can start with the same design as a `snapcraft.yaml` file where snapcraft first looks for `snapcraft.yaml` then looks for `snap/snapcraft.yaml`. Do you want to...
@lupaulus Try `sudo rm -r ~/.cache/snapcraft/stage-packages/`
You might have to delete the `~/.cache/snapcraft` dir.
`core20` snaps require LXD to be installed as a snap whereas `core22` and `core24` snaps do not. We should backport the [logic from craft-providers](https://github.com/canonical/craft-providers/blob/5c12422b367de3f96d5f0f2d1838331adc21c9f8/craft_providers/lxd/installer.py#L112-L117) to [snapcraft_legacy](https://github.com/canonical/snapcraft/blob/9456f71d804e148d7b60f68bd691c5f89bc78a89/snapcraft_legacy/internal/build_providers/_lxd/_lxd.py#L66-L75) to support building `core20`...
This is similar to #4960. Same function, but fails on the `apt` code instead of the `snap` code.
When we implement #4892, we should implement this as well.
Waiting on #5092 to land first sounds like a good plan. Thanks!
Closing because this is stale and I didn't investigate it properly at the time. If we get another bug report, I can investigate further.
I'm able to reproduce this directly with craft-parts. I proposed a solution in https://github.com/canonical/craft-parts/issues/766 but I'm not sure what side-effects it will have.