This release will be tentatively promoted to the 7.x/stable channel on 2022-08-03T03:00:00Z if not issues are found during the testing period. The team appreciates your involvement.
Been experimenting with this release and I have encountered some issues with the meson plugin when trying to snap GNOME applications. It looks like meson is not being installed in the build environment which is causing the parts that use the meson plugin to fail.
After running snapcraft on my amd64 machine, the amd64 snap is built correctly, but the arm64 build fails with the error Stage package not found in part ātheengs-gatewayā: bluez.
Previously (with Snapcraft 7.0) I built the arm64 snap on a jammy LXC container on an arm64 machine, and the armhf snap on an a jammy LXC container on an armhf machine, and this just worked: the stage package bluez was found and the resulting snaps installed and ran fine locally. Building the arm64 snap on arm64 or the armhf snap on armhf with Snapcraft 7.1 also works, and the resulting snaps install and run fine too. So it seems something is going wrong with stage packages while cross-compiling.
Hereās the project:
Hereās the pull request where I try to use the architectures support:
$ snapcraft remote-build
snapcraft remote-build is experimental and is subject to change - use with caution.
Issues while validating snapcraft.yaml: The 'apps/spot/extensions[0]' property does not match the required schema: 'gnome' is not one of ['flutter-stable', 'flutter-beta', 'flutter-dev', 'flutter-master', 'gnome-3-28', 'gnome-3-34', 'gnome-3-38', 'kde-neon', 'ros1-noetic', 'ros2-foxy']
Using remote-build because for some reason lxd locally is using IPV6 and failing and I donāt have the time or inclination to debug it, so thought I could test remotely instead.
@koenvervloesem, nice find and thanks for filing a launchpad bug!
Iām seeing the same failure.
When building on amd64 with core20, snapcraft will download bluez from the amd64 repository.
When building on amd64 with core22, snapcraft attempts to download bluez from the arm64 repository, then fails because the arm64 repository was never added.
Will this be going to latest/stable in addition to 7.x/stable when you push the button? That will be most helpful as I need the gnome extension to be available via the build service for some of my snaps now (remote build doesnāt work as @popey pointed out)
Well for positive feedback - Iāve used it successfully over the past few days to port several snaps over to core22 and the gnome extension nowā¦ No issues to be seen from my end so farā¦
Related to the fix above, is there any functionality similar to this hack of mine for ensuring that root-anchored symlinks are rewritten to be relative (so that they point to the file within the snap filesystem rather than the root/base-snap filesystem)? https://github.com/snapcrafters/gimp/blob/master/snap/snapcraft.yaml#L169-L183
As soon as it is in stable. I believe what Alan alludes to is being able to test the in-flight version of Snapcraft using remote-build through launchpad builders