Update failure

[leminisage]

HI all, i need help with... updating the system, i think.
i tried to use the command

sudo apt update

but the i got this:

Ign:1 http://ftp.debian.org/debian buster-backports InRelease
Err:2 http://ftp.debian.org/debian buster-backports Release
404 Not Found [IP: 2a04:4e42:6a::644 80]
Hit:3 https://dl.winehq.org/wine-builds/debian bullseye InRelease
Hit:4 https://deb.debian.org/debian bullseye InRelease
Hit:5 https://deb.debian.org/debian bullseye-updates InRelease
Hit:6 https://deb.debian.org/debian-security bullseye-security InRelease
Hit:7 https://deb.debian.org/debian bullseye-backports InRelease
Hit:8 https://repo.steampowered.com/steam stable InRelease
Ign:9 https://storage.googleapis.com/cros-packages/126 bullseye InRelease
Hit:10 https://storage.googleapis.com/cros-packages/126 bullseye Release
Reading package lists... Done
E: The repository 'http://ftp.debian.org/debian buster-backports Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

I don't really know what to do to solve this problem. Do you have any solutions?

 

[osprey]

HI all, i need help with... updating the system, i think.
i tried to use the command

but the i got this:

I don't really know what to do to solve this problem. Do you have any solutions?

The problem appears to be that your sources.list is configured to draw packages from at least 3 different debian distributions: buster, bullseye and bookworm (stable).

To resolve the matter, reconfigure the sources.list to a single debian release, for example, bullseye (without all the specialist non-debian.org repos) , then do an update, upgrade and full-upgrade. Then, if you wish to update to bookworm, configure the sources.list to access bookworm, by editing the sources.list to access the bookworm release, and do the same again, update, upgrade and full-upgrade. After that, you can introduce the specialist repos one by one, updating and upgrading each time to see that they work..

There's an example of a sources.list here for debian bookworm: https://wiki.debian.org/SourcesList

This site has an explanation of why and how users can best maintain their debian installation in robust and reliable condition: https://wiki.debian.org/DontBreakDebian

 

[tinfoil-hat]

I think you successfully created a frankendebian

 

[tinfoil-hat]

If you actually installed software between those releases, it could be, your installation is broken.
If I were you, I'd edit my

/etc/apt/sources.list

and insert the stable repo list like this

deb https://deb.debian.org/debian bullseye main contrib non-free
deb-src https://deb.debian.org/debian bullseye main contrib non-free

deb https://deb.debian.org/debian bullseye-updates main contrib non-free
deb-src https://deb.debian.org/debian bullseye-updates main contrib non-free

deb https://deb.debian.org/debian bullseye-backports main contrib non-free
deb-src https://deb.debian.org/debian bullseye-backports main contrib non-free

deb https://security.debian.org/debian-security/ bullseye-security main contrib non-free
deb-src https://security.debian.org/debian-security/ bullseye-security main contrib non-free

Then do a backup, press fingers and do a

sudo apt update
sudo apt dist-upgrade

if something fails around the way, you could try a

sudo apt-get autoremove
sudo apt-get -f install

Maybe we can help you if you tried this

Again, this is what I would do, maybe someone else would do otherwise

 

[Trenix25]

The problem appears to be that your sources.list is configured to draw packages from at least 3 different debian distributions: buster, bullseye and bookworm (stable).

To resolve the matter, reconfigure the sources.list to a single debian release, for example, bullseye (without all the specialist non-debian.org repos) , then do an update, upgrade and full-upgrade. Then, if you wish to update to bookworm, configure the sources.list to access bookworm, by editing the sources.list to access the bookworm release, and do the same again, update, upgrade and full-upgrade. After that, you can introduce the specialist repos one by one, updating and upgrading each time to see that they work..

There's an example of a sources.list here for debian bookworm: https://wiki.debian.org/SourcesList

This site has an explanation of why and how users can best maintain their debian installation in robust and reliable condition: https://wiki.debian.org/DontBreakDebian

Be careful with full-upgrade. I tried to update to Debian 12 that way from Debian 11 and the update process failed and left my Linux system unusable.

Signed,

Matthew Campbell

 

[Trenix25]

If you actually installed software between those releases, it could be, your installation is broken.
If I were you, I'd edit my

/etc/apt/sources.list

and insert the stable repo list like this

deb http://deb.debian.org/debian bullseye main contrib non-free
deb-src http://deb.debian.org/debian bullseye main contrib non-free

deb http://deb.debian.org/debian bullseye-updates main contrib non-free
deb-src http://deb.debian.org/debian bullseye-updates main contrib non-free

deb http://deb.debian.org/debian bullseye-backports main contrib non-free
deb-src http://deb.debian.org/debian bullseye-backports main contrib non-free

deb http://security.debian.org/debian-security/ bullseye-security main contrib non-free
deb-src http://security.debian.org/debian-security/ bullseye-security main contrib non-free

Then do a backup, press fingers and do a

sudo apt update
sudo apt dist-upgrade

if something fails around the way, you could try a

sudo apt-get autoremove
sudo apt-get -f install

Maybe we can help you if you tried this

Again, this is what I would do, maybe someone else would do otherwise

You should always use https instead of http in your sources.list file.

Signed,

Matthew Campbell

 

[tinfoil-hat]

You should always use https instead of http in your sources.list file.

Signed,

Matthew Campbell

I edited the post, thank you

 

[osprey]

You should always use https instead of http in your sources.list file.

Signed,

Matthew Campbell

Here is an interesting discussion on the matter with some links to further info: https://forums.debian.net/viewtopic.php?t=152681

Basically, apt has its own verification processes which is what really matters in terms of valid packages and the debian wiki is pretty much a consistently reliable guide which is overseen by many wise debian eyes. The apt-secure manpage has some details. YMMV

 

[Brickwizard]

i tried to use the command
but the i got this:

sudo apt update is only the start of the process, for my Debian based distributions I use
sudo apt update && apt upgrade -y or on some I need to use sudo apt update && apt full-upgrade -y or sudo apt update && apt distribution-upgrade -y
upgrade should ignore repositories it cant reach

if you get a report cannot continue broken packages, then try
configure -a
followed by sudo apt --fix-broken install && apt-get -f install