Re: Pi UPDATE Errors! some help
Edit: deleted the content since I can't delete the post. Nobody needs the hassle it caused.
Last edited by Anonymous on Fri Apr 07, 2023 12:57 am, edited 1 time in total.
- davidcoton
- Posts: 7120
- Joined: Mon Sep 01, 2014 2:37 pm
- Location: Cambridge, UK
Re: Pi UPDATE Errors! some help
As was mentioned by rpdom, there are differences between apt and apt-get. The differences are deliberate and for good reason.
Historically, apt-get was intended to be scriptable. It makes guesses about what to do when there is a choice, avoiding any interactive questions to an absent user. The guesses are designed to be, firstly, safe and secondly, helpful.
However, when the command is run interactively, it is more helpful to ask what was intended if there is a choice. Rather than changing apt-get and potentially breaking thousands of scripts, the sensible decision was to fork a new version, apt, optimised for interactive use, while leaving the behaviour of apt-get unchanged in this respect. Therefore, apt-get continues to be the correct choice for using in a script, whilst apt will normally be more useful when used interactively.
There was also an additional subcommand added: full-upgrade. The reason for that is that it is a more helpful name than dist-upgrade, although it does the same thing (which is not to do a cross -version upgrade of the distribution, which was frequently assumed). Again, the older command was retained (even, IIRC, in apt), in order not to break existing scripts.
Historically, apt-get was intended to be scriptable. It makes guesses about what to do when there is a choice, avoiding any interactive questions to an absent user. The guesses are designed to be, firstly, safe and secondly, helpful.
However, when the command is run interactively, it is more helpful to ask what was intended if there is a choice. Rather than changing apt-get and potentially breaking thousands of scripts, the sensible decision was to fork a new version, apt, optimised for interactive use, while leaving the behaviour of apt-get unchanged in this respect. Therefore, apt-get continues to be the correct choice for using in a script, whilst apt will normally be more useful when used interactively.
There was also an additional subcommand added: full-upgrade. The reason for that is that it is a more helpful name than dist-upgrade, although it does the same thing (which is not to do a cross -version upgrade of the distribution, which was frequently assumed). Again, the older command was retained (even, IIRC, in apt), in order not to break existing scripts.
Location: 345th cell on the right of the 210th row of L2 cache
- DougieLawson
- Posts: 42641
- Joined: Sun Jun 16, 2013 11:19 pm
- Location: A small cave in deepest darkest Basingstoke, UK
Re: Pi UPDATE Errors! some help
How about not
Languages using left-hand whitespace for syntax are ridiculous
DMs sent on https://twitter.com/DougieLawson or LinkedIn will be answered next month.
Fake doctors - are all on my foes list.
The use of crystal balls and mind reading is prohibited.
DMs sent on https://twitter.com/DougieLawson or LinkedIn will be answered next month.
Fake doctors - are all on my foes list.
The use of crystal balls and mind reading is prohibited.
Re: Pi UPDATE Errors! some help
Changing the Raspbian Repository Mirror will solve the update problem
Follow below link:
https://pimylifeup.com/raspbian-repository-mirror/
Follow below link:
https://pimylifeup.com/raspbian-repository-mirror/
Re: Pi UPDATE Errors! some help
I'm having the same errors with upgrading on a new Raspberry Pi OS Lite 32-bit install. I changed my source list mirror to one from North America on the official mirror list (http://www.raspbian.org/RaspbianMirrors). Now I can get an upgrade. Not sure why the default source location is failing.
I used the tips on Pi My Life Up: https://pimylifeup.com/raspbian-repository-mirror/.
I used the tips on Pi My Life Up: https://pimylifeup.com/raspbian-repository-mirror/.
Re: Pi UPDATE Errors! some help
$ sudo apt update
Err:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Temporary failure resolving 'raspbian.raspberrypi.org'
Err:2 http://archive.raspberrypi.org/debian bullseye InRelease
Temporary failure resolving 'archive.raspberrypi.org'
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
W: Failed to fetch http://raspbian.raspberrypi.org/raspbia ... /InRelease Temporary failure resolving 'raspbian.raspberrypi.org'
W: Failed to fetch http://archive.raspberrypi.org/debian/d ... /InRelease Temporary failure resolving 'archive.raspberrypi.org'
W: Some index files failed to download. They have been ignored, or old ones used instead.
I facing this issue.
Err:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Temporary failure resolving 'raspbian.raspberrypi.org'
Err:2 http://archive.raspberrypi.org/debian bullseye InRelease
Temporary failure resolving 'archive.raspberrypi.org'
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
W: Failed to fetch http://raspbian.raspberrypi.org/raspbia ... /InRelease Temporary failure resolving 'raspbian.raspberrypi.org'
W: Failed to fetch http://archive.raspberrypi.org/debian/d ... /InRelease Temporary failure resolving 'archive.raspberrypi.org'
W: Some index files failed to download. They have been ignored, or old ones used instead.
I facing this issue.