remove xorg packages, upgrade to bookworm by this guide
bash -c “$(curl -sSfL ‘ttps://raw.githubusercontent.com/MichaIng/DietPi/master/.build/images/dietpi-installer’)”
(i removed “h” because of limitations for number of urls, it is from official guide and i can’t make it not url otherwise)
I choose Trixie
Expected behaviour:
dietpi installation
Actual behaviour:
linux-image-pine64 does not install
Extra details:
…
Additional logs:
Reading package lists...
Building dependency tree...
Reading state information...
Package linux-image-pine64 is not available, but is referred to by another packa
ge.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'linux-image-pine64' has no installation candidate
it just… worked for me. apt did not complain about debian repositories. I have issues downloading stretch image for bpi-m4, so i started from ubuntu mate. Can that influence the outcome of apt not finding linux-image-pine64 in trixie repos that dietpi script put into my sources.list?
root@bpi-iot-ros-ai:/tmp/DietPi-Installer# cat /etc/apt/sources.list
deb https://deb.debian.org/debian/ trixie main contrib non-free non-free-firmwar
e
deb https://deb.debian.org/debian/ trixie-updates main contrib non-free non-free
-firmware
deb https://deb.debian.org/debian-security trixie-security main contrib non-free
non-free-firmware
deb https://deb.debian.org/debian/ trixie-backports main contrib non-free non-fr
ee-firmware
This package does not exist in the apt repo at all.
But the BananaPi M4 uses a RK3399, so it should be linux-image-arm64 maybe? But why is it detected as Pine64? @Katie do you have more of the log before the error occured?
For my understanding of the script, it should’ve picked
You can have a look into /var/tmp/dietpi/logs.
Ubuntu loggs into the journal, but since a lot gets removed, idk if you will find anything useful about the dietpi isntallation there, but you can have a look
It’s not that we don’t want to help. But even if it works for now, who’s to say there won’t be problems in the future? And then no one will remember that it was once an Ubuntu system. Who knows? There’s a reason why we don’t support Ubuntu as a source. There is a difference between it and Debian after all.
linux-image-pine64 got autodetected by our installer as kernel package to keep. But it looks like that package is not installed anymore, just its config files which keeps it in the database.
Anyway, yes it the base image was Ubuntu, ot won’t work anyway.