`build-attributes: [enable-patchelf]` uses incorrect dynamic linker when setting binary ELF interpreter on core24 about snapcraft HOT 5 CLOSED

@mr-cal to clarify my comment on Element, I did not see the issue when building LXD inside an ubuntu-daily:24.04 container using SNAPCRAFT_BUILD_ENVIRONMENT=host snapcraft --verbose. I tested this snap on a ubuntu 22.04 system and it worked fine.

However I did see the issue when using the normal snapcraft invocation that manages its own LXD container and image.

from snapcraft.

Some things I need to investigate for this:

1. In this example, something is staging libc6 and snapcraft is using it (as designed).
   • I'm not sure how lib6 is getting staged or why this is only occurring in core24. We should follow Sergio's advice, "Check also if the dpkg.list we use to filter stage-packages is in place for core24, remember core24 is most likely moving to chisel, so would be good to sync with the Ubuntu Core team on that"
2. patchelf stops running when an override-prime script is defined (even if it calls craftctl default)
   • I have not been able to reproduce this with a simple reproducer. I need to to try this with the slurm snap.
3. We have a related issue reported here. Building this snap works locally but produces linter errors when using snapcraft remote-build

from snapcraft.

This bug appears to have the same problem @tomponline experienced, where the linter disagrees with what patchelf did.

from snapcraft.

@mr-cal thanks, do you know when this will land in a snap channel?

from snapcraft.

This should be in edge later today.

It should be included in the next hotfix release 8.0.3, but @sergiusens would know the timing for that.

from snapcraft.