This bug renders the package unusable so shouldn't the severity be
raised to "grave" ?
On Wed, 4 Feb 2026 09:26:04 +0000 Steven Maddox
<[email protected]> wrote:
Presuming the d-i / netinst experience undergoes any kind of continuous
integration tests... is using PPPoE part of those tests?
It just feels both oddly very well documented ... yet
simultaneously unloved ?
Maybe because unlike "pure" d-i packages it is not maintained by the d-i
team, being part of the ppp source package ?
I never got why this is an optional module anyway? Why not just make it
part of the network autoconfiguration step?
PPPoE requires a username and password, it cannot be autoconfigured.
i.e. if local-link/ipv6-autoconf/dhcp has failed then look for a PPPoE
AC instead (which now thanks to bug #1070753 takes a mere blip of
time)... and if one is found then ask for user/pass.
By the way, this bug [1] has not been closed yet even though the
reported issue is fixed. Same with bug #1005142 [2] which reported the
now fixed "pppoe-discovery -A" issue.
Or if you don't want it part of the autoconfiguration, then after that
has failed and you've currently got the option to 'retry', or 'retry
with a dhcp hostname', or 'configure manually'... just add a new option...
'Retry network autoconfiguration with PPPoE'IMO this is unrelated with this bug report. Wishlist bug #403963 [3]
already suggested something similar almost two decades ago.
[1] <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070753>
[2] <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005142>
[3] <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=403963>
