-
Notifications
You must be signed in to change notification settings - Fork 55
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
install-deps.pl fails to build libsodium with gcc 11.2.1 #1114
Comments
I think this is now causing See the action and a specific run: https://github.com/matrix-org/sytest/runs/4091959405?check_suite_focus=true#step:5:4467 |
I'm guessing this happened after https://tracker.debian.org/news/1272843/gcc-defaults-1194-migrated-to-testing/ (the timing seems about right) |
Indeed:
|
I think we need to migrate away from Crypt::NaCl::Sodium, which seems to be abandonware. https://metacpan.org/pod/Crypt::Ed25519 seems to be a good alternative, however to be able to drop Crypt::NaCl::Sodium altogether we need our dependencies (in particular Protocol::Matrix) to also drop it. To that end, I've filed https://rt.cpan.org/Public/Bug/Display.html?id=140079. |
This marks the `testing` image as experimental and allows the builds of the stable images to continue even if the experimental ones fail. It's nice to know when something in `testing` will break CI for a future Debian version, but it probably shouldn't stop us from successfully building existing images based on the stable distributions. (Related to #1114)
looks like @leonerd doesn't have time to update |
First we vendor in `Protocol::Matrix`. Then we patch it to use `Crypt::Ed25519` instead of `Crypt::NaCl::Sodium`. Then we switch the rest of sytest to use `Crypt::Ed25519`. Hopefully fixes #1114, and generally makes sytest a whole lot easier to install.
Describe the bug
Unable to install sytest's perl dependencies following step 3 in README.md.
To Reproduce
./install-deps.pl
Gory details
Expected behavior
Successful installation.
Desktop (please complete the following information):
Additional context
Discussed in various places:
GCC's behaviour apparently changed with https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=50bc94898fac1bd9cc1dabf227208fb5d369c4c4
The text was updated successfully, but these errors were encountered: