Bug#873074: cdrom: Mirror chosen in expert install will not be written to sources.list

[Daniel]

Package: cdrom
Severity: normal
Tags: d-i

Dear Maintainer,

* What led up to the situation?

installed debian stretch dvd image (from usb flashdrive), used
installer in expert mode, chosen mirror ftp.halifax.rwth-aachen.de,
protocol http

* What was the outcome of this action?

After installation, there is an entry in file /etc/apt/sources.list
for the cd image but not for the mirror.

* What outcome did you expect instead?

mirror chosen during installation is written to sources.list


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

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

[Steve McIntyre]

Post by Daniel
Package: cdrom
Severity: normal
Tags: d-i
Dear Maintainer,
* What led up to the situation?
installed debian stretch dvd image (from usb flashdrive), used
installer in expert mode, chosen mirror ftp.halifax.rwth-aachen.de,
protocol http
* What was the outcome of this action?
After installation, there is an entry in file /etc/apt/sources.list
for the cd image but not for the mirror.
* What outcome did you expect instead?
mirror chosen during installation is written to sources.list

Hi Daniel,

I'd absolutely expect this to work in d-i as you expect. Could you
share the installer syslog from your machine please, so we can see
what's happened?

[Debian Bug Tracking System]

Your message dated Fri, 15 Sep 2023 15:41:25 +0100
with message-id <***@adam-barratt.org.uk>
and subject line Re: Bug#873074: cdrom: Mirror chosen in expert install will not be written to sources.list
has caused the Debian Bug report #873074,
regarding cdrom: Mirror chosen in expert install will not be written to sources.list
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 ***@bugs.debian.org
immediately.)