Overview
Request 561774 accepted
- Created by luke_nukem
- In state accepted
Request History
luke_nukem created request
factory-auto added opensuse-review-team as a reviewer
Please review sources
factory-auto added repo-checker as a reviewer
Please review build success
factory-auto accepted review
Check script succeeded
Output of check script (non-fatal):
Unknown license 'MIT or Apache-2.0'
Unknown license 'MIT or Apache-2.0'
jengelh accepted review
staging-bot set openSUSE:Factory:Staging:G as a staging project
Being evaluated by staging project "openSUSE:Factory:Staging:G"
staging-bot accepted review
Picked openSUSE:Factory:Staging:G
licensedigger accepted review
ok
repo-checker accepted review
cycle and install check passed
dimstar_suse accepted review
ready to accept
dimstar_suse approved review
ready to accept
dimstar_suse accepted request
Accept to openSUSE:Factory
The cargo package we have (and the ine submitted) are nit compatible with this rust version (buildrequires rust <= 1.21.1)
Err 1.22.1
Incoming - I may change it to require a version such as >= current since cargo usually builds with n-1 version okay.
Seems MozillaFirefox is not happy with this version of rust:
https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:G:DVD/MozillaFirefox/standard/x86_64
@wrosenauer
No definitely not to do with the Rust compiler, that's an issue with that release of Firefox. Seems they've turned on the equivalent of warnings == error.
"#![deny(warnings)]" So, either patch to remove "use std::ascii::AsciiExt;" from servo/components/style/gecko_string_cache/mod.rs (line 16).
I'd assume rust to behave slightly different and/or having new warnings/errors raised.
Keep in mind that the same version of Firefox is currently in TW and builds with the previous version of rust.
this of course does not mean rust is at fault, but it IS exposed by the new rust version
I'll check upstream as I would expect mozilla codebase pretty up to date with latest rust. Probably a fix from head can be backported.
Yes, of course - I need to remind myself to investigate next time, not make a snap judgment based on what I've seen previously (especially for breakage from new versions)
https://build.opensuse.org/request/show/563240 should hopefully fix the breakage. The problem is indeed change in rust. The fact that it is an error instead of the default warning is a different story. https://blog.rust-lang.org/2018/01/04/Rust-1.23.html
Ah, I completely forgot I'd seen the Ascii change. Sorry, I should have picked up on it sooner.