Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign up1.1.15b1 testing #5414
1.1.15b1 testing #5414
Comments
|
We've decided to build the ARM binaries for alpha and beta versions too You can find them at https://borg.bauerj.eu/?show-unstable I'll be updating the build system to also include all 1.2.* alpha builds. |
|
Hi, I would like to work on this issue. Is there anything else I would need to know before starting the testing? |
|
pyinstaller/pyinstaller#2357 see the last comment there, maybe test that, too. Guess this might be interesting in the context of |
|
@mmarinez well, the biggest change is about how the binary is built / the glibc it is built for / the python version it bundles/uses, so guess testing should address primarily that. |
For macOS I'm currently using the develop branch of PyInstaller due to this issue, which needs a bootloader with newer With this setup I didn't see any issue when calling Maybe the linked issue is related to Linux or to single binary Pyinstaller executables. For Vorta and Borg on macOS we only use single directory binaries to get around macOS signing issues. |
I made a new release 1.1.15b1 for testing, see there:
https://github.com/borgbackup/borg/releases/tag/1.1.15b1
As you see, the borg code is pretty much the same as in 1.1.14, but especially the binary building got some updates. Thus, primarily the binaries should get some testing, to find issues before I make the final 1.1.15 release later this year.
As they were made on debian stretch with libc 2.24, they will require a libc compatible to that.
The binary not working on linux dists with incompatible libc versions is expected.
Note: In 1.1.14 and before, binaries were built on debian jessie with libc 2.19.
This issue is about general feedback, there is also #5402 about performance and resource usage, please give such feedback there.