Open EHJ-52n opened 2 months ago
Are you using the "fat binary" from github releases downloads?
Or how did you install borg 1.4.0?
I am downloading the following file from github:
https://github.com/borgbackup/borg/releases/download/$(borg_latest)/borg-linux-glibc236
borg_latest
requests the latest version from the github API via
curl --silent "https://api.github.com/repos/borgbackup/borg/releases/latest" | jq -r .tag_name | sed 's/v\(.*\)/\1/'
Ubuntu 22.04 has libc 2.35. Ubuntu 24.04 has libc 2.39.
You should use a borg binary built for libc <= 2.35.
We offer one for 2.31, so use that one, not the 2.36 one.
TODO: check if docs / FAQ / 00_README.txt needs more info about this.
Switching to the borg binary with libc 2.31 is not showing the error anymore.
What about extending the --version
output to include the used libc version?
@EHJ-52n Not sure if I can easily query that (also considering that borg is multi-platform).
But you can easily use your package manager and search for "libc" (not: "libc++") or so there.
Reopening for the TODO.
Show the package version of libc on apt based systems, here ubuntu:
~ apt-cache policy libc6 | grep Installed | awk '{print $2}'
2.35-0ubuntu3.8
Have you checked borgbackup docs, FAQ, and open GitHub issues?
Yes
Is this a BUG / ISSUE report or a QUESTION?
Issue or Question - unclear atm
System information
Your borg version (borg -V).
1.4.0
Operating system (distribution) and version.
Ubuntu 22.04.4 LTS
withPython 3.10.12
withpython3-msgpack 1.0.3-1build1
Hardware / network configuration, and filesystems used.
Lenovo ThinkPad P14s Gen 3
How much data is handled by borg?
Full borg commandline that lead to the problem (leave away excludes and passwords)
Describe the problem you're observing.
I tried to check the msgpack implementation by myself, and it seems to be the fast version, hence, I am unclear, why borg is using the pure python implementation.
See https://github.com/borgbackup/borg/blob/1.4-maint/src/borg/helpers/msgpack.py#L131-L134
Can you reproduce the problem? If so, describe how. If not, describe troubleshooting steps you took before opening the issue.
The "issue" is reproducible and the "pure-python msgpack" statement is always logged.
Include any warning/errors/backtraces from the system logs
There are none.
Do you need any additional information from my side?
Is there anything, I can install on ubuntu, to get rid of this message and use a fast msgpack implementation?