I have dietpi PC 9.11.2 and wanted to update but i cant. It give me error and say retry to retry rerun the last command that failed.
and i try to retry but keeps fail.
it say something 404 not found and an ip adress 195.135… something
what can I do to fix this or do I have to reflash an SD card.
[ INFO ] DietPi-Update | APT update, please wait...
Hit:1 https://deb.debian.org/debian bookworm InRelease
Hit:2 https://deb.debian.org/debian bookworm-updates InRelease
Hit:3 https://deb.debian.org/debian-security bookworm-security InRelease
Hit:4 https://deb.debian.org/debian bookworm-backports InRelease
Ign:5 http://download.opensuse.org/repositories/home:/pragmalin/Debian_10 InRelease
Err:6 http://download.opensuse.org/repositories/home:/pragmalin/Debian_10 Release
404 Not Found [IP: 195.135.....]
Hit:7 https://dietpi.com/apt bookworm InRelease
Reading package lists...
E: The repository 'http://download.opensuse.org/repositories/home:/pragmalin/Debian_10 Release' does not have a Release file.
[FAILED] DietPi-Update | APT update
- Command: apt-get -y -eany update
[FAILED] DietPi-Update | Unable to continue, DietPi-Update will now terminate.
Debian 10 means Debian Buster, but your other lists show that you are using Bookworm, 2 versions newer. Try this:
sed -i 's/Debian_10/Debian_12/' /etc/apt/sources.list.d/*.list
Then dietpi-update should work again.
Is there a particular reason you added this repository? It seems to provide rpi-imager only, but a very outdated version. Latest is v1.9.4, while the repo ships v1.7.5. If you use the Raspberry Pi Imager, better download a recent package from RPi website:
cd /tmp
wget https://downloads.raspberrypi.org/imager/imager_latest_amd64.deb
apt install ./imager_latest_amd64.deb
So unless there is another good reason to keep that repo, I would just remove it:
grep -r pragmalin /etc/apt/sources.list.d
This print the file which contains the repo. Just remove it. There should be a related key as well, either in /etc/apt/trusted.gpg.d, or /etc/apt/trusted.gpg itself. Since you otherwise use Debian and DietPi repos only, you can remove /etc/apt/trusted.gpg in any case, if it exists.
when I run dietpi-update
Im not good at all on linux and dietpi.
it just sit there for my plex.
but I relise I need to learn more.
but at the moment I really sux on this kind of stuff
it still give me this
as already mentioned by @MichaIng, it is better to remove this repository as it contains a very old version of RPI imager. If it is really needed, you should go with the official source and use the current version Releases · raspberrypi/rpi-imager · GitHub
but the sed line does not do anything. or at least i dont see it do anything.
and after do that line the repo is still there.
or is there another way to remove the repo
when run sudo nano /etc/apt/sources.list
this is in there
GNU nano 7.2 /etc/apt/sources.list
deb https://deb.debian.org/debian/ bookworm main contrib non-free non-free-firm>
deb https://deb.debian.org/debian/ bookworm-updates main contrib non-free non-f>
deb https://deb.debian.org/debian-security/ bookworm-security main contrib non->
deb https://deb.debian.org/debian/ bookworm-backports main contrib non-free non>
yes it seems to work now.
thanks both of you. and sorry for me being little slow to understand stuff.
but again thanks
I really appreciate the help I get from here
However, really no point to keep a random someone’s repo to keep certain software up-to-date, if the repo is not kept up-to-date with software releases.
General take when adding any new repository to /etc/apt/sources.list.d:
Take care to keep it updated when upgrading your Debian version. The path was Debian_10, which is Debian Buster, but you upgraded to Debian 12 Bookworm in the meantime, so it does not match anymore. Our distro upgrade instructions and scripts contain a step to adjust the well-known (as used by Debian itself) suite names automatically, i.e. buster => bullseye => bookworm. But some repositories use different suite names, or an old style repo structure without suites but a custom path element, like Debian_xy here. I see the same in the myMPD repo, which uses the OpenSUSE platform as well, and follows the same logic. So we can adjust these in upgrade instructions/scripts in all those cases it seems.
Take care to keep the repository key updated. It may change when switching to a different repository path (when changing if for a distro upgrade), or it may expire, or it may be revoked. Check instructions you used to add the repo in the first place. Often they are located within the repo URL and can be just downloaded, like the one I linked above. Replace the old file with it, usually found in /etc/apt/trusted.gpg.d. Or the .list files defines the path to the key explicitly.
ok thanks for the explain. I think I understand it more.
I think that I did add the repo just because some old guide told me to so I only wrote those command that the guide told me and I was not thinking what it was saying if some of it was not needed. but it was also quite long ago.