[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#273056: D-I: Network / sources.list configuration issues using apt-proxy.



Package: debian-installer
Version: rc1
Severity: minor

I'm currently in the process of installing Sarge on a workstation, using sarge-i386-netinst.iso retrieved from

http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/i386/rc1/sarge-i386-netinst.iso

today.

I have both a Squid and an apt-proxy server running in this LAN.

I decided to enter my sources.list manually. The first time round, I mistyped. I got my second chance, very good! So far, so smooth sailing.

Pretty much immediately thereafter, I was asked about which HTTP proxy to use.

What's that about? The question left me confused. (Maybe I didn't read the screen carefully enough. If that is the case, please pardon me.)

I declined giving an answer, as I did not understand why that would be useful. As a matter of fact, out of sheer configuration lazyness you can actually reach the apt-proxy through the Squid. But I certainly do not want the new box to actually do that.

Only a moment later it became clear to me that this question was asked on behalf of Debian security updates.

This is needlessly confusing.


My suggestion:

In the best Debian tradition, D-I should assume a person who edits manually knows what she is doing.

Provide a template, yes. Drop the security line into sources.list, with an appropriate commentary, *before* the editor is fired, yes. Once we are at it, please add example lines for http_proxy and ftp_proxy, as comments. And then leave it at that, whatever comes out of the editor.


Regards, and thank you for providing fine software

Andreas
--
Dr. Andreas Krüger, andreas.krueger@dv-ratio.com
GPG/PGP Fingerprint 8063 4A9B 362D 4220 A546  14C1 EA19 AADC FD44 5EB7
DV-RATIO Nordwest GmbH, Tel.: +49 211 577 996-0, Fax:  +49 211 559 1617
Leostraße 31, 40545 Düsseldorf, Germany

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: