coreutils: release artifacts for v0.0.24 and v0.0.25 are missing
It looks like something went wrong here: https://github.com/uutils/coreutils/actions/runs/7596318857
EDIT: I’m seeing this error between a mountain of weird output:
2024-01-20T19:21:23.9087255Z [0m C:/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/12.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: C:\Users\runneradmin\.cargo\registry\src\index.crates.io-6f17d22bba15001f\windows_x86_64_gnu-0.42.2\lib/libwindows.a(ntdll_dll_s00082.o): illegal symbol index -1869611008 in relocs
Pipeline is green now but release artifacts are still missing.
About this issue
- Original URL
- State: closed
- Created 5 months ago
- Comments: 15 (12 by maintainers)
I took a step to hopefully fix this: https://github.com/uutils/coreutils/pull/6181
I’m of the opinion that we shouldn’t generate artifacts for the old releases. uutils is too unstable to be concerned with that in my opinion. We’ll experiment with fixing this with pre-releases for 0.0.26 instead of making a real release right away, so that we won’t have more proper releases without artifacts. Once it works, we release 0.0.26 and everybody can be happy again.
With #5694 (which is in 0.0.24), I was trying to get a larger set of statically linked release artifacts. I need this for another PR in another repo which depends on those binary artifacts: https://github.com/aspect-build/bazel-lib/pull/706
But I also totally understand if you prefer to just wait until the next release.
See also: https://github.com/uutils/coreutils/discussions/5915
@cakebaker seems to just have triggered a rerun of the actions. Hopefully that’ll fix it.