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 assume i'm doing something wrong here. But all of the packages seem to be pinned to the version they were originally installed at. Take cargo for example:
trent@athena:~$ cargo version
Command 'cargo' not found, but can be installed with:
sudo snap install rustup # version 1.27.1, or
sudo apt install cargo # version 1.75.0+dfsg0ubuntu1~bpo0-0ubuntu0.22.04
See 'snap info rustup' for additional versions.
trent@athena:~$
trent@athena:~$ # no install on base machine
trent@athena:~$ cargo version
Command 'cargo' not found, but can be installed with:
sudo snap install rustup # version 1.27.1, or
sudo apt install cargo # version 1.75.0+dfsg0ubuntu1~bpo0-0ubuntu0.22.04
See 'snap info rustup' for additional versions.
trent@athena:~$ devbox search cargo
Found 49+ results for "cargo":
* cargo (1.78.0, 1.77.2, 1.77.1, 1.76.0, 1.75.0, 1.74.0, 1.73.0, 1.72.1, 1.72.0, 1.71.1 ...)
* cargo-about (0.6.2, 0.6.1, 0.6.0, 0.5.7, 0.5.6, 0.5.5, 0.5.4, 0.5.3, 0.5.2, 0.5.1 ...)
* cargo-apk (0.9.6)
* cargo-asm (2019-12-24)
* cargo-audit (0.20.0, 0.19.0, 0.18.3, 0.18.2, 0.18.1, 0.17.6, 0.17.5, 0.17.4, 0.17.3, 0.17.2 ...)
* cargo-auditable (0.6.2, 0.6.1, 0.6.0, 0.5.5, 0.5.4, 0.5.3, 0.5.2, 0.5.1)
* cargo-autoinherit (0.1.5, 0.1.4)
* cargo-bazel (0.8.0)
* cargo-benchcmp (0.4.4)
* cargo-binstall (1.6.9, 1.6.8, 1.6.7, 1.6.6, 1.6.5, 1.6.4, 1.6.3, 1.6.2, 1.6.1, 1.5.0 ...)
Warning: Showing top 10 results and truncated versions. Use --show-all to show all.
trent@athena:~$ #latest version is 1.78.0
trent@athena:~$ devbox update cargo
Info: Already up-to-date cargo@latest 1.78.0
Info: Installing the following packages to the nix store: go@latest, cargo@latest, python@latest, bun@latest, nodejs@latest, gh@latest, vim@latest, tmux@latest, wget@latest, nmap@latest, xxd@latest, jq@latest, yq-go@latest, pngcheck@latest, steghide@latest, htop@latest, btop@latest, zsh@latest, thc-hydra@latest, john@latest, hashcat@latest, binwalk@latest, gobuster@latest, wfuzz@latest, medusa@latest, dislocker@latest, aircrack-ng@latest, exifprobe@latest, masscan@latest, kubectl@latest, krew@latest, helm@latest, podman@latest, podman-compose@latest, podman-tui@latest, opentofu@latest, awscli2@latest, azure-cli@latest, google-cloud-sdk@latest
Info: Running "nix flake update"
trent@athena:~$ # devbox states package is up to date
trent@athena:~$ # enter devbox
trent@athena:~$ dev
Starting a devbox shell...
(.venv) (devbox) trent@athena:~$ cargo version
cargo 1.76.0
(.venv) (devbox) trent@athena:~$ # 1.76.0 != 1.78.0
Cargo isn't the only package - it is in fact all of the packages in my devbox env. looking at my devbox.lock I can also see that it has the 1.78 version set.
What happened?
I assume i'm doing something wrong here. But all of the packages seem to be pinned to the version they were originally installed at. Take
cargo
for example:Cargo isn't the only package - it is in fact all of the packages in my devbox env. looking at my
devbox.lock
I can also see that it has the 1.78 version set.wondering what else I can try besides nuking and redeploying. Maybe im missing something obvious?
Thanks.
Steps to reproduce
devbox update
Command
No response
devbox.json
Devbox version
0.12.0
Nix version
nix (Nix) 2.23.3
What system does this bug occur on?
Linux (x86-64)
Debug logs
No response
The text was updated successfully, but these errors were encountered: