`just --unstable reset-bazzite-arch` iirc does the same thing
just --unstable reset-bazzite-arch iirc does the same thing
Ti hope you have the justfiles
Wgive this a shot if the other command doesn't work I think
MI have no idea
MI'll try this
Tyou will know if both commands that both @wangjangler. and i just said dont work 
Mjust --unstable reset-bazzite-arch iirc
error: The argument '--unstable' was provided more than once, but cannot be used multiple times
USAGE:
just --color <COLOR> --dump-format <FORMAT> --unstable
For more information try --help
[normand64@Normand64 .var]$
hmmmm
error: The argument '--unstable' was provided more than once, but cannot be used multiple times
USAGE:
just --color <COLOR> --dump-format <FORMAT> --unstable
For more information try --help
[normand64@Normand64 .var]$
hmmmm
Tok forget the unstable flag
Ttry it without that
T
M[normand64@Normand64 .var]$ just --unstable install-bazzite-arch
error: The argument '--unstable' was provided more than once, but cannot be used multiple times
USAGE:
just --color <COLOR> --dump-format <FORMAT> --unstable
For more information try --help
[normand64@Normand64 .var]$
same thing with the other version
error: The argument '--unstable' was provided more than once, but cannot be used multiple times
USAGE:
just --color <COLOR> --dump-format <FORMAT> --unstable
For more information try --help
[normand64@Normand64 .var]$
same thing with the other version
Tsame thing
just reset-bazzite-archTat least just is installed lol
M[normand64@Normand64 .var]$ just reset-bazzite-arch
error: Justfile does not contain recipe
[normand64@Normand64 .var]$
error: Justfile does not contain recipe
reset-bazzite-arch.[normand64@Normand64 .var]$
Tyeah i figured this was happening ...
Mmaybe I don't have the just files
Tonce you said bazzite portal wasnt working
Tyeah you dont
Thold on
Jare you up to date?
Mnot sure the updates happen too frequently so I ignore them.
Tyeah try
rpm-ostree updateyeah you'll need to be more aggressive on the updates
M[normand64@Normand64 .var]$ rpm-ostree update
Pulling manifest: ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:38
Importing: ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:38 (digest: sha256:58e5521a6ab890e106f9b21a0f44625c82cdde5052db80a4d140883eacaf4379)
ostree chunk layers already present: 53
ostree chunk layers needed: 12 (662.6 MB)
custom layers needed: 4 (1.5 GB)
not sure if it's still processing.
Pulling manifest: ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:38
Importing: ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia:38 (digest: sha256:58e5521a6ab890e106f9b21a0f44625c82cdde5052db80a4d140883eacaf4379)
ostree chunk layers already present: 53
ostree chunk layers needed: 12 (662.6 MB)
custom layers needed: 4 (1.5 GB)
not sure if it's still processing.
MI'll be right back.
Jyeah that'll take a bit
Tgood to know that there is an update so just sit tight
Wyeah it just silently updates
MSo what do I do to get the just files back?
Mrpm-md repo 'updates-archive'; generated: 2023-09-23T02:26:21Z solvables: 38222
Resolving dependencies... done
Will download: 1 package (158.6 kB)
Downloading from 'copr:copr.fedorainfracloud.org:kylegospo:oversteer'... done
Importing packages... done
Relabeling... done
Checking out packages... done
Running pre scripts... done
Running post scripts... done
Running posttrans scripts... done
Writing rpmdb... done
Writing OSTree commit... done
Staging deployment... done
Freed: 492.6 MB (pkgcache branches: 0)
Upgraded:
container-selinux 2:2.221.1-1.fc38 -> 2:2.222.0-1.fc38
gstreamer1 1.22.5-1.fc38 -> 1.22.6-1.fc38
oversteer 0.0.git.316.bf27c8ba-1.fc38 -> 0.0.git.319.86040501-1.fc38
oversteer-udev 0.0.git.317.579bab90-1.fc38 -> 0.0.git.319.86040501-1.fc38
pipewire-codec-aptx 0.3.79-1.fc38 -> 0.3.80-1.fc38
ublue-os-just 0.3-1.fc38 -> 0.4-1.fc38
zip 3.0-36.fc38 -> 3.0-37.fc38
Run "systemctl reboot" to start a reboot
Oh. Looks like the thing finished when I went to check on laundry.
Resolving dependencies... done
Will download: 1 package (158.6 kB)
Downloading from 'copr:copr.fedorainfracloud.org:kylegospo:oversteer'... done
Importing packages... done
Relabeling... done
Checking out packages... done
Running pre scripts... done
Running post scripts... done
Running posttrans scripts... done
Writing rpmdb... done
Writing OSTree commit... done
Staging deployment... done
Freed: 492.6 MB (pkgcache branches: 0)
Upgraded:
container-selinux 2:2.221.1-1.fc38 -> 2:2.222.0-1.fc38
gstreamer1 1.22.5-1.fc38 -> 1.22.6-1.fc38
oversteer 0.0.git.316.bf27c8ba-1.fc38 -> 0.0.git.319.86040501-1.fc38
oversteer-udev 0.0.git.317.579bab90-1.fc38 -> 0.0.git.319.86040501-1.fc38
pipewire-codec-aptx 0.3.79-1.fc38 -> 0.3.80-1.fc38
ublue-os-just 0.3-1.fc38 -> 0.4-1.fc38
zip 3.0-36.fc38 -> 3.0-37.fc38
Run "systemctl reboot" to start a reboot
Oh. Looks like the thing finished when I went to check on laundry.
Treboot
Tthen hopefully the justfiles are back
MLooks like I gotta do a reboot. So I'll be back and let you know if I see anything different.
MComputer is fine but the bad news is I still don't have Bazzite arch yet. I suppose that is only for providing the Just Files?
Tyup
Thopefully you have the justfiles now
Ttry the previous commands
MI'll give it try.
Moh wait! Should I do this one first?
Tif you do it'll probably just say you're up to date lol
Twould try
just reset-bazzite-archMgotchya nevermind
MOk
Tim not sure if it actually needs
--unstableMBefore I do what exactly is reset arch gonna do? It's not going to reset the whole computer right?
Tno
MThank god!
Tit just deletes the old container, if there, and pulls the newest bazzite-arch image
Moh and the current terminal is under .var]$ and my hostname is that fine?
Tyeah it should be fine
