Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#1033200: apt, apt-get, aptitude and others have been failing for an extended period.
88 views
Skip to first unread message
WILLIAM ORVILLE RICHMOND
Mar 19, 2023, 11:30:05 AM3/19/23
to
Package: apt-get
Version: 2.2.4
From: William O Richmond
wor...@windstream.net
When, for example, I do:
orville@flinta:~$ sudo apt-get install lynx
[sudo] password for orville:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
lynx-common
The following NEW packages will be installed:
lynx lynx-common
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,844 kB of archives.
After this operation, 5,768 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Ign:1 http://deb.debian.org/debian bullseye/main amd64 lynx-common all
2.9.0dev.6-3~deb11u1
Ign:2 http://deb.debian.org/debian bullseye/main amd64 lynx amd64
2.9.0dev.6-3~deb11u1
Err:1 http://deb.debian.org/debian bullseye/main amd64 lynx-common all
2.9.0dev.6-3~deb11u1
Connection failed [IP: 199.232.34.132 80]
Err:2 http://deb.debian.org/debian bullseye/main amd64 lynx amd64
2.9.0dev.6-3~deb11u1
Connection failed [IP: 199.232.34.132 80]
E: Failed to fetch
http://security.debian.org/debian-security/pool/updates/main/l/lynx/lynx-common_2.9.0dev.6-3%7edeb11u1_all.deb
Connection failed [IP: 199.232.34.132 80]
E: Failed to fetch
http://security.debian.org/debian-security/pool/updates/main/l/lynx/lynx_2.9.0dev.6-3%7edeb11u1_amd64.deb
Connection failed [IP: 199.232.34.132 80]
E: Unable to fetch some archives, maybe run apt-get update or try with
--fix-missing?
orville@flinta:~$
orville@flinta:~$
orville@flinta:~$ lynx
-bash: lynx: command not found
orville@flinta:~$
I have been mystified by this sort of behavior for a number of
months. I have made no headway. I have effectively lost the use of
debian linux due to problems resulting from the failure of the update
and installation mechanisms. For me this has also become a major
security problem. Clamav has ceased to function after months of
freshclam failures. Firefox is getting older and older.
I have a number of machines running various flavors of ubuntu. The
problems which I have with debian are very much the same as ubuntu.
I have a Fedora machine as well. I normally have not much liked
Fedora because I find it constricting, however it is up to date. I had a
spell where its updates were very slow, but it seems to have gotten past
that time.
I have installed Fedora on a second machine, and if I can resolve the
problems with it I will begin the VERY laborious process of porting
applications and data to Fedora.
I have been considering that maybe some part of the update process,
(curl ??), has been being intercepted ... perhaps by my ISP?? ... but I
don't know. I have been studying VPN implementation. I really require
a VPN with its own IP address to test this. I would have to do this
using Fedora or some other system as I cannot download VPN components
successfully on Debian or Ubuntu machines.
I have successfully connected to both the Debian and Ubuntu sites
using ncftp and also to a limited extent using lynx. I was able to
download files with ncftp and to a lesser extent with lynx. Apt-get etc
however seem to have no luck. I can make no sense of any of this.
Needless to say, I have not been able to download and install
"reportbug" and am probably obviously not using it.
It has seemed to be to be unlikely that I am the only person with
these problems, however I do apologize for waiting so long,
I would appreciate at least a note that somebody has received this
missive and am actually hoping for some resolution. I am most easily
reached by email at wor...@windstream.net.
Thanking everyone in advance for their help.
William O Richmond
orville@flinta:~$ uname -a
Linux flinta 5.10.0-14-amd64 #1 SMP Debian 5.10.113-1 (2022-04-29) x86_64
orville@flinta:~$ ls -l /lib/*/libc.so.6
lrwxrwxrwx 1 root root 12 Mar 17 2022 /lib/x86_64-linux-gnu/libc.so.6
-> libc-2.31.so
orville@flinta:~$ apt show libc6 | grep ^Version
Version: 2.31-13+deb11u3
Version: 2.2.4
From: William O Richmond
wor...@windstream.net
When, for example, I do:
orville@flinta:~$ sudo apt-get install lynx
[sudo] password for orville:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
lynx-common
The following NEW packages will be installed:
lynx lynx-common
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,844 kB of archives.
After this operation, 5,768 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Ign:1 http://deb.debian.org/debian bullseye/main amd64 lynx-common all
2.9.0dev.6-3~deb11u1
Ign:2 http://deb.debian.org/debian bullseye/main amd64 lynx amd64
2.9.0dev.6-3~deb11u1
Err:1 http://deb.debian.org/debian bullseye/main amd64 lynx-common all
2.9.0dev.6-3~deb11u1
Connection failed [IP: 199.232.34.132 80]
Err:2 http://deb.debian.org/debian bullseye/main amd64 lynx amd64
2.9.0dev.6-3~deb11u1
Connection failed [IP: 199.232.34.132 80]
E: Failed to fetch
http://security.debian.org/debian-security/pool/updates/main/l/lynx/lynx-common_2.9.0dev.6-3%7edeb11u1_all.deb
Connection failed [IP: 199.232.34.132 80]
E: Failed to fetch
http://security.debian.org/debian-security/pool/updates/main/l/lynx/lynx_2.9.0dev.6-3%7edeb11u1_amd64.deb
Connection failed [IP: 199.232.34.132 80]
E: Unable to fetch some archives, maybe run apt-get update or try with
--fix-missing?
orville@flinta:~$
orville@flinta:~$
orville@flinta:~$ lynx
-bash: lynx: command not found
orville@flinta:~$
I have been mystified by this sort of behavior for a number of
months. I have made no headway. I have effectively lost the use of
debian linux due to problems resulting from the failure of the update
and installation mechanisms. For me this has also become a major
security problem. Clamav has ceased to function after months of
freshclam failures. Firefox is getting older and older.
I have a number of machines running various flavors of ubuntu. The
problems which I have with debian are very much the same as ubuntu.
I have a Fedora machine as well. I normally have not much liked
Fedora because I find it constricting, however it is up to date. I had a
spell where its updates were very slow, but it seems to have gotten past
that time.
I have installed Fedora on a second machine, and if I can resolve the
problems with it I will begin the VERY laborious process of porting
applications and data to Fedora.
I have been considering that maybe some part of the update process,
(curl ??), has been being intercepted ... perhaps by my ISP?? ... but I
don't know. I have been studying VPN implementation. I really require
a VPN with its own IP address to test this. I would have to do this
using Fedora or some other system as I cannot download VPN components
successfully on Debian or Ubuntu machines.
I have successfully connected to both the Debian and Ubuntu sites
using ncftp and also to a limited extent using lynx. I was able to
download files with ncftp and to a lesser extent with lynx. Apt-get etc
however seem to have no luck. I can make no sense of any of this.
Needless to say, I have not been able to download and install
"reportbug" and am probably obviously not using it.
It has seemed to be to be unlikely that I am the only person with
these problems, however I do apologize for waiting so long,
I would appreciate at least a note that somebody has received this
missive and am actually hoping for some resolution. I am most easily
reached by email at wor...@windstream.net.
Thanking everyone in advance for their help.
William O Richmond
orville@flinta:~$ uname -a
Linux flinta 5.10.0-14-amd64 #1 SMP Debian 5.10.113-1 (2022-04-29) x86_64
orville@flinta:~$ ls -l /lib/*/libc.so.6
lrwxrwxrwx 1 root root 12 Mar 17 2022 /lib/x86_64-linux-gnu/libc.so.6
-> libc-2.31.so
orville@flinta:~$ apt show libc6 | grep ^Version
Version: 2.31-13+deb11u3
Tim Bell
Mar 19, 2023, 12:30:04 PM3/19/23
to
On 3/19/2023 10:19 AM, WILLIAM ORVILLE RICHMOND wrote:
> Err:1 http://deb.debian.org/debian bullseye/main amd64 lynx-common all
> 2.9.0dev.6-3~deb11u1
> Connection failed [IP: 199.232.34.132 80]
> Err:2 http://deb.debian.org/debian bullseye/main amd64 lynx amd64
> 2.9.0dev.6-3~deb11u1
> Connection failed [IP: 199.232.34.132 80]
> E: Failed to fetch
> http://security.debian.org/debian-security/pool/updates/main/l/lynx/lynx-common_2.9.0dev.6-3%7edeb11u1_all.deb
> Connection failed [IP: 199.232.34.132 80]
> E: Failed to fetch
> http://security.debian.org/debian-security/pool/updates/main/l/lynx/lynx_2.9.0dev.6-3%7edeb11u1_amd64.deb
> Connection failed [IP: 199.232.34.132 80]
> E: Unable to fetch some archives, maybe run apt-get update or try with
> --fix-missing?
> orville@flinta:~$
> orville@flinta:~$
> orville@flinta:~$ lynx
> -bash: lynx: command not found
> orville@flinta:~$
What does /etc/apt/sources.list look like?
> Err:1 http://deb.debian.org/debian bullseye/main amd64 lynx-common all
> 2.9.0dev.6-3~deb11u1
> Connection failed [IP: 199.232.34.132 80]
> Err:2 http://deb.debian.org/debian bullseye/main amd64 lynx amd64
> 2.9.0dev.6-3~deb11u1
> Connection failed [IP: 199.232.34.132 80]
> E: Failed to fetch
> http://security.debian.org/debian-security/pool/updates/main/l/lynx/lynx-common_2.9.0dev.6-3%7edeb11u1_all.deb
> Connection failed [IP: 199.232.34.132 80]
> E: Failed to fetch
> http://security.debian.org/debian-security/pool/updates/main/l/lynx/lynx_2.9.0dev.6-3%7edeb11u1_amd64.deb
> Connection failed [IP: 199.232.34.132 80]
> E: Unable to fetch some archives, maybe run apt-get update or try with
> --fix-missing?
> orville@flinta:~$
> orville@flinta:~$
> orville@flinta:~$ lynx
> -bash: lynx: command not found
> orville@flinta:~$
--
This email has been checked for viruses by Avast antivirus software.
www.avast.com
David Kalnischkies
Mar 21, 2023, 9:40:05 AM3/21/23
to
Control: merge 1033200 1033208 1033209
Hi,
On Sun, Mar 19, 2023 at 11:19:23AM -0400, WILLIAM ORVILLE RICHMOND wrote:
> Package: apt-get
> Version: 2.2.4
> Subject: This info seems to have inadvertently been omitted from the
> Debian Bug report logs
The package is called "apt", a package named "apt-get" doesn't exist, so
the bugs were assigned to a catch-all package – from there it got
assigned now to where you probably intended to report it against in the
first place…
Just, please don't make every of your mails a new bugreport. You can
add a message by replying to 103...@bugs.debian.org (or just reply-all
to this message here). Thanks.
> When, for example, I do:
>
> orville@flinta:~$ sudo apt-get install lynx
[…]
the IP in a browser, e.g. with "http://199.232.34.132/"? (It is
normal if the page you see isn't very informative and just talks about
"Fastly error: unknown domain". Not normal would be an error message
from your browser about being unable to connect or some such.)
> I have been considering that maybe some part of the update process, (curl
> ??), has been being intercepted ... perhaps by my ISP?? ... but I don't
curl is not part of the "update process". Sure, 'something' could
potentially interfere with your network, but while a real attack could
look the same, it is usually just some local misconfiguration and not
some sinister plot by your ISP or country (if you don't happen to live
in a sinister country of course).
Have you e.g. recently changed something in your router configuration?
Is your machine connected to the right wlan network? Sometimes, these
issues turn out to be just some new neighbor with an open wlan…
Or do you have a proxy configuration? Adblocker? A open hotspot near by
with a captive portal? …
You can change the apt sources.list to use 'https' instead of 'http' to
potentially avoid some problems with external interference (although,
some interference is considered good interference, so this isn't
a default in Debian for now). A VPN would indeed eliminate far more of
potential external interference, but for now that seems like overkill.
> It has seemed to be to be unlikely that I am the only person with these
> problems, however I do apologize for waiting so long,
As the world isn't burning (well, it is given climate and wars, but
I digress) it is actually very likely that you are the only person with
these problems as we would have literal thousands of people reporting
such issues, especially if they were ongoing for months, while we are
even in the process of releasing a new major version of Debian and
so many people interact with our servers for upgrades.
In fact, between 16 and 17 March the mail reception of the BTS and
a couple other things went down for a few hours only, and the outcry was
huge [0]. Problems for "months" is nearly 100% proof that this problem is
local to your setup.
I somewhat suspect that the reason Fedora isn't effected is simple that
the configuration you accidentally broke network reaching tools on
Debian with hasn't reached your Fedora setup yet, so I would start with
figuring out what makes your Fedora machines different from the Debian
ones. Are they in a different (sub)net on your network for example?
All in all, I don't really see a way to help you as I don't really see
how it could be a problem originating from "apt". Especially if you have
similar network problems with other tools.
Best regards
David Kalnischkies
[0] https://lists.debian.org/debian-infrastructure-announce/2023/03/msg00003.html
Hi,
On Sun, Mar 19, 2023 at 11:19:23AM -0400, WILLIAM ORVILLE RICHMOND wrote:
> Package: apt-get
> Version: 2.2.4
> Subject: This info seems to have inadvertently been omitted from the
> Debian Bug report logs
The package is called "apt", a package named "apt-get" doesn't exist, so
the bugs were assigned to a catch-all package – from there it got
assigned now to where you probably intended to report it against in the
first place…
Just, please don't make every of your mails a new bugreport. You can
add a message by replying to 103...@bugs.debian.org (or just reply-all
to this message here). Thanks.
> When, for example, I do:
>
> orville@flinta:~$ sudo apt-get install lynx
> Err:1 http://deb.debian.org/debian bullseye/main amd64 lynx-common all
> 2.9.0dev.6-3~deb11u1
> Connection failed [IP: 199.232.34.132 80]
[…]
> 2.9.0dev.6-3~deb11u1
> Connection failed [IP: 199.232.34.132 80]
> E: Failed to fetch http://security.debian.org/debian-security/pool/updates/main/l/lynx/lynx-common_2.9.0dev.6-3%7edeb11u1_all.deb
> Connection failed [IP: 199.232.34.132 80]
The IP belongs to Fastly, a big CDN, sponsoring Debian. Can you reach
> Connection failed [IP: 199.232.34.132 80]
the IP in a browser, e.g. with "http://199.232.34.132/"? (It is
normal if the page you see isn't very informative and just talks about
"Fastly error: unknown domain". Not normal would be an error message
from your browser about being unable to connect or some such.)
> I have been considering that maybe some part of the update process, (curl
> ??), has been being intercepted ... perhaps by my ISP?? ... but I don't
potentially interfere with your network, but while a real attack could
look the same, it is usually just some local misconfiguration and not
some sinister plot by your ISP or country (if you don't happen to live
in a sinister country of course).
Have you e.g. recently changed something in your router configuration?
Is your machine connected to the right wlan network? Sometimes, these
issues turn out to be just some new neighbor with an open wlan…
Or do you have a proxy configuration? Adblocker? A open hotspot near by
with a captive portal? …
You can change the apt sources.list to use 'https' instead of 'http' to
potentially avoid some problems with external interference (although,
some interference is considered good interference, so this isn't
a default in Debian for now). A VPN would indeed eliminate far more of
potential external interference, but for now that seems like overkill.
> It has seemed to be to be unlikely that I am the only person with these
> problems, however I do apologize for waiting so long,
I digress) it is actually very likely that you are the only person with
these problems as we would have literal thousands of people reporting
such issues, especially if they were ongoing for months, while we are
even in the process of releasing a new major version of Debian and
so many people interact with our servers for upgrades.
In fact, between 16 and 17 March the mail reception of the BTS and
a couple other things went down for a few hours only, and the outcry was
huge [0]. Problems for "months" is nearly 100% proof that this problem is
local to your setup.
I somewhat suspect that the reason Fedora isn't effected is simple that
the configuration you accidentally broke network reaching tools on
Debian with hasn't reached your Fedora setup yet, so I would start with
figuring out what makes your Fedora machines different from the Debian
ones. Are they in a different (sub)net on your network for example?
All in all, I don't really see a way to help you as I don't really see
how it could be a problem originating from "apt". Especially if you have
similar network problems with other tools.
Best regards
David Kalnischkies
[0] https://lists.debian.org/debian-infrastructure-announce/2023/03/msg00003.html
WILLIAM ORVILLE RICHMOND
Mar 31, 2023, 5:50:05 PM3/31/23
to
You had noted:
You can change the apt sources.list to use 'https' instead of
'http' to potentially avoid some problems with external interference
(although, some interference is considered good interference, so this
isn't a default in Debian for now). A VPN would indeed eliminate far
more of potential external interference, but for now that seems like
overkill.
==========
I got a Debian installation together ( archived ssd ) and edited
the "/etc/apt/services.list" file. I then did "sudo apt update" which
listed 187 items. I followed this with "sudo apt upgrade" which
miraculously downloaded and installed all 187 items. After rebooting
this machine with "shutdown -r now" {amazing after the amount of time I
had put in these last 2-3 months} it worked properly. I then did a
"sudo apt install a2ps", a " sudo apt install gv" and a "sudo apt
install aptitude". I followed this with "sudo aptitude" and selected
"openssh server" with the shift/+ followed by g and g. After this
completed installation and I had exited from aptitude and rebooted I
tested this by doing "ssh orville@andy". After logging in to andy I did
"ssh orville@elmer" and was able to log in to elmer.
While this is not an extensive test it seems that all on Debian
was now working.
==========
Unless I understand why this happened I will continue to consider
a VPN.
==========
The current “/etc/apt/sources.list” file on elmer --- the current Debian
makchine.
orville@elmer:/etc/apt$ cat sources.list
# See https://wiki.debian.org/SourcesList for more information.
deb https://deb.debian.org/debian bullseye main
deb-src https://deb.debian.org/debian bullseye main
deb https://deb.debian.org/debian bullseye-updates main
deb-src https://deb.debian.org/debian bullseye-updates main
deb https://security.debian.org/debian-security/ bullseye-security main
deb-src https://security.debian.org/debian-security/ bullseye-security main
==========
Xubuntu with unmodified “/etc/apt/sources.list and unmodified
“/etc/apt/sources.list.distUpgrade”
root@andy:/etc/apt# apt update
Err:1 http://security.ubuntu.com/ubuntu jammy-security InRelease
Temporary failure resolving 'security.ubuntu.com'
Err:2 http://us.archive.ubuntu.com/ubuntu jammy InRelease
Connection failed [IP: 91.189.91.39 80]
Err:3 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease
Connection failed [IP: 91.189.91.38 80]
Err:4 http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease
Connection failed [IP: 91.189.91.39 80]
All packages are up to date.
W: Failed to fetch
http://us.archive.ubuntu.com/ubuntu/dists/jammy/InRelease Connection
failed [IP: 91.189.91.39 80]
W: Failed to fetch
http://us.archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease
Connection failed [IP: 91.189.91.38 80]
W: Failed to fetch
http://us.archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease
Connection failed [IP: 91.189.91.39 80]
W: Failed to fetch
http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease
Temporary failure resolving 'security.ubuntu.com'
W: Some index files failed to download. They have been ignored, or old
ones used instead.
Xubuntu with all “http://” replaced with “https://”
root@andy:/etc/apt# apt update
Err:1 https://security.ubuntu.com/ubuntu jammy-security InRelease
Temporary failure resolving 'security.ubuntu.com'
Err:2 https://us.archive.ubuntu.com/ubuntu jammy InRelease
Temporary failure resolving 'us.archive.ubuntu.com'
Err:3 https://us.archive.ubuntu.com/ubuntu jammy-updates InRelease
Could not connect to us.archive.ubuntu.com:443 (91.189.91.39). -
connect (111: Connection refused) Cannot initiate the connection to
us.archive.ubuntu.com:443 (2001:67c:1562::15). - connect (101: Network
is unreachable) Could not connect to us.archive.ubuntu.com:443
(91.189.91.38). - connect (111: Connection refused) Cannot initiate the
connection to us.archive.ubuntu.com:443 (2001:67c:1562::18). - connect
(101: Network is unreachable)
Err:4 https://us.archive.ubuntu.com/ubuntu jammy-backports InRelease
Cannot initiate the connection to us.archive.ubuntu.com:443
(2001:67c:1562::15). - connect (101: Network is unreachable) Cannot
initiate the connection to us.archive.ubuntu.com:443
(2001:67c:1562::18). - connect (101: Network is unreachable)
All packages are up to date.
W: Failed to fetch
https://us.archive.ubuntu.com/ubuntu/dists/jammy/InRelease Temporary
failure resolving 'us.archive.ubuntu.com'
W: Failed to fetch
https://us.archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease Could
not connect to us.archive.ubuntu.com:443 (91.189.91.39). - connect (111:
Connection refused) Cannot initiate the connection to
us.archive.ubuntu.com:443 (2001:67c:1562::15). - connect (101: Network
is unreachable) Could not connect to us.archive.ubuntu.com:443
(91.189.91.38). - connect (111: Connection refused) Cannot initiate the
connection to us.archive.ubuntu.com:443 (2001:67c:1562::18). - connect
(101: Network is unreachable)
W: Failed to fetch
https://us.archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease
Cannot initiate the connection to us.archive.ubuntu.com:443
(2001:67c:1562::15). - connect (101: Network is unreachable) Cannot
initiate the connection to us.archive.ubuntu.com:443
(2001:67c:1562::18). - connect (101: Network is unreachable)
W: Failed to fetch
https://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease
Temporary failure resolving 'security.ubuntu.com'
W: Some index files failed to download. They have been ignored, or old
ones used instead
==========
The same procedure was tried on a plain Ubuntu machine. It
produced very similar results.
The "Some index files failed to download. They have been ignored,
or old ones used instead" is not a real attention grabber as an error
message and Is pretty much all that might be easily visible with more
common update methods.
==========
Tim,
This resolution is MYSTERIOUS to me. If you have ideas as to why
it might have worked I would appreciate your input. While a similar
approach fails with Ubuntu and Xubuntu is not so mystifying ... It
would appear that their distribution is just not able to deal with
"https://" unlike Debian.
I will now try a clean install of Debian ... I expect some
problems and should have added infornation for you by early next week.
Much thanks,
WILLIAM O RICHMOND
wor...@windstream.net
You can change the apt sources.list to use 'https' instead of
'http' to potentially avoid some problems with external interference
(although, some interference is considered good interference, so this
isn't a default in Debian for now). A VPN would indeed eliminate far
more of potential external interference, but for now that seems like
overkill.
I got a Debian installation together ( archived ssd ) and edited
the "/etc/apt/services.list" file. I then did "sudo apt update" which
listed 187 items. I followed this with "sudo apt upgrade" which
miraculously downloaded and installed all 187 items. After rebooting
this machine with "shutdown -r now" {amazing after the amount of time I
had put in these last 2-3 months} it worked properly. I then did a
"sudo apt install a2ps", a " sudo apt install gv" and a "sudo apt
install aptitude". I followed this with "sudo aptitude" and selected
"openssh server" with the shift/+ followed by g and g. After this
completed installation and I had exited from aptitude and rebooted I
tested this by doing "ssh orville@andy". After logging in to andy I did
"ssh orville@elmer" and was able to log in to elmer.
While this is not an extensive test it seems that all on Debian
was now working.
==========
Unless I understand why this happened I will continue to consider
a VPN.
==========
The current “/etc/apt/sources.list” file on elmer --- the current Debian
makchine.
orville@elmer:/etc/apt$ cat sources.list
# See https://wiki.debian.org/SourcesList for more information.
deb https://deb.debian.org/debian bullseye main
deb-src https://deb.debian.org/debian bullseye main
deb https://deb.debian.org/debian bullseye-updates main
deb-src https://deb.debian.org/debian bullseye-updates main
deb https://security.debian.org/debian-security/ bullseye-security main
deb-src https://security.debian.org/debian-security/ bullseye-security main
==========
Xubuntu with unmodified “/etc/apt/sources.list and unmodified
“/etc/apt/sources.list.distUpgrade”
root@andy:/etc/apt# apt update
Err:1 http://security.ubuntu.com/ubuntu jammy-security InRelease
Temporary failure resolving 'security.ubuntu.com'
Err:2 http://us.archive.ubuntu.com/ubuntu jammy InRelease
Connection failed [IP: 91.189.91.39 80]
Err:3 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease
Connection failed [IP: 91.189.91.38 80]
Err:4 http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease
Connection failed [IP: 91.189.91.39 80]
Reading package lists... Done
Building dependency tree
Reading state information... Done
Building dependency tree
All packages are up to date.
W: Failed to fetch
http://us.archive.ubuntu.com/ubuntu/dists/jammy/InRelease Connection
failed [IP: 91.189.91.39 80]
W: Failed to fetch
http://us.archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease
Connection failed [IP: 91.189.91.38 80]
W: Failed to fetch
http://us.archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease
Connection failed [IP: 91.189.91.39 80]
W: Failed to fetch
http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease
Temporary failure resolving 'security.ubuntu.com'
W: Some index files failed to download. They have been ignored, or old
ones used instead.
Xubuntu with all “http://” replaced with “https://”
root@andy:/etc/apt# apt update
Err:1 https://security.ubuntu.com/ubuntu jammy-security InRelease
Temporary failure resolving 'security.ubuntu.com'
Err:2 https://us.archive.ubuntu.com/ubuntu jammy InRelease
Temporary failure resolving 'us.archive.ubuntu.com'
Err:3 https://us.archive.ubuntu.com/ubuntu jammy-updates InRelease
Could not connect to us.archive.ubuntu.com:443 (91.189.91.39). -
connect (111: Connection refused) Cannot initiate the connection to
us.archive.ubuntu.com:443 (2001:67c:1562::15). - connect (101: Network
is unreachable) Could not connect to us.archive.ubuntu.com:443
(91.189.91.38). - connect (111: Connection refused) Cannot initiate the
connection to us.archive.ubuntu.com:443 (2001:67c:1562::18). - connect
(101: Network is unreachable)
Err:4 https://us.archive.ubuntu.com/ubuntu jammy-backports InRelease
Cannot initiate the connection to us.archive.ubuntu.com:443
(2001:67c:1562::15). - connect (101: Network is unreachable) Cannot
initiate the connection to us.archive.ubuntu.com:443
(2001:67c:1562::18). - connect (101: Network is unreachable)
Reading package lists... Done
Building dependency tree
Reading state information... Done
Building dependency tree
All packages are up to date.
W: Failed to fetch
https://us.archive.ubuntu.com/ubuntu/dists/jammy/InRelease Temporary
failure resolving 'us.archive.ubuntu.com'
W: Failed to fetch
https://us.archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease Could
not connect to us.archive.ubuntu.com:443 (91.189.91.39). - connect (111:
Connection refused) Cannot initiate the connection to
us.archive.ubuntu.com:443 (2001:67c:1562::15). - connect (101: Network
is unreachable) Could not connect to us.archive.ubuntu.com:443
(91.189.91.38). - connect (111: Connection refused) Cannot initiate the
connection to us.archive.ubuntu.com:443 (2001:67c:1562::18). - connect
(101: Network is unreachable)
W: Failed to fetch
https://us.archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease
Cannot initiate the connection to us.archive.ubuntu.com:443
(2001:67c:1562::15). - connect (101: Network is unreachable) Cannot
initiate the connection to us.archive.ubuntu.com:443
(2001:67c:1562::18). - connect (101: Network is unreachable)
W: Failed to fetch
https://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease
Temporary failure resolving 'security.ubuntu.com'
W: Some index files failed to download. They have been ignored, or old
ones used instead
==========
The same procedure was tried on a plain Ubuntu machine. It
produced very similar results.
The "Some index files failed to download. They have been ignored,
or old ones used instead" is not a real attention grabber as an error
message and Is pretty much all that might be easily visible with more
common update methods.
==========
Tim,
This resolution is MYSTERIOUS to me. If you have ideas as to why
it might have worked I would appreciate your input. While a similar
approach fails with Ubuntu and Xubuntu is not so mystifying ... It
would appear that their distribution is just not able to deal with
"https://" unlike Debian.
I will now try a clean install of Debian ... I expect some
problems and should have added infornation for you by early next week.
Much thanks,
WILLIAM O RICHMOND
wor...@windstream.net
0 new messages