Snapcraft/snappy should detect incompatible version mismatches
Metadata
Current evaluation
⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.
Abandoned. The report detailed Snapcraft failing to detect version mismatches, causing large snaps to install incorrectly. With zero comments and over a decade of dormancy, it received no resolution and was closed.
Suggested action: —
No scores available.
Issue body
Going for creating a LibreOffice snap with Snapcraft 2.2.2 on xenial finishes without error message or error code, but results in an uninstallable image.
Here is what is happening on trying to install the snap in a vagrant created snappy instance:
(amd64)ubuntu@ubuntu-core-edge-15:~$ sudo snappy install libreoffice_5.0.4_amd64.snap
Installing libreoffice_5.0.4_amd64.snap
libreoffice_5.0.4_amd64.snap failed to install: open /tmp/read-file704372866/unpack/meta/package.yaml: no such file or directory
Note that:
- other snaps (e.g."hello world") install fine in that instance
- at least "file libreoffice_5.0.4_amd64.snap" is convinced this is a squashfs
- there were snaps created on Snapcraft 1.0.2/wily, that just installed fine in that instance
- this snap is currently 928MB -- so this might also be a problem in snappy, not snapcraft (e.g. running out of storage somewhere).
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Abandoned. The report detailed Snapcraft failing to detect version mismatches, causing large snaps to install incorrectly. With zero comments and over a decade of dormancy, it received no resolution and was closed. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without comments after over a thousand days, indicating it was abandoned or superseded by newer Snapcraft/snappy releases that later addressed version mismatch detection. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without comments or resolution. The version mismatch and package.yaml error were not addressed, indicating the issue was abandoned or superseded by newer Snapcraft/snappy releases. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #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. | |
| #1925050 snapcraft status missing information | snapcraft (launchpad) | closed | snapcraft status missing information for arch: all revisions was closed without comments or resolution, indicating the report was abandoned or superseded. | |
| #1497453 snapcraft fails if it needs to pull a deb that has an uninstallable version on the system | snapcraft (launchpad) | closed | Abandoned. Closed without documented resolution or fix. The bug caused a TypeError crash when snapcraft attempted to pull a deb package with an incompatible system version during stage setup. | |
| #1752964 Snapcraft snap broken on trusty | snapcraft (launchpad) | closed | Closed without resolution. Snapcraft v2.39.2 failed on Ubuntu Trusty due to a missing liblz4.so.1 dependency for mksquashfs. No comments were posted, and the report was likely abandoned following Trusty's end-of-life. | |
| #1670100 Snapcraft includes files from installed snaps in new snap | snapcraft (launchpad) | closed | Abandoned due to inactivity. Snapcraft incorrectly bundled files from previously installed snaps into new builds, but no fix or follow-up was 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. | |
| #1663625 No script named 'snapcraft' | snapcraft (launchpad) | closed | A report of snapcraft failing after apt installation was closed without resolution or comments, indicating the matter was abandoned. | |
| #2013112 Installing snapcraft under a different name causes version mixup | snapcraft (launchpad) | closed | The snapcraft parallel install version mixup was closed without resolution. With zero comments and over three years of inactivity, the bug was abandoned and remains unfixed. | |
| #1956216 Snapcraft is no longer working within a Docker container | snapcraft (launchpad) | closed | Closed without resolution. The report detailed a snapcraft ModuleNotFoundError in Docker containers, but received no comments or fixes. The issue remains abandoned. | |
| #1761488 snapcraft 2.39.2 failed to release a snap: snapcraft.storeapi.errors.StoreReleaseError: <exception str() failed> | snapcraft (launchpad) | closed | Closed without resolution. The report details a StoreReleaseError during snapcraft 2.39.2 release attempts. With zero maintainer comments and significant age, the issue was likely abandoned. No fix or workaround was provided. |