-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upstream signald binaries requires glibc>=2.29 #31
Comments
I see 3 options:
|
Ogod yeah I would say let's focus on support for bullseye ... We should release an alpha in the coming weeks / days ... (Also we're jumping to v11 not v5, we're willing to match with debian version for simplicity) |
Upstream reverted to buster in order to fix this: https://gitlab.com/signald/libraries/libsignal-client/-/commit/f0b1c1a348c6d9f7182a11b8e747292fdeca0add Currently signald requires zkgroup which is still built on bullseye. This will change once the following is merged: https://gitlab.com/signald/signald/-/merge_requests/93 After that MR is merged into signald, the package should work again on buster. |
Should be fixed upstream, I tested the package locally. I pushed a change to the testing branch to depend on signald >=0.15.0-27 |
Upstream now builds native libraries using debian bullseye instead of buster. Bullseye upgrades glibc to
2.29
from2.28
. Since the rust toolchain is built with that, the binaries need 2.29 as well.I submitted a patch to upstream to build with buster, let's hope it gets accepted:
An alternative is to compile from source #9
Meanwhile, signald versions from about 3 weeks ago and up are unusable. The app will install, but linking a device is not possible:
The text was updated successfully, but these errors were encountered: