Bug#720345: marked as done ('apt-get update' considers connection failures non-transient)
Your message dated Thu, 27 Mar 2025 21:53:33 +0100
with message-id <613c8f87-fe6f-4444-b719-488eb0064c87@wp.pl>
and subject line Re: Bug#720345: 'apt-get update' considers connection failures non-transient
has caused the Debian Bug report #720345,
regarding 'apt-get update' considers connection failures non-transient
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
720345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720345
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: 'apt-get update' considers connection failures non-transient
- From: "Dustin J. Mitchell" <dustin@mozilla.com>
- Date: Tue, 20 Aug 2013 12:09:16 -0700 (PDT)
- Message-id: <2083644450.75362.1377025756441.JavaMail.zimbra@mozilla.com>
- In-reply-to: <1812206410.71873.1377024039016.JavaMail.zimbra@mozilla.com>
Package: apt
Version: 0.8.16~exp12ubuntu10.7
If a mirror fails in such a way as to trigger the "Unable to connect" error, it is not represented as a transient error.
To reproduce, add an unallocated IP to sources.list, e.g.,
deb http://10.26.57.199/repos/apt/foo precise dependencies main
for a repo that contains
then run apt-get update:
Ign http://10.26.57.199 precise InRelease
Err http://10.26.57.199 precise Release.gpg
Unable to connect to 10.26.57.199:http:
Ign http://10.26.57.199 precise Release
Ign http://10.26.57.199 precise/dependencies TranslationIndex
Ign http://10.26.57.199 precise/main TranslationIndex
Err http://10.26.57.199 precise/dependencies amd64 Packages
Unable to connect to 10.26.57.199:http:
Err http://10.26.57.199 precise/main amd64 Packages
Unable to connect to 10.26.57.199:http:
Err http://10.26.57.199 precise/dependencies i386 Packages
Unable to connect to 10.26.57.199:http:
Err http://10.26.57.199 precise/main i386 Packages
Unable to connect to 10.26.57.199:http:
Err http://10.26.57.199 precise/dependencies Translation-en
Unable to connect to 10.26.57.199:http:
Err http://10.26.57.199 precise/main Translation-en
Unable to connect to 10.26.57.199:http:
...
W: Failed to fetch http://10.26.57.199/repos/apt/puppetlabs/dists/precise/Release.gpg Unable to connect to 10.26.57.199:http:
W: Failed to fetch http://10.26.57.199/repos/apt/puppetlabs/dists/precise/dependencies/binary-amd64/Packages Unable to connect to 10.26.57.199:http:
W: Failed to fetch http://10.26.57.199/repos/apt/puppetlabs/dists/precise/main/binary-amd64/Packages Unable to connect to 10.26.57.199:http:
W: Failed to fetch http://10.26.57.199/repos/apt/puppetlabs/dists/precise/dependencies/binary-i386/Packages Unable to connect to 10.26.57.199:http:
W: Failed to fetch http://10.26.57.199/repos/apt/puppetlabs/dists/precise/main/binary-i386/Packages Unable to connect to 10.26.57.199:http:
W: Failed to fetch http://10.26.57.199/repos/apt/puppetlabs/dists/precise/dependencies/i18n/Translation-en Unable to connect to 10.26.57.199:http:
W: Failed to fetch http://10.26.57.199/repos/apt/puppetlabs/dists/precise/main/i18n/Translation-en Unable to connect to 10.26.57.199:http:
E: Some index files failed to download. They have been ignored, or old ones used instead.
[root@talos-linux64-ix-044.test.releng.scl3.mozilla.com ~]# echo $?
100
Expected result:
Exit status 0, since this is a transient failure of the host containing that repo.
http://anonscm.debian.org/loggerhead/apt/apt/debian-squeeze/view/head:/apt-pkg/algorithms.cc#L1495
should write "Some index files failed to download, they have been ignored, or old ones used instead." as a warning in that case.
Use case:
I have multiple mirrors of the debian repos used internally. Temporary failure of a single mirror should not cause 'apt-get update' to fail: that's why I have multiple mirrors!
Related links:
https://bugzilla.mozilla.org/show_bug.cgi?id=906785
--- End Message ---
--- Begin Message ---
Closing per information from my previous e-mail.
Kamil
--- End Message ---
Reply to: