Callahan Kovacs

> [`craft_platforms._errors.InvalidBaseError: cannot specify a core 'build-base' alongside a 'base'`](https://github.com/canonical/snapcraft/actions/runs/12860277143/job/35851964190?pr=5106#step:5:240) This failure is a consequence of using pydantic validators to modify the data [here](https://github.com/canonical/snapcraft/blob/3aacad74bf055ea8cb88f00c510f57d870aefcf7/snapcraft/models/project.py#L1149). There's probably not a way around...

Thanks for the bug report. I can confirm this is a regression with how snapcraft and craft-application load project files. We will need some refactoring in craft-application to support this.

This is fixed in Snapcraft 8.9 for core24 but requires regression testing to ensure it doesn't fail again.

Thanks for the report. @jhenstridge provided a minimal reproducer [here](https://forum.snapcraft.io/t/getting-themed-icons-to-work-with-snap/46126/6?u=mr_cal). In summary, the problem is that Snapcraft doesn't allow for themed icons and specifying an icon file. This happens after...

Thanks for the report @simondeziel. I've made a bug for the upstream work: https://github.com/canonical/craft-grammar/issues/89

I've added it to the pulse. We still need to scope the work.

You're correct, this should be snapctl, not craftctl.

Hi, can you please raise issues against [snapd](https://bugs.launchpad.net/snapd) and [review-tools](https://bugs.launchpad.net/review-tools)? As you pointed out, since Snapcraft calls `snap pack`, there isn't much we can do in Snapcraft.

Thanks for submitting an upstream bug. I agree, we'll leave this issue open here until it's resolved between snapd and review-tools.

We will need to land https://github.com/canonical/snapcraft/pull/5603 first to fix the docs.