Package: security.debian.org
Severity: normal
I haven't been able to upgrade my etch system with the recent security
updates since Friday, although the etch-and-a-half upgrade proceeded
normally on Saturday. I use aptitude. I think the following output
should summarize the problem nicely:
...
Get:2 http://security.debian.org etch/updates Release.gpg [189B]
Get:4 http://security.debian.org etch/updates Release [37.6kB]
Get:7 http://security.debian.org etch/updates/main Packages [264kB]
Get:10 http://security.debian.org etch/updates/contrib Packages [3926B]
Get:12 http://security.debian.org etch/updates/non-free Packages [1420B]
Get:14 http://security.debian.org etch/updates/main Sources [43.0kB]
Get:15 http://security.debian.org etch/updates/contrib Sources [1168B]
Get:16 http://security.debian.org etch/updates/non-free Sources [1176B]
...
The following packages will be upgraded:
iceweasel [2.0.0.15-0etch1 -> 2.0.0.16-0etch1] iceweasel-gnome-support
[2.0.0.15-0etch1 -> 2.0.0.16-0etch1]
libxul-common [1.8.0.15~pre080323b-0etch2 -> 1.8.0.15~pre080614d-0etch1]
libxul0d [1.8.0.15~pre080323b-0etch2 -> 1.8.0.15~pre080614d-0etch1]
4 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 17.7MB of archives. After unpacking 8192B will be used.
Get:1 http://security.debian.org etch/updates/main iceweasel-gnome-support
2.0.0.16-0etch1 [87.8kB]
Err http://security.debian.org etch/updates/main iceweasel 2.0.0.16-0etch1
Connection failed [IP: 212.211.132.250 80]
Err http://security.debian.org etch/updates/main libxul0d
1.8.0.15~pre080614d-0etch1
Connection failed [IP: 130.89.175.54 80]
Get:2 http://security.debian.org etch/updates/main libxul-common
1.8.0.15~pre080614d-0etch1 [1087kB]
Fetched 1174kB in 4m3s (4815B/s)
Note that there aren't any problems getting the metadata, and I was able
to get the iceweasel-gnome-support and libxul-common without a hitch.
However, I have consistently gotten the "Connection failed" message for
the iceweasel and libxul0d packages since Friday.
I noticed that during my repeated attempts of "aptitude updates;
aptitude upgrade" on Friday, that there were key issues that seemed to
go away the next cycle.
Any ideas of what might be causing this problem?
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.utf8)
--
Bill Wohler <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
