Snapcraft

A core24 snap creation fails on compression (RISCV64)

Bug #2080728 reported by Claudio André on 2024-09-14

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	Snapcraft	New	Undecided	Unassigned
	snapd	Fix Released	Undecided	Unassigned	snapd 2.65

Bug Description

Since July, the “final” step (compression) of creating a snap package is failing, printing the message below:

```
[...]
Running linter: library
Creating snap package...
Command '['snap', 'pack', '--filename', 'john-the-ripper_1.9J1+07aef97_riscv64.snap', '--compression', 'xz', PosixPath('/build/john-the-ripper/prime'), PosixPath('/build/john-the-ripper')]' returned non-zero exit status 20.
Full execution log: '/root/.local/state/snapcraft/log/snapcraft-20240914-141157.452959.log'
[...]
```

It works on all other archs and the message seems to blame the compression process itself. In other words, it's not related to “my code”.

See, on 2024-07-23
https://launchpad.net/~claudioandre.br/john/+snap/john-the-ripper/+build/2549421/+files/buildlog_snap_ubuntu_noble_riscv64_john-the-ripper_BUILDING.txt.gz

See, on 2024-09-14
https://launchpad.net/~claudioandre.br/john/+snap/john-the-ripper/+build/2597662/+files/buildlog_snap_ubuntu_noble_riscv64_john-the-ripper_BUILDING.txt.gz

Revision history for this message

Callahan Kovacs (mr-cal) wrote on 2024-09-16:

Hi,

This is a failure with the command `snap pack` such as a missing file, but may not be related to the `--compression` argument.

Unfortunately, we have an outstanding bug where `snap pack` failures are not sent to stdout. They are captured in the log file, but that is not accessible in launchpad builds.

We have an outstanding issue here https://github.com/canonical/snapcraft/issues/4499, which is blocked by upstream work in snapd to produce printable error messages (https://bugs.launchpad.net/snapd/+bug/2070926?comments=all).

Revision history for this message

Claudio André (claudioandre.br) wrote on 2024-09-20:

Only riscv64 is affected by the issue Edit (73.8 KiB, image/png)

Revision history for this message

Claudio André (claudioandre.br) wrote on 2024-09-21:

NOTE: reverting the package to core22 solves the issue, as seen:
https://launchpadlibrarian.net/750651356/buildlog_snap_ubuntu_jammy_riscv64_john-the-ripper_BUILDING.txt.gz

21 Sep
Snapcraft 8.3.4

So we don't know what's wrong, but we do know that it's related to core24.

Claudio André (claudioandre.br) on 2024-09-22

summary:

- A snap creation fails on compression (RISCV64 only)
+ A core24 snap creation fails on compression (RISCV64)

Revision history for this message

Philip Meulengracht (the-meulengracht) wrote on 2024-09-23:

Hey!

This is a known issue and should be fixed in newer snapd. The snapd on RISCV (in stable) is currently a bit older, and have issues with core24 for riscv.

If you switch to snapd in edge, does this solve it for you?

Changed in snapcraft:
status:	New → Incomplete
status:	Incomplete → Confirmed
Changed in snapd:
status:	New → Fix Committed
Changed in snapcraft:
status:	Confirmed → New
Changed in snapd:
milestone:	none → 2.65

Revision history for this message

Claudio André (claudioandre.br) wrote on 2024-09-23:

Launchpad ISSUE Edit (67.7 KiB, image/png)

> If you switch to snapd in edge, does this solve it for you?

I tried setting “edge” as shown in the attached image, but it failed to save [1]. So, I'll wait for 2.65 to be moved to stable. No hurry, there's already a workaround.

```
[1]
Server Error: TransactionFailedError
Request-Id
e9a3d11e-9c94-45a9-9579-cb6f8f67fc08
[...]
Connectionclose
[...]
Refererhttps://launchpad.net/~claudioandre.br/john/+snap/john-the-ripper/+edit
```