#273 1.0.0-alpha fails to build from source on Fedora 33 (1.0.0-alpha.35 is fine)
Fedora 33 (which is the latest version of Fedora) has this Rust version:
rustc --version
rustc 1.49.0
Thanks! This seems to come from another bad practice than not having “standard” CIs:
- I worked so hard on the 1.0 version, rewriting everything from scratch, that I couldn’t call it anything other than 1.0. In hindsight, this wasn’t quite reasonable. Would I do it again? Maybe: calling it 1.0-alpha attracted a lot more feedback than I hoped, and a lot more than I ever got on all previous versions. Also, I released that version immediately after “almost” stabilising all the formats, meaning immediately after Pijul was bootstrapped again.
- The Semver specification, which Cargo is following, mandates that all versions named 1.0.0-alpha.xx be compatible.
- Unfortunately, because Libpijul and Pijul moved a lot in the last two months, none of them are compatible, and only the last one of each is guaranteed to work with the other.
In your case, the path /home/edwin/.cargo/registry/src/github.com-1ecc6299db9ec823/pijul-1.0.0-alpha seems to be from an old version of Pijul, and doing cargo install --version 1.0.0-alpha.36 would probably work better.
As for the CI, I’m not super happy with the current CI on the Nest:
- We don’t have tags yet (this is currently my main mission in Pijul)
- It is based on Nix, which means that it’s really fast and doesn’t have to recompile stuff all the time. But it also means that the build process isn’t completely “natural”, in the sense that it doesn’t follow what Cargo does.
If the command I suggested doesn’t work, I’m super interested in your report!
Thanks, explicitly running cargo install pijul --version 1.0.0-alpha.36 worked.
Although cargo install pijul --version 1.0.0-alpha still fails (even after wiping ~/.cargo), I think it is installing something very old:
https://crates.io/crates/pijul/1.0.0-alpha
Could you update the instructions on https://pijul.org/downloads/ to say to install 1.0.0-alpha.36?
I would’ve assumed that when you ask it to install 1.0.0-alpha it’ll install 1.0.0-alpha.36, but they are in fact separate versions.
I’ve read https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html Here is another possibility (that doesn’t require updating the docs every time you release a new alpha):
cargo install pijul --version '~1.0.0-alpha'
If you change https://pijul.org/downloads/ to suggest that then it wouldn’ try to install an outdated 1.0.0-alpha but go straight to trying to install the latest, which is 1.0.0-alpha.36 at the moment.
Also failed to use cargo instal ....alpha command without alpha number.
No problem upgrade from crates from alpha.31 to latest alpha.36 on Fedora Rawhide.
@tankf33der see ‘Fedora Updates’ on Fedora 33, it has rustc 1.49.
cargo install pijulfails due to missing dependency (it tries to install 0.12.2). https://pijul.org/downloads/ says to usecargo install pijul --version 1.0.0-alpha, but that fails (it tries to install 1.0.0-alpha.36)Workaround:
cargo install pijul --version 1.0.0-alpha.35As you approach 1.0 I’d suggest you set up a CI, so that the alpha (and final) versions are always buildable.