During Update Using Terminal - Multiple Errors regarding missing "Release File"

onepiece · 2025/08/27, 22:24:03

Folks,
I tried to untangle this web of errors using Google..but was unsuccessful. Can someone point me in the direction of getting rid of the multiple errors after running: $ sudo apt update at the terminal?

I do have a backup of my SHINE ON instance, but I'm trying to learn HOW to untangle knots like this one. Thanks in advance. Also, not sure if I'd get the same errors using my backup as it seems some of the problem is related to sources or lists that are no longer available.

Thank you in advance.

==============================

d@d-virtualbox:~$ sudo apt update
[sudo] password for d:
Ign:1 https://ftp.belnet.be/mirror/siduction/extra unstable InRelease
Ign:2 https://ftp.belnet.be/mirror/siduction/fixes unstable InRelease
Err:3 https://ftp.belnet.be/mirror/siduction/extra unstable Release
Cannot initiate the connection to ftp.belnet.be:443 (2001:6a8:3c80::27). - connect (101: Network is unreachable) Cannot initiate the connection to ftp.belnet.be:443 (193.190.198.27). - connect (101: Network is unreachable)
Err:4 https://ftp.belnet.be/mirror/siduction/fixes unstable Release
Cannot initiate the connection to ftp.belnet.be:443 (2001:6a8:3c80::27). - connect (101: Network is unreachable) Cannot initiate the connection to ftp.belnet.be:443 (193.190.198.27). - connect (101: Network is unreachable)
Ign:5 https://brave-browser-apt-release.s3.brave.com stable InRelease
Err:6 https://brave-browser-apt-release.s3.brave.com stable Release
Cannot initiate the connection to brave-browser-apt-release.s3.brave.com:443 (18.238.96.109). - connect (101: Network is unreachable) Cannot initiate the connection to brave-browser-apt-release.s3.brave.com:443 (18.238.96.110). - connect (101: Network is unreachable) Cannot initiate the connection to brave-browser-apt-release.s3.brave.com:443 (18.238.96.22). - connect (101: Network is unreachable) Cannot initiate the connection to brave-browser-apt-release.s3.brave.com:443 (18.238.96.101). - connect (101: Network is unreachable)
Hit:7 https://deb.debian.org/debian trixie InRelease
Hit:8 https://deb.debian.org/debian unstable InRelease
Error: The repository 'https://ftp.belnet.be/mirror/siduction/extra unstable Release' no longer has a Release file.
Notice: Updating from such a repository can't be done securely, and is therefore disabled by default.
Notice: See apt-secure(

manpage for repository creation and user configuration details.
Error: The repository 'https://ftp.belnet.be/mirror/siduction/fixes unstable Release' no longer has a Release file.
Notice: Updating from such a repository can't be done securely, and is therefore disabled by default.
Notice: See apt-secure(

manpage for repository creation and user configuration details.
Error: The repository 'https://brave-browser-apt-release.s3.brave.com stable Release' no longer has a Release file.
Notice: Updating from such a repository can't be done securely, and is therefore disabled by default.
Notice: See apt-secure(

manpage for repository creation and user configuration details.
d@d-virtualbox:~$ sudo apt-get upgrade --fix-missing
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
d@d-virtualbox:~$

effo · 2025/08/27, 22:32:40

I think the problem here is

Code Select

Err:3 https://ftp.belnet.be/mirror/siduction/extra unstable Release                                         
  Cannot initiate the connection to ftp.belnet.be:443 (2001:6a8:3c80::27). - connect (101: Network is unreachable) Cannot initiate the connection to ftp.belnet.be:443 (193.190.198.27). - connect (101: Network is unreachable)

For some reason you can not connect to the package repository.
I have the same problem myself after the last updates, I think it broke during weekend.
It seems like my network connection suddenly got unstable. It works, then stops working, then works:

Code Select

root@siductionbox:~# apt update
Ign:1 http://httpredir.debian.org/debian unstable InRelease
Err:2 http://httpredir.debian.org/debian unstable Release                                                                 
  Cannot initiate the connection to httpredir.debian.org:80 (2a04:4e42:6b::644). - connect (101: Network is unreachable) Cannot initiate the connection to httpredir.debian.org:80 (199.232.174.132). - connect (101: Network is unreachable)
Hit:4 http://dl.google.com/linux/chrome/deb stable InRelease                                                                                                     
Hit:3 https://repository.spotify.com stable InRelease                                                 
Hit:7 https://updates.signal.org/desktop/apt xenial InRelease                                        
Hit:5 https://packages.siduction.org/extra unstable InRelease                 
Hit:6 https://packages.siduction.org/fixes unstable InRelease
Error: The repository 'http://httpredir.debian.org/debian unstable Release' no longer has a Release file.
Notice: Updating from such a repository can't be done securely, and is therefore disabled by default.
Notice: See apt-secure(8) manpage for repository creation and user configuration details.
root@siductionbox:~# apt update
Ign:1 http://packages.siduction.org/extra unstable InRelease
Ign:2 http://packages.siduction.org/fixes unstable InRelease                                                                           
Hit:4 http://dl.google.com/linux/chrome/deb stable InRelease                                                                                                                    
Hit:5 http://httpredir.debian.org/debian unstable InRelease                                                                                           
Hit:3 https://repository.spotify.com stable InRelease                                                                      
Hit:8 https://updates.signal.org/desktop/apt xenial InRelease                                                              
Get:6 https://packages.siduction.org/extra unstable Release [17.7 kB]          
Get:7 https://packages.siduction.org/fixes unstable Release [23.2 kB]
Get:9 https://packages.siduction.org/extra unstable Release.gpg [833 B]
Get:10 https://packages.siduction.org/fixes unstable Release.gpg [833 B]
Fetched 42.6 kB in 0s (116 kB/s)    
53 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@siductionbox:~# apt update
Ign:1 http://dl.google.com/linux/chrome/deb stable InRelease
Err:2 http://dl.google.com/linux/chrome/deb stable Release                                                                                           
  Cannot initiate the connection to dl.google.com:80 (2a00:1450:400f:80c::200e). - connect (101: Network is unreachable) Cannot initiate the connection to dl.google.com:80 (216.58.211.14). - connect (101: Network is unreachable)
Ign:3 http://httpredir.debian.org/debian unstable InRelease                                                                                                         
Get:6 http://httpredir.debian.org/debian unstable Release [214 kB]                                                                                                  
Ign:5 https://packages.siduction.org/extra unstable InRelease                                                                        
Hit:4 https://repository.spotify.com stable InRelease                                                                                
Hit:8 https://updates.signal.org/desktop/apt xenial InRelease                                     
Get:7 https://packages.siduction.org/fixes unstable InRelease [24.1 kB]                                       
Get:10 http://httpredir.debian.org/debian unstable Release.gpg [1,601 B]
Hit:9 https://packages.siduction.org/extra unstable Release               
Error: The repository 'http://dl.google.com/linux/chrome/deb stable Release' no longer has a Release file.
Notice: Updating from such a repository can't be done securely, and is therefore disabled by default.
Notice: See apt-secure(8) manpage for repository creation and user configuration details.
root@siductionbox:~#

I have no clues, network is stable for other clients on my network

unklarer · 2025/08/28, 09:34:42

Why don't you use another mirror listed in the files?

/etc/apt/soures.list.d/debian.sources
/etc/apt/sources.list.d/extra.sources
/etc/apt/sources.list.d/fixes.sources

onepiece · 2025/09/03, 03:52:31

Quote from: unklarer on 2025/08/28, 09:34:42
Why don't you use another mirror listed in the files?

/etc/apt/soures.list.d/debian.sources
/etc/apt/sources.list.d/extra.sources
/etc/apt/sources.list.d/fixes.sources

Thank you for your suggestion...but...I'm afraid I'll need a bit more handholding to execute your idea. I've attached my directory screenshot. Can you explain exactly which files I should modify...and exactly what the modifications would be? Thank you for your understanding.

dibl · 2025/09/03, 07:10:39

About 3 days ago, a Debian repo source file like this:

Code Select

Types: deb
URIs: https://deb.debian.org/debian/
Suites: unstable
Components: main contrib non-free non-free-firmware
Enabled: yes
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

suddenly started causing this error: "Cannot initiate the connection to ftp.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx). - connect (101: Network is unreachable) " .....

After I changed it to this:

Code Select

Types: deb
URIs: https://deb.debian.org/debian
Suites: unstable
Components: main contrib non-free non-free-firmware
Enabled: yes
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

the error is gone. Apparently, "/" was the problem.

unklarer · 2025/09/03, 14:08:27

Quote from: onepiece on 2025/09/03, 03:52:31
Quote from: unklarer on 2025/08/28, 09:34:42
Why don't you use another mirror listed in the files?

/etc/apt/soures.list.d/debian.sources
/etc/apt/sources.list.d/extra.sources
/etc/apt/sources.list.d/fixes.sources

Thank you for your suggestion...but...I'm afraid I'll need a bit more handholding to execute your idea. I've attached my directory screenshot. Can you explain exactly which files I should modify...and exactly what the modifications would be? Thank you for your understanding.

Please read the manual.

onepiece · 2025/09/13, 05:43:16

I decided to 'live with' the multiple errors during updates. Too many other of Life's competing needs.

Then over several days and several update sessions later. . .
Without rhyme or reason and without me making ANY further tweaks or adjustments of ANY kind
ALL the errors auto--magically DISAPPEARED!
System is operating in tip top performance.

Love Siduction Linux...but hard to wrap my head around behaviors like that.

Cheers to all!

Pip · 2025/09/13, 09:16:30

You have a number of files in /etc/apt/sources.list.d. brave-browser-release.list is the only one still in the old "list" format instead of the new "sources" format, though there isn't a working list for dbgsym, so it looks like you've run "apt modernize-sources" already, which converts old list files into sources ones. Once you've established that the sources files work, you can delete the list.bak and list.save files which have a sources equivalent to tidy up the directory.
If you get a problem with connecting to a URI, find out where it is listed with

Code Select

grep ftp.belnet.be /etc/apt/sources.list.d/*
When I do it, I get

Code Select

/etc/apt/sources.list.d/extra.sources:# deb-src https://ftp.belnet.be/mirror/siduction/extra unstable main
/etc/apt/sources.list.d/fixes.sources:# deb https://ftp.belnet.be/mirror/siduction/fixes unstable main
/etc/apt/sources.list.d/fixes.sources:# deb-src https://ftp.belnet.be/mirror/siduction/fixes unstable main

from which I can see that it turns up in the extra.sources and fixes.sources files, though in my case commented out.

Code Select

sudo vi /etc/apt/sources.list.d/extras.sources
shows me that my active URI is

Code Select

Types: deb
URIs:  http://ftp.uni-stuttgart.de/siduction/extra 
Suites: unstable
Components: main contrib non-free non-free-firmware
Enabled: yes
Signed-By: /usr/share/keyrings/extra-archive-keyring.gpg

If I was having problems with ftp.uni-stuttgart.de, I'd replace it with one of the other sources in the file (like ftp.belnet.be).
That was pretty much it. You were pointing to a site which was having problems, you could have changed what you were pointing to to get around that. Sometimes, like in your case, it just recovers anyway.

onepiece · 2025/09/14, 22:29:03

Thanks to all...and especially to Pip for his helpful explanation.

The list of errors ....when it first happened...were overwhelming. I couldn't tell if it was truly a 'network' connection issue OR if the Release file I needed was not there or up-to-date. With your explanation AND 20/20 hindsight, it *mostly* makes sense to me now.

I appreciate Pip's detailed explanation of the bad or offline URL embedded within the 3 sources.list.d/ files
/etc/apt/soures.list.d/debian.sources
/etc/apt/sources.list.d/extra.sources
/etc/apt/sources.list.d/fixes.sources

Just to beat a dead horse a little more....
Regarding the need to connect with a fully operational mirror's URL.
PLEASE confirm for me the servers I should be trying out in the future if this happens again are the ones listed in Section 3.4 of the Siduction Manual, right? (Small portion of Siduction Manual Section 3.4 copied below).

3.4 Downloading the ISO
Please use the closest mirror. Mirror servers listed below, with details for the entry
in
/etc/apt/sources.list.d/siduction.sources, are updated in a timely manner.
Europe
• Office Vienna, Vienna, Austria
https://siduction.office-vienna.at/
• Freie Universität Berlin/spline (Student Project LInux NEtwork), Germany
http://ftp.spline.de/pub/siduction/
https://ftp.spline.de/pub/siduction/
ftp://ftp.spline.de/pub/siduction/
• University of Stuttgart, Germany
https://ftp.uni-stuttgart.de/siduction/
ftp://ftp.uni-stuttgart.de/siduction/
• Academic Computer Club, Umeå University, Sweden
http://ftp.acc.umu.se/mirror/siduction.org/
https://ftp.acc.umu.se/mirror/siduction.org/
rsync://ftp.acc.umu.se/mirror/siduction.org/

Thanks again to all.

Pip · 2025/09/16, 19:42:52

Or those found on https://siduction.org/mirrors/

onepiece · 2025/09/16, 19:53:49

Thanks Pip! You really walked me through this and I have a much better understanding. You should be a Linux Instructor! Very helpful and easy to understand!