As seb128 found, the issue is also affecting the debian package of snapd
since when we call mksquashfs, we actually have code which specifically
calls mksquashfs from the "system" snap which is either the snapd snap
or the core snap, this is presumably to ensure that a consistent
mksquashfs is used always and to avoid snaps from being packed with too
old or new mksquashfs's.
So the net effect is that the fix for this that was landed into the
snapd snap will also probably need to be added to the core snap for
completeness, and also means that the only way to avoid snap pack from
failing is to have a snapd snap with the fix which is only available on
the edge channel currently.
So long story short, if you are affected by this today, a short-term
workaround is to use the edge channel of the snapd snap by running
snap refresh snapd --edge
We have already included the fix into the snapd snap that is built on
edge and it will be included in the release branch for 2.52, meaning
that the next bugfix release on 2.52 will have the fix, we do plan on
doing a 2.52.1 release in short order after 2.52 is complete, but it may
be a few weeks from now before that is on stable.
** Changed in: snapd
Milestone: None => 2.52
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943077
Title:
snapd fails to autopkgtest on mksquashfs, which is looking for
libgcc_s
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1943077/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
