Skip to content

snap: Declared target platforms, skipped qaseprite on s390x/ppc64el#4535

Merged
bjorn merged 1 commit into
masterfrom
snap-s390x-ppc64el
Jun 2, 2026
Merged

snap: Declared target platforms, skipped qaseprite on s390x/ppc64el#4535
bjorn merged 1 commit into
masterfrom
snap-s390x-ppc64el

Conversation

@bjorn
Copy link
Copy Markdown
Member

@bjorn bjorn commented May 29, 2026

The snap-store auto-build was attempting all five Launchpad architectures (amd64, arm64, s390x, ppc64el, armhf) and silently failing on the latter three. Declared platforms: explicitly to limit the target set to amd64, arm64, s390x, and ppc64el (armhf is excluded because libqt5gui5 is no longer built for that arch in noble).

The qaseprite plugin bundles Aseprite's laf library, which static- asserts the CPU architecture against a hardcoded whitelist (x86/x64/arm64/riscv64). Skip the plugin's pull and build steps on s390x and ppc64el so the rest of the snap still builds; users on those arches lose .ase/.aseprite import.

The snap-store auto-build was attempting all five Launchpad
architectures (amd64, arm64, s390x, ppc64el, armhf) and silently
failing on the latter three. Declared `platforms:` explicitly to
limit the target set to amd64, arm64, s390x, and ppc64el (armhf is
excluded because libqt5gui5 is no longer built for that arch in
noble).

The qaseprite plugin bundles Aseprite's laf library, which static-
asserts the CPU architecture against a hardcoded whitelist
(x86/x64/arm64/riscv64). Skip the plugin's pull and build steps on
s390x and ppc64el so the rest of the snap still builds; users on
those arches lose .ase/.aseprite import.
@bjorn bjorn merged commit d353d43 into master Jun 2, 2026
17 checks passed
@bjorn bjorn deleted the snap-s390x-ppc64el branch June 2, 2026 12:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant