Fix AppImage error with libpcap#971
Conversation
|
Will this work with older distributions though? 🤔 |
|
And why was it happening even if we were using bookworm? https://packages.debian.org/search?searchon=sourcenames&keywords=libpcap |
|
It was happening because the manifest was pulling the package from the repository for the latest version of Debian. I could've modified to keep it pulling from the bookworm repository, but since the .deb is now being built for trixie I decided to update that line and keep it pulling from stable. |
I did not consider this, though. libpcap from Trixie requires glibc 2.38. Seeing as the main |
libpcap
|
Changed it to use Debian 10 libpcap. It would be possible to use Debian 11, but that would cause breakage in August next year when it's archived. |
|
Thanks, I prefer this solution. I'm also wondering whether I should also fix something in the .deb package building and the Docker package (they're both built on a ubuntu-latest runner) 🤔 |
|
Bookworm libpcap requires glibc 2.33, which would have prevented running it on, among others, Debian 11 and Ubuntu 20.04. |
|
What about using ubuntu-latest for building the AppImage as well? Is that possible? So we're consistent with how I'm building the other packages. |
|
Please elaborate. In what way would ubuntu-latest be used in the AppImage build, beyond being the runner? |
|
Using it as the dist in the ingredients section. But I'm not really sure if it's possible and meaningful. |
|
That would cause the same problem as using Debian 13, with the libpcap requiring too new versions of glibc. |
|
If you remove the libpcap package from your host system you should be able to replicate the issue, or you can run the AppImage with the flag |
|
Works fine now!! Thanks so much for your responsiveness and availability. |

#859 (comment) Seems to have been caused by Debian 13 changing the name of the libpcap package. I've updated the manifest to use the new name.