You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Missing tag / crates.io update for version 0.2.64 #1515
As of right now, the latest tag version is 0.2.63, but the Cargo.toml version was bumped to 0.2.64 with commit 1dd09fb. In addition, crates.io has a 0.2.63, but it has been yanked.
Could we get a 0.2.64 tag in place and update crates.io?
There are some bugs upstream that must be fixed before we can release 0.2.64. Right now, the latest usable version is 0.2.62. The 0.2.63 had a serious bug and was yanked, the tag should reflect that.
Once 0.2.64 is released, the commit that correspond to the code in that release will be tagged.
The one problem I can find with 0.2.63 was an issue with musl, and the code causing that breakage has been removed. I can't find anything else that would be blocking, but I'm not all that familiar with this crate so I don't know if there's something else.
rust-lang/rust#63649 was rolled back in rust-lang/rust#65151, but that should not block a new libc release. The Emscripten fixes in #1478 are independent of rust-lang/rust#63649 and should be rolled into rust-lang/rust as soon as possible regardless of what happens with other PRs.
As soon as bors reports all green, which is hopefully today. Last week some smaller components for the standard library were shipped, and those were missing some binary components that were required for some targets to work properly, but the fix landed on nightly today. But... the new rustup profiles also landed today, and that broke CI in different ways on some targets as well... #1550 fixes that there, and afterwards I can do a release.
Activity
gnzlbg commentedon Sep 12, 2019
There are some bugs upstream that must be fixed before we can release 0.2.64. Right now, the latest usable version is 0.2.62. The 0.2.63 had a serious bug and was yanked, the tag should reflect that.
Once 0.2.64 is released, the commit that correspond to the code in that release will be tagged.
loganwendholt commentedon Sep 12, 2019
Got it, thanks for the clarification!
loganwendholt commentedon Oct 4, 2019
Are there any specific issues / PRs related to the bugs that are blocking?
Osspial commentedon Oct 5, 2019
The one problem I can find with
0.2.63was an issue with musl, and the code causing that breakage has been removed. I can't find anything else that would be blocking, but I'm not all that familiar with this crate so I don't know if there's something else.Osspial commentedon Oct 6, 2019
Looking through the diff from
0.2.63to now, the other issue that's mentioned is rust-lang/rust#63649, but that has also been resolved.tlively commentedon Oct 8, 2019
rust-lang/rust#63649 was rolled back in rust-lang/rust#65151, but that should not block a new libc release. The Emscripten fixes in #1478 are independent of rust-lang/rust#63649 and should be rolled into rust-lang/rust as soon as possible regardless of what happens with other PRs.
newpavlov commentedon Oct 15, 2019
@gnzlbg
Any news regarding ETA for
v0.2.64release?gnzlbg commentedon Oct 15, 2019
As soon as bors reports all green, which is hopefully today. Last week some smaller components for the standard library were shipped, and those were missing some binary components that were required for some targets to work properly, but the fix landed on nightly today. But... the new rustup profiles also landed today, and that broke CI in different ways on some targets as well... #1550 fixes that there, and afterwards I can do a release.
gnzlbg commentedon Oct 15, 2019
0.2.64 has been released, please, do test and report any issues, I'll update rust-lang/rust to use this version after it has received some testing