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

Bug#895275: marked as done (debian-installer: Incorrect installer proxy suggested format)

Your message dated Wed, 23 Oct 2019 20:12:13 +0200
with message-id <20191023181132.hjlwykoewwwnxdgm@hupe>
and subject line unreproducible
has caused the Debian Bug report #895275,
regarding debian-installer: Incorrect installer proxy suggested format
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.)


-- 
895275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895275
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: debian-installer
Version: 20170615+deb9u3
Severity: minor

Dear Maintainer,

Installer from Debian 9.4 netinstall iso on "Configure the package manager" stage suggests HTTP proxy should be filled in the form of 
"http://[[user][:pass]@]host[:port]/";. But it will fail to work through proxy if you include trailing slash after port number. 
The correct form which works for proxy are without trailing slash, i.e. http://192.168.0.1:3128
Tested with proxy running polipo-1.0.4.1 on CentOS-6, other proxyies most likely are affected as well.

-- System Information:
Debian Release: 9.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-6-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message --- 
Hi,

testing here on several machines, the suggested proxy scheme works
fine.  In addition, nobody else seems to have that problem.
Therefore, I assume something else went wrong in your case and
I am closing this bug.  If it still applies in your case, please
reopen with more detailed information.

Best regards,

  Andi

--- End Message ---
Reply to: