Panic when attempting to adopt /etc/crontab

[MaddyGuthridge]

When I try to adopt my server's crontab, tuckr panics.

| maddy@ursula :: ~/.dotfiles/Configs/ursula/^etc (main) ⚡
⋙   RUST_BACKTRACE=1 tuckr add -a ursula
Are you sure you want to adopt conflicts? (N/y) y

thread 'main' panicked at /home/maddy/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/tuckr-0.11.2/src/symlinks.rs:643:65:
called `Result::unwrap()` on an `Err` value: Os { code: 2, kind: NotFound, message: "No such file or directory" }
stack backtrace:
   0: __rustc::rust_begin_unwind
   1: core::panicking::panic_fmt
   2: core::result::unwrap_failed
   3: tuckr::symlinks::add_cmd::{{closure}}::{{closure}}
   4: tuckr::symlinks::add_cmd
   5: tuckr::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
| maddy@ursula :: ~/.dotfiles/Configs/ursula/^etc (main) ⚡
⋙   ls                                                                                           ⏎
crontab
| maddy@ursula :: ~/.dotfiles/Configs/ursula/^etc (main) ⚡
⋙   ls /etc/crontab
/etc/crontab

I may have a mistake somewhere (likely something to do with the file being owned by root), but even then, I'd expect tuckr to handle the error gracefully and give a detailed and helpful error message.

[RaphGL]

Dotfiles targeting the root is still very new so not everything has been ironed out yet. If you're attempting to mess with files that are owned by root, it will simply not work. Either because you don't have the permissions necessary to modify the file or because if you run as root your user's home directory changes and I can't detect where it should actually be.

I have an issue related to that here: #73

[RaphGL]

I have some major ish refactor coming up that will change how I track symlink status internally and right after I will release 0.12.0, so this issue will have to wait for the next version to be fixed. What I can do for now is try and spot where and why this is happening and attempt to leave a temporary error telling the user why this is not possible currently.

[MaddyGuthridge]

Let me know if there's anything I can do to help! I've been hunting for a Rust project to sink my teeth into, so if there are any issues you don't have the time or energy for, I'd love to give them a shot :)

[RaphGL]

You can try and start with one of these:

• Make tuckr push be able to use ^ prefix with root targeting dotfiles #74
• Show what groups are not available in the current platform with status <group> #83

Once you're comfortable, you can try one of these if you still feel up to it:

• Improve Secrets security #35
  The secrets functionality has been massively overlooked because I just consider hooks and configs much more important and I personally don't use secrets all that much.
  Someone started updating it (Replaced the encryption with age #67) but nothing substantial has been done with it since I introduced it.

• Adding shell autocompletion:
  I haven't had the time or disposition to provide a good autocompletion experience yet, ik that clap-complete exists and that you can generate autocompletions with it but last I tried I couldn't get the groups to be autocompleted, so I tried writing the completions manually but the docs were very sparse so I gave up.

• Figure out how to handle root targeting:
  Escalate user privileges for root targeted dotfiles #73

Feel free to ask any questions in case you need it.