Regular OS update/upgrade

mgarcia · 21 August 2020 21:49

Can someone clarify? It’s been several weeks since the last time I did complete a routine update/upgrade and evidently/apparently nobody is watching because every time, without fail, there are constant errors and the system is unable to get to the correct site to find the required piece(s) of software. There are more IGN sites than HITs and even ends with the following error messages:
The repository ‘http://mirrordirector.raspbian.org/raspbian wheezy Release’ does
│ not have a Release file.
│ E: Failed to fetch
│ http://mirrordirector.raspbian.org/raspbian/dists/wheezy/main/source/Sources 404
│ Not Found
│ E: Some index files failed to download. They have been ignored, or old ones used
│ instead.

Is this something happening to only one person? Don’t think so. Maybe someone can take a look and let us know, please? As always, in advance, I thank you for your time, help, consideration and expertise.

Joulinar · 22 August 2020 11:11

Hi,

many thanks for your message. Pls can you post the entire output of apt update

mgarcia · 22 August 2020 16:07

Thank you for your reply, the requested information follows:

-------------------------------------------------------
#### Details:
- Date           | Sat Aug 22 10:53:33 CDT 2020
- DietPi version | v6.30.0 (MichaIng/master)
- Image creator  | DietPi Core Team
- Pre-image      | Raspbian Lite
- Hardware       | RPi 2 Model B (armv7l) (ID=2)
- Kernel version | Linux dietpi20053101 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux
- Distro         | stretch (ID=4)
- Command        | apt-get -q update
- Exit code      | 100
- Software title | DietPi-Update
#### Steps to reproduce:
<!-- Explain how to reproduce the issue -->
1. ...
2. ...
#### Expected behaviour:
<!-- What SHOULD happen? -->
- ...
#### Actual behaviour:
<!-- What IS happening? -->
- ...
#### Extra details:
<!-- Please post any extra details that might help solve the issue -->
- ...
#### Additional logs:

---------------------------------------------------------------------
[FAILED] DietPi-Update | Unable to continue, DietPi-Update will now terminate.

Joulinar · 22 August 2020 21:04

no need to run dietpi-update. It’s enough to do apt update.

Your problem seems to be Debian package source. As far as I can see you are on Debian 9 (Stretch). However you seems to have a package source defined for Debian 7 (Wheezy).

Do you know if there is a reason for having such an old Debian package source configured? I guess the data your system is looking for simple did not existing anymore. Therefore you get the error message. If not needed, I would recommend to remove Wheezy from package source files.

pls can you have a look to following file /etc/apt/sources.list as well as directory /etc/apt/sources.list.d/ if you see someting related to Wheezy

BTW: Current version is Debian 10 (Buster)

https://en.wikipedia.org/wiki/Debian_version_history#Release_table

mgarcia · 24 August 2020 19:56

Thank you for your reply and information. Unfortunately, unable to reply sooner.

As you may conclude, I’m new to DietPi and only have basic (literally BASIC, from Commodore Business Machines back in the 80’s) self-education and since then, have been dealing with originally MS-DOS and most of the Win versions 'till I became tired of the loss of time and need to provide end-user input on bugs to include in their next version/upgrade that requires paying for the new version to only repeat the process, however, I’ve been using multiple versions of live Linux distros and most recently with rPi now after trying different NOOB options, I concluded that DietPi is the simplest and easiest to use to create my own projects, with the intention of most likely creating my own personalized OS version in the future if at all possible.

You are definitely correct, big difference, I reviewed the files in the areas you pointed to and found the reference to different and conflicting versions that I myself most likely entered when reading how to setup the different servers I’ve tried and I’m using, however, I attempted to standardize all those references now to the most recent version (Buster) and the following errors still came back and I’m certain I’m not using the proper archive/repositories, therefore, the question is how to know which are the ones considered official and which are the ones to use as back-up.

apt update:
Get:1 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB]
Err:2 http://mirrordirect.raspbian.org/raspbian buster InRelease
  Could not resolve 'mirrordirect.raspbian.org'
W: Failed to fetch http://mirrordirect.raspbian.org/raspbian/dists/buster/InRelease  Could not resolve 'mirrordirect.raspbian.org'
W: Some index files failed to download. They have been ignored, or old ones used instead.

apt upgrade:
863 upgraded, 251 newly installed, 0 to remove and 95 not upgraded.
Err:276 http://mirror.sjc02.svwh.net/raspbian/raspbian buster/main armhf libwebkit2gtk-4.0-37 armhf 2.28.4-1~deb10u1+rpi1
  Could not connect to mirror.sjc02.svwh.net:80 (72.5.72.15), connection timed out
Err:314 http://mirror.sjc02.svwh.net/raspbian/raspbian buster/main armhf libjavascriptcoregtk-4.0-18 armhf 2.28.4-1~deb10u1+rpi1
  Unable to connect to mirror.sjc02.svwh.net:http:
Fetched 588 MB in 9min 55s (988 kB/s)
E: Failed to fetch http://mirror.sjc02.svwh.net/raspbian/raspbian/pool/main/w/webkit2gtk/libwebkit2gtk-4.0-37_2.28.4-1~deb10u1+rpi1_armhf.deb  Could not connect to mirror.sjc02.svwh.net:80 (72.5.72.15), connection timed out
E: Failed to fetch http://mirror.sjc02.svwh.net/raspbian/raspbian/pool/main/w/webkit2gtk/libjavascriptcoregtk-4.0-18_2.28.4-1~deb10u1+rpi1_armhf.deb  Unable to connect to mirror.sjc02.svwh.net:http:
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

Hope this helps clarify.

MichaIng · 24 August 2020 21:23

Please replace http://mirrordirect.raspbian.org/raspbian in your /etc/apt/sources.list with http://raspbian.raspberrypi.org/raspbian/. This mirror director has been shut down a longer time ago and some earlier raspberrypi-sys-mods package upgrades already replaced it.

mgarcia · 25 August 2020 01:18

There are currently two entries:
one starting with deb
second one starting with deb-src

Do we need to keep both or only one?

Joulinar · 25 August 2020 07:45

deb entry should be fine. And, pls don’t add a simple buster entry. You are still on Stretch and there are some other steps needed to upgrade. First I would recommend to get all thinks done on Stretch and afterwards you could think on an in-place upgrade to Buster

MichaIng · 27 August 2020 21:53

deb-src is the source package repository, which you usually do not required if you don’t compile software on your own from Debian sources.

A reset to functional defaults can be btw done via:

/boot/dietpi/func/dietpi-set_software apt-mirror default

mgarcia · 28 August 2020 02:08

Very much appreciate all your help. Best wishes and until next time.

Joulinar · 28 August 2020 07:30

pls can you let us know if you issue was fixed? And if yes, what was the final solution?