### Check existing issues - [x] I've verified that this bug isn't described by any existing issues. ### Bug description While upgrading the [upower snap](https://github.com/canonical/upower-snap) for Ubuntu Core 26, I have noticed that some packages, such as libc, are pulled as dependencies for the only staged package (libgudev-1.0-0), which then triggers a lots of linter warnings. ``` Lint warnings: - classic: usr/bin/upower: ELF interpreter should be set to '/snap/upower/current/usr/lib64/ld-linux-x86-64.so.2'. (https://documentation.ubuntu.com/snapcraft/stable/how-to/debugging/use-the-classic-linter) - classic: usr/bin/upower: ELF rpath should be set to '$ORIGIN/../lib/x86_64-linux-gnu'. (https://documentation.ubuntu.com/snapcraft/stable/how-to/debugging/use-the-classic-linter) - classic: usr/lib/x86_64-linux-gnu/gconv/ANSI_X3.110.so: ELF rpath should be set to '$ORIGIN/..'. (https://documentation.ubuntu.com/snapcraft/stable/how-to/debugging/use-the-classic-linter) ``` I would not expect libc to be needed here, as the default version in resolute is high enough (libc 2.43, which is >= 2.38, the requested dependency). I checked by launching a minimal resolute LXC container, and running apt install libgudev-1.0-0, and no additional dependency is pulled. When crafting (with the same snapcraft version) the snap with a core24 base, the parts/upower/stage folder contains only the expected staged package: libgudev-1.0-0. ### Steps to reproduce Clone [upower-snap](https://github.com/canonical/upower-snap), checkout the snap-26 branch, and apply commits for this [PR](https://github.com/canonical/upower-snap/pull/10) if not yet merged. Build with snapcraft 8.14.4 and observe the linter warnings, and staged packages. You can compare with the snap-24 branch. ### Environment Using LXD to build, host OS is Ubuntu 24.04. ### snapcraft.yaml ```yaml ``` ### Log output ```shell ```