You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m not sure where to put this as it’s not a bug, nor a compilation error.
When building eza v0.18.11 with cargo with cargo, I’m getting warnings.
I am in a local git repo, in detached head on the commit corresponding to the tag v0.18.11.
❯ git switch -d v0.18.11
Previous HEAD position was 75f1f8cf chore: release eza v0.18.10
HEAD is now at 99562e3a chore: release eza v0.18.11
❯ cargo install --path .
Installing eza v0.18.11 (/root/eza)
Updating crates.io index
[OMITTED FOR BREVITY]
Compiling git2 v0.18.3
warning: use of deprecated associated function `chrono::NaiveDateTime::from_timestamp_opt`: use `DateTime::from_timestamp` instead
--> src/fs/file.rs:740:24
|
740 | NaiveDateTime::from_timestamp_opt(self.metadata.ctime(), self.metadata.ctime_nsec() as u32)
| ^^^^^^^^^^^^^^^^^^
|
= note: `#[warn(deprecated)]` on by default
warning: `eza` (lib) generated 1 warning
warning: unused imports: `DisplayWidth`, `TextCellContents`, `TextCell`
--> src/output/mod.rs:2:22
|
2 | pub use self::cell::{DisplayWidth, TextCell, TextCellContents};
| ^^^^^^^^^^^^ ^^^^^^^^ ^^^^^^^^^^^^^^^^
|
note: the lint level is defined here
--> src/main.rs:7:9
|
7 | #![warn(unused)]
| ^^^^^^
= note: `#[warn(unused_imports)]` implied by `#[warn(unused)]`
^[warning: `eza` (bin "eza") generated 2 warnings (1 duplicate) (run `cargo fix --bin "eza"` to apply 1 suggestion)
Finished release [optimized] target(s) in 7m 35s
Replacing /root/.cargo/bin/eza
Replaced package `eza v0.18.10 (/root/eza)` with `eza v0.18.11 (/root/eza)` (executable `eza`)
The text was updated successfully, but these errors were encountered:
I’m not sure where to put this as it’s not a bug, nor a compilation error.
When building eza v0.18.11 with cargo with cargo, I’m getting warnings.
I am in a local git repo, in detached head on the commit corresponding to the tag v0.18.11.
The text was updated successfully, but these errors were encountered: