Closed nominolo closed 7 years ago
Oh, it's maybe worth mentioning that gfx_gl v0.3.1
uses:
[[package]]
name = "gfx_gl"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
dependencies = [
"gl_generator 0.5.5 (registry+https://github.com/rust-lang/crates.io-index)",
]
khronos_api
should have been bumped from 1.0.1
to 2.0.0
because the 1.0.1
and 1.1.0
are compatible (http://doc.crates.io/specifying-dependencies.html#caret-requirements).
The gl_generator
dependency should be also changed to ~2.0
to avoid future sem ver issues imo.
It's more that gl_generator should have a dependency on khronos_api <= 1.0
so that 1.1
wouldn't get picked.
Oh fun. Should we yank 1.1.0
then?
Ok, I've yanked the following crates:
khronos_api:1.1.0
gl_generator:0.6.0
gl:0.6.4
We'll need to publish a new version of khronos_api
with the major version bumped.
A reminder that yanking these versions will still allow the previously applied hacks to continue to work, but will ensure that future folks don't run into the same problem!
There was no need to yank these crates. Gl_generator 0.6 actually contains the fix for the problem.
Khronos_api 1.1 was correct as well.
Oh yeah - if I just yanked khronos_api
it would have been fine. Still would have needed to bump the versions to khronos_api = 2.0.0
though, and would have needed to republish. 🤔 Well - it's done now!
When I installed
ggez v0.3.3
today (5 Nov 2017) it failed to buildgfx_gl v0.3.1
:Since this was working a week ago I compared the
Cargo.lock
files andkhronos_api
was the most likely candidate, so I tried downgrading tov1.0.1
which fixed the issue. So I assume that was indeed the issue.I don't know if this is a macOS-specific issue. To reproduce, just create
cargo --bin new
and add this to yourCargo.toml
:My current work-around is to just add:
Attached
Cargo.lock
files (I needed to add.txt
to make Github happy). Cargo.lock.borken.txt Cargo.lock.txt