Snapcraft modifies binaries
Metadata
Current evaluation
⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.
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.
Suggested action: —
No scores available.
Issue body
When building with snapcraft 2.40.1 (or 2.39.2), the resulting snap file binaries differ by 4096 bytes from the original binaries that reside in the parts directory.
Under snapcraft 2.35, the resulting binaries from the parts directory match the snap exactly.
It's unclear if this behavior is limited to classic snaps or not, but I discovered this issue with the juju snap which is classic.
Here's comparing sha256sums for a binary for juju snap. Just to ensure there isn't something odd with unsquashfs, I also installed the snap and compared the mounted binary as well.
Under 2.39.2(or 2.40.1)
fafec8a06edb6e80069591436b92cfc84bc58aaee5b6992976f3b00b3851b2c0 squashfs-root/bin/jujud
58d50e028b7840aa2c1a25476037895588fa7241c51940da69367e4164ca8b9f parts/juju/install/bin/jujud
fafec8a06edb6e80069591436b92cfc84bc58aaee5b6992976f3b00b3851b2c0 /snap/juju/current/bin/jujud
du -b /snap/juju/current/bin/jujud squashfs-root/bin/jujud parts/juju/install/bin/jujud
121452768 /snap/juju/current/bin/jujud
121452768 squashfs-root/bin/jujud
121448672 parts/juju/install/bin/jujud
Redoing the build with snapcraft 2.35 I get matching binaries as expected.
58d50e028b7840aa2c1a25476037895588fa7241c51940da69367e4164ca8b9f squashfs-root/bin/jujud
58d50e028b7840aa2c1a25476037895588fa7241c51940da69367e4164ca8b9f parts/juju/install/bin/jujud.
58d50e028b7840aa2c1a25476037895588fa7241c51940da69367e4164ca8b9f /snap/juju/current/bin/jujud
du -b /snap/juju/current/bin/jujud squashfs-root/bin/jujud parts/juju/install/bin/jujud
121448672 /snap/juju/current/bin/jujud
121448672 squashfs-root/bin/jujud
121448672 parts/juju/install/bin/jujud
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | 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. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. Snapcraft versions 2.39.2 and 2.40.1 unexpectedly appended 4096 bytes to binaries, a regression from 2.35. The report received no comments or patches and was abandoned. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution. The binary modification issue in snapcraft 2.39.2 and 2.40.1 was not addressed, indicating the report was abandoned or superseded by newer releases. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1746607 snapcraft 2.38 is very slow | snapcraft (launchpad) | closed | A performance regression in snapcraft 2.38 was abandoned and closed without resolution or comments. No fix or merge was implemented. | |
| #1660696 Snapcraft is testing file collisions on unbuilt parts | snapcraft (launchpad) | closed | Closed without a merged fix. Snapcraft incorrectly checked file collisions on unbuilt parts, causing file not found errors. The author verified a local workaround, but the report was closed without upstream resolution or discussion. | |
| #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. | |
| #1548225 Snapcraft/snappy should detect incompatible version mismatches | snapcraft (launchpad) | closed | 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. | |
| #1723965 snapcraft doesn't work | snapcraft (launchpad) | closed | Closed without resolution or comments, indicating abandonment. The reported snap command failure and GL driver errors remain unresolved. | |
| #1566363 snapcraft deb touches snap-package systemd files | snapcraft (launchpad) | closed | Closed without resolution. The report described unexpected systemd file modifications during snapcraft package removal, but no fix or follow-up was documented. | |
| #1742373 Zip packages are not extracted properly with snapcraft 2.35 | snapcraft (launchpad) | closed | Closed without documented resolution. Author provided a code workaround. Likely abandoned or resolved in a later release. | |
| #1583718 snapcraft command doesn't include expected changes | snapcraft (launchpad) | closed | Closed without resolution or comments. The build caching bug was abandoned or superseded by later improvements, requiring manual cache cleaning as a workaround. | |
| #1907721 Snapcraft broken on ARM64 | snapcraft (launchpad) | closed | Closed without comments. No fix or merge was applied. The ARM64 Multipass QEMU error and YAML !PrimeState deserialization bug were likely resolved by upstream Snapcraft updates or abandoned. | |
| #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. |