Arch Linux

Noneuclidery

Member

Registered: 2025-06-22

Posts: 1

Trying to figure out "clean chroot"

I'm trying to get taskchampion-sync-server from the AUR, but the build fails.

I was told it works on a "clean chroot", so I went off to learn what that was. But a few things confused me.

First, the error in question was

error[E0282]: type annotations needed for `Box<_>`
  --> /home/username/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/time-0.3.20/src/format_description/parse/mod.rs:83:9
   |
83 |     let items = format_items
   |         ^^^^^
...
86 |     Ok(items.into())
   |              ---- type must be known at this point
   |
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`

...

For more information about this error, try `rustc --explain E0282`.

I never installed rust until now, so this being out of date seems like something simply having a clean workspace wouldn't solve.

Second... I still get the same error. I may be messing this up, but I still don't know enough to tell if I'm misunderstanding something. If I understand correctly, running

paru --chroot -S taskchampion-sync-server

should run in a clean workspace. If it is, then am I doing something *else* wrong? But if it isn't, then there's something I'm not understanding about how chroot works, right?

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 14,967

Re: Trying to figure out "clean chroot"

No idea how good the --chroot option of paru works .

https://wiki.archlinux.org/title/Develo … ean_chroot are the supported methods to use chroot on archlinux .

The convenience way is the easiest one to get working .

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky