Bug#388572: marked as done (debian-installer won't let me select a local apt-proxy mirror)
Your message dated Sun, 24 Sep 2006 00:00:07 +0200
with message-id <1159048807.1240.221.camel@localhost>
and subject line my apologies
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: debian-installer
Version: no idea. Netinstall image was DL'ed on 20-Sep-2006
The way you're expected to enter a server and path differs from how
sources are defined in every other place; it's not apparent how they are
translated into a sources.list entry.
After trying several combinations of "server" and "path" statements to
no avail, I resigned and switched to the second console in an attempt to
edit the sources.list manually. In vain, though, as the installer would
immediately uncomment my changes in an attempt to make a clean start.
Good intentions notwithstanding, I found this to be annoying.
Please bring back the option to edit the sources.list file; while it may
look scary to a beginner, even a half-experienced user who has no idea
how sources work (like me) could still add a valid entry simply by
copying it verbatim from another source.
regards,
Schnobs
--- End Message ---
--- Begin Message ---
The actual problem was an old (and long since closed) apt-proxy bug:
#374405: Incompatible with full URL HTTP requests from recent apt
versions
An update of the apt-proxy machine would be overdue, it seems.
I still find it interesting that while installing the base system,
outdated apt-proxy served well -- apparently the old way (no full URLs)
is still being used during that step.
However, the actual issue of the installer not getting along with my
apt-proxy was in no way a bug in apt-setup, but my own damn fault. I'm
sorry for wasting your time.
regards,
Schnobs
--- End Message ---
Reply to: