Bug#360717: installation-report: mirror selection not available for security updates
Package: installation-reports
Version: 2.14
Severity: normal
-- Package-specific info:
Boot method: network
Image version: http://cdimage.debian.org/cdimage/etch_di_beta2/i386/iso-cd/debian-testing-i386-netinst.iso (netinst 120MB)
Date: Mon, 03 Apr 2006 18:33:45 +0200
Machine: irrelevant information
Partitions: irrelevant information
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot: [O]
Detect network card: [O]
Configure network: [O]
Detect CD: [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives: [O]
Create file systems: [O]
Mount partitions: [O]
Install base system: [E]
Install boot loader: [ ]
Installed system ok: [ ]
I tried a network installation using an apt-proxy server on the LAN as
Debian mirror.
Before installing the base system, I'm asked to choose a mirror. This is
what I typed:
mirror:
http://apt-proxy:9999/
section:
/debian/
proxy:
<none>
The problem is that I'm not asked the Debian mirror I want to use for the
security updates. And unfortunately, the LAN is behind a proxy.
Therefore it is impossible to download anything from security.debian.org
because I specified no proxy for apt.
After a long time, the installer "said" it was unable to download from
security.debian.org ("great!"), and then suggest that I should solve
this problem later ("fine!"). But at this point, I didn't manage to
continue with the installation process. The arrows keys didn't seem to
work and the debian installer tried one more time to download packages
from security.debian.org.
On one hand I think that the user should be able to choose the security
updates mirror by himself.
On the other hand, the installer should let the user continue with the
installation process even if it couldn't fetch security packages.
For this point, I'll try one more time to be sure of whate really
happened. In fact, I don't remember exactly if the installer tried to
download the same packages one more time or tried something else...
--
pitchum
Reply to: