Opened 3 weeks ago
Last modified 2 weeks ago
#70833 assigned defect
wezterm @20240203-110809-5046fc22: error[E0282]: type annotations needed for `Box<_>`
| Reported by: | eschnett (Erik Schnetter) | Owned by: | herbygillot (Herby Gillot) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.10.1 |
| Keywords: | sequoia | Cc: | |
| Port: | wezterm |
Description
I cannot install wezterm on Sequoia. The build aborts with an error. The relevant lines in the log file seem to be
:info:build error[E0282]: type annotations needed for `Box<_>` :info:build --> registry/src/index.crates.io-6f17d22bba15001f/time-0.3.31/src/format_description/parse/mod.rs:83:9 :info:build | :info:build 83 | let items = format_items :info:build | ^^^^^ :info:build ... :info:build 86 | Ok(items.into()) :info:build | ---- type must be known at this point :info:build | :info:build = note: this is an inference error on crate `time` caused by an API change in Rust 1.80.0; update `time` to version `>=0.3.35` by calling `cargo update`
Attachments (1)
Change History (5)
Changed 3 weeks ago by eschnett (Erik Schnetter)
| Attachment: | main.log.bz2 added |
|---|
comment:1 Changed 3 weeks ago by markemer (Mark Anderson)
comment:3 Changed 2 weeks ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | herby.gillot@… herbygillot removed |
|---|---|
| Keywords: | sequoia added |
| Owner: | set to herbygillot |
| Status: | new → assigned |
| Summary: | wezterm 20240203: Build error on Sequoia → wezterm @20240203-110809-5046fc22: error[E0282]: type annotations needed for `Box<_>` |
comment:4 Changed 2 weeks ago by markemer (Mark Anderson)
Replying to eschnett:
Can you provide the SHA?
This is what I've been building with, but there may be some newer ones out there that will work. Or maybe some older ones. This one works, though: 30345b36d8a00fed347e4df5dadd83915a7693fb
https://github.com/wez/wezterm/commit/30345b36d8a00fed347e4df5dadd83915a7693fb
Note: See
TracTickets for help on using
tickets.
I've had this problem, and I solved it but moving to the HEAD of wezterm on https://github.com/wez/wezterm - so it's an upstream problem. We may want to pick a SHA for now and build that. I have one a few commits back and it works. We could also find the upstream commit that fixes it and patch using that. The last release was Feb, so I'd hope there is a new one soon.