Dan, note that although we set the SNAP_REEXEC environment variable in that integration test, that environment variable is actually not obeyed when it comes to the mksquashfs command which is called here:
https://github.com/snapcore/snapd/blob/dfba7de59a41bc22786d87f53b20deea14240713/snap/squashfs/squashfs.go#L524 and the function snapdtool.CommandFromSystemSnap does not observe the SNAP_REEXEC environment variable at all, instead just checking if the snapd or core snaps exist at all, and using the mksquashfs from those snaps instead of what's on the host on $PATH (though we do fallback and if there is no mksquashfs found in the core or snapd snaps (somehow???), then we use $PATH). As I mentioned on IRC, we could potentially someday add a workaround where if mksquashfs from the system snap specifically segfaults then we will fall back to using the host's mksquashfs, but we have chosen for now not to work on that patch. Hope this helps explain things. -- 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
