Skip to content
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

Closed
MayeulC opened this issue Nov 15, 2021 · 4 comments · Fixed by #28
Closed

Upstream signald binaries requires glibc>=2.29 #31

MayeulC opened this issue Nov 15, 2021 · 4 comments · Fixed by #28
Labels
bug Something isn't working dependency isue We'd like to fix this, but the problem isn't ours

Comments

@MayeulC
Copy link
Collaborator

MayeulC commented Nov 15, 2021

Upstream now builds native libraries using debian bullseye instead of buster. Bullseye upgrades glibc to 2.29 from 2.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:

(Me) > link

(Signal bridge bot) > Unhandled error while handling command:
Traceback (most recent call last):
  File "/opt/yunohost/mautrix_signal/lib/python3.7/site-packages/mautrix/bridge/commands/handler.py", line 409, in handle
    await self._run_handler(handler, evt)
  File "/opt/yunohost/mautrix_signal/lib/python3.7/site-packages/mautrix/bridge/commands/handler.py", line 296, in __call__
    return await self._handler(evt)
  File "/opt/yunohost/mautrix_signal/lib/python3.7/site-packages/mautrix_signal/commands/auth.py", line 64, in link
    sess = await evt.bridge.signal.start_link()
  File "/opt/yunohost/mautrix_signal/lib/python3.7/site-packages/mausignald/signald.py", line 112, in start_link
    return LinkSession.deserialize(await self.request_v1("generate_linking_uri"))
  File "/opt/yunohost/mautrix_signal/lib/python3.7/site-packages/mausignald/rpc.py", line 221, in request_v1
    return await self.request(command, expected_response=command, version="v1", **data)
  File "/opt/yunohost/mautrix_signal/lib/python3.7/site-packages/mausignald/rpc.py", line 215, in request
    resp_type, resp_data = await self._raw_request(command, **data)
  File "/opt/yunohost/mautrix_signal/lib/python3.7/site-packages/mausignald/rpc.py", line 212, in _raw_request
    return await asyncio.shield(future)
mausignald.errors.ResponseError: UnsatisfiedLinkError: /tmp/resource7826374141016698858.so: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/resource7826374141016698858.so)

@MayeulC MayeulC added bug Something isn't working dependency isue We'd like to fix this, but the problem isn't ours labels Nov 15, 2021
@Gredin67
Copy link
Collaborator

Gredin67 commented Nov 15, 2021

I see 3 options:

@alexAubin
Copy link
Member

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)

@MayeulC
Copy link
Collaborator Author

MayeulC commented Nov 19, 2021

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.

@MayeulC
Copy link
Collaborator Author

MayeulC commented Nov 23, 2021

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

@MayeulC MayeulC mentioned this issue Nov 26, 2021
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working dependency isue We'd like to fix this, but the problem isn't ours
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants