snapcraft 2.8 fails on s390x
Metadata
Current evaluation
Closed without resolution. Snapcraft 2.8 failed on s390x due to a missing architecture table entry, but no fix or follow-up was recorded.
Suggested action: —
No scores available.
Issue body
with the update to 2.8 snapcraft seems to not know about the s390x architecture anymore ...
we use the snapcraft snap command to roll the ubuntu-core os snap for all arches, since today this fails with the error shown in http://paste.ubuntu.com/15848428/
seems like some table is simply missing an entry for s390x
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. Snapcraft 2.8 failed on s390x due to a missing architecture table entry, but no fix or follow-up was recorded. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed. The missing s390x architecture entry in snapcraft 2.8 was not addressed; the report was closed without explicit resolution or follow-up comments. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without documented resolution. The missing s390x architecture entry in snapcraft 2.8 caused build failures. Likely fixed in a subsequent release or abandoned. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed. Fixed by adding s390x to snapcraft's architecture table, resolving the build failure introduced in version 2.8. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1628457 snapcraft fails on s390x with utf8 error | snapcraft (launchpad) | closed | Closed without a fix. The report detailed a UTF-8 encoding error in snapcraft 2.18 causing s390x builds to fail. The issue was abandoned with no code changes or resolution provided. | |
| #1641123 snapcraft does not properly detect the architecture when kernel is 64 bits but userspace is 32 | snapcraft (launchpad) | closed | Closed without resolution. Snapcraft incorrectly identified arm64 architecture in 64-bit kernel/32-bit userspace chroots, generating mismatched snaps. The report was abandoned due to inactivity. | |
| #1691569 snapcraft fails when specifying 'any' architecture in build packages | snapcraft (launchpad) | closed | Closed without resolution. Snapcraft failed when build packages used the ':any' architecture suffix. The reporter suggested stripping the suffix to match apt behavior, but no fix or pull request was implemented. | |
| #1520248 snap with only scripts gets wrongs architecture set | snapcraft (launchpad) | closed | Closed without comments or resolution. Snapcraft 0.5 incorrectly flagged script-only snaps as missing amd64 binaries. The issue was abandoned and likely resolved in later snapcraft versions. | |
| #5638 Snapcraft fails to run on 32bit userspace container on 64bit ARM kernel. | snapcraft | closed | Closed and moved to internal tracking (SNAPCRAFT-1190). No fix merged; the proposed architecture mapping remains unimplemented. | |
| #1980536 snapcraft unusable on systems not using apt | snapcraft (launchpad) | closed | Closed without resolution. Snapcraft retained hard apt dependencies, causing crashes on non-Debian systems like Arch Linux. The issue appears abandoned with no fix provided. | |
| #1761598 Snapcraft modifies binaries | snapcraft (launchpad) | closed | Closed without resolution. Snapcraft 2.39.2 and 2.40.1 modified binaries by adding 4096 bytes, a regression from 2.35. The report was abandoned with no comments or fix applied. | |
| #3850 meta: add support for s390x | snapcraft | merged | Merged after approval and CI checks. Adds s390x architecture support to snapcraft 7 to align with snapcraft_legacy, modifying two files with four lines of code. | |
| #1981979 snapcraft 7.0.8+ stopped working on non debian systems | snapcraft (launchpad) | closed | Closed without resolution or comments. The reported apt_pkg error blocking snapcraft 7.0.8+ builds on non-Debian systems remains unfixed and the issue appears abandoned. | |
| #1769551 snapcraft 2.42 not working in trusty armhf | snapcraft (launchpad) | closed | Closed without comments or resolution. The author reverted to version 2.41, indicating the issue was abandoned or superseded by newer releases. |