-
Notifications
You must be signed in to change notification settings - Fork 930
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
sbtn 1.8.1 regression on Debian 11 with glibc 2.31 #7118
Comments
@Locke Thanks for the detailed report! I guess this could be caused by ipcsocket build (https://github.com/sbt/ipcsocket) or the GraalVM native-image build for sbtn. In general, any part of the sbt that requires native integration is somewhat finicky, and if the compatibility is not enforced by CI (often set to "ubuntu-latest") we won't notice when it slips. @mkurz Do you know if this is mostly due to whatever the glibc lying around in the Github Actions image we use to build sbtn? If so using slightly older ubuntu would restore the Debian 11 compatibility? |
https://repology.org/project/glibc/versions says Ubuntu 22.04 uses glibc 2.35, and Ubuntu 20.04 uses glibc 2.31. I'd be happy to try to downgrade the Ubuntu machine and see if this might get fixed. |
I am pretty sure that should fix the problem. You used |
Thankfully this was fairly easy to reproduce on Github Actions as well using ubuntu-20.04 - #7119 |
👍 IMHO that bug basically was more or less unavoidable, and it was just waiting till a new ipcsocket release gets cut 😉 Guess we stay on ubuntu 20.04 for a bit longer. |
Fixes sbt#7118 Problem ------- sbtn 1.8.1 was built using ubuntu-latest, which meant picking up newer glibc. Solution -------- This downgraded the ubuntu machine to build sbtn.
Fixes sbt#7118 Problem ------- sbtn 1.8.1 was built using ubuntu-latest, which meant picking up newer glibc. Solution -------- This downgraded the ubuntu machine to build sbtn.
sbt 1.8.2 is out - https://eed3si9n.com/sbt-1.8.2 |
steps
I just updated sbt on two Debian 11 ("bullseye" / "stable") x86_64 machines from 1.8.0 to 1.8.1 (a local machine and a vm used for GitHub Actions hosted-runner).
problem
On both I can no longer start sbtn and receive the following output instead.
This happens not only in a project folder which I compiled successfully just before the update, but also in a completely empty folder.
It happens with both
sbt --client
and manually downloaded sbtn.expectation
sbt and sbtn should work on Debian 11 ("bullseye" / "stable") with glibc 2.31, as this is the current supported release.
Otherwise, it has to be clearly stated somewhere (e.g. https://www.scala-sbt.org/download.html), that systems with an older glibc like Debian 11 are no longer supported.
notes
full log on a vm
after downgrading to 1.8.0, sbtn works
other systems
I manually downloaded sbt from the GitHub Release onto Debian 12 ("bookworm" / "testing", using glibc 2.36-7) on my RaspberryPI 4 (aarch64) and had no problem with the simple
clean
smoketest.The text was updated successfully, but these errors were encountered: