-
Notifications
You must be signed in to change notification settings - Fork 2.7k
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Zed Preview 0.153.6 Remote Requiress GLIBC 2.35 #18088
Comments
See #17643 for more context: GitHub removed all Linux ARM runners with Ubuntu 20 and we cannot ship binaries with older libc that easy anymore. Ubuntu 20.04 EOL is 23 April 2025n which is ~6 months so it makes not much sense for us to keep something more complex in CI for 6 months only. |
Thanks for the reply! This is an x86 based system, which I'm unfortunately going to be stuck using for the next 6 months 😅. But I imagine that note in the linked issue about the new 2.35 requirement is what's catching me here. Any insight into if getting around this problem by building on a more up to date system and statically linking to musl would cause more trouble than it's worth? |
The note in the 0.152.3 changelog reflect the move Ubuntu 22.04 for the ARM runners was correct. Separately this week we moved our Linux x86 runners to Ubuntu 22.04 in d3d3a09 which included some changes to our CI infrastructure as part of: This was unintentionally missing from the Release Notes in today's releases of Preview/Stable. I've updated the v0.153.6 v0.154.0-pre changelogs to include this change. |
Check for existing issues
Describe the bug / provide steps to reproduce it
When using the latest nightly zed on an ubuntu 20.04 system I see the following error reported by my local Zed instance.
On previous versions of nightly I was able to use the remote development feature without issue.
Environment
On remote system
If applicable, add mockups / screenshots to help explain present your vision of the feature
No response
If applicable, attach your Zed.log file to this issue.
Zed.log
The text was updated successfully, but these errors were encountered: