Renamed lints in 1.27 beta

[pietroalbini]

Please note it's unlikely this change will be reverted before the release.
This issue exists mostly to notify crate authors about the change.

In the next release of Rust, 1.27.0, a few lints will be renamed to be consistent with the other names and RFC 344. You can find the full rationale for the change and the list of changed lints in PR #50879.

Your crates have #[deny(warnings)] in the build, so the change broke their build. If you want to allow the lint while still supporting old compilers you can use:

#![allow(unknown_lints, renamed_and_removed_lints, old_lint, new_lint)]

• elastic regressed from stable to beta (build log) cc @KodrAus
• itm regressed from stable to beta (build log) cc @japaric
• libjwt regressed from stable to beta (build log) cc @lightdiscord
• libpasta regressed from stable to beta (build log) cc @samscott89
• mqtt regressed from stable to beta (build log) cc @flier
• sherpa regressed from stable to beta (build log) cc @mikeastock
• slack-hook regressed from stable to beta (build log) cc @compressed
• sudo_plugin regressed from stable to beta (build log) cc @stouset
• ptx-builder regressed from stable to beta (build log) cc @denzp
• serde_qs regressed from stable to beta (build log) cc @samscott89
• japaric/itm (GitHub repo) regressed from stable to beta (build log) cc @japaric

[petrochenkov]

The root reason for all the regressions is actually error-chain, so everything will be fixed if rust-lang-deprecated/error-chain#247 is merged and minor version of error-chain is released.

Does anybody know who currently has rights in that repo? @Yamakaky and @brson seem to be unavailable.

[est31]

Does anybody know who currently has rights in that repo? @Yamakaky and @brson seem to be unavailable.

What matters far more than git access is who has crates.io access which according to the crates.io page is @alexcrichton @Yamakaky and @brson . Not sure how alex can be reached before the 1.27 release is out.

[Dylan-DPC-zz]

Not sure how alex can be reached before the 1.27 release is out.

This is why we created the Rust Bus Organisation. In such emergency cases, we can push releases on the owner's behalf.

[KodrAus]

In my opinion, this is the kind of thing that can happen with #[deny(warnings)], and while fixing it would be nice in the meantime there's also the solution of not denying warnings. I don't think it's worth bothering Alex over.

[Yamakaky]

To be honest, I'm not really programming in rust these time (following the news though),so I kinda left error-chain behind. failure being there, I'm not sure it's worth it to maintain error-chain.

[pietroalbini]

@Yamakaky 1.27 release is next week, if you have time to cut out a new error-chain release it would be awesome!