Bug#984846: netcfg: Default hostname hardcoded in netcfg-common

2021-03-09 Thread Raphael Hertzog
Hi, Le mardi 09 mars 2021, Cyril Brulebois a écrit : > My first reaction was “we could make that configurable on a per-vendor > fashion” (e.g. via debian/rules) but reading you are already patching > debian/netcfg-common.templates, why aren't you patching the two harcoded > locations in the first

Bug#984846: netcfg: Default hostname hardcoded in netcfg-common

2021-03-09 Thread Cyril Brulebois
Hello, Arnaud Rebillout (2021-03-09): > Dear Maintainer, > > the default hostname "debian" is hardcoded in two places in the file > netcfg-common.c: > > https://salsa.debian.org/installer-team/netcfg/-/blob/master/netcfg-common.c#L1043 > https://salsa.debian.org/installer-team/netcfg/-/blob/mas

Re: Merge request created [Re: Use isenkram to get around the firmware problem?]

2021-03-09 Thread Cyril Brulebois
Brian Potkin (2021-03-09): > On Mon 08 Mar 2021 at 22:41:53 +0100, Holger Wansing wrote: > > At the bare minimum, I have created a merge request for my > > "introduce a dialog to enter packages for firmware installation" > > approach, so it is at least officially documented somewhere... I have no

Re: Merge request created [Re: Use isenkram to get around the firmware problem?]

2021-03-09 Thread Brian Potkin
On Mon 08 Mar 2021 at 22:41:53 +0100, Holger Wansing wrote: > Hi, > > Holger Wansing wrote (Sun, 7 Mar 2021 17:02:06 +0100): > > And for the (graphics) firmware problem, isenkram is of no help as it > > seems, > > at least for Bullseye. > > I have reached the end of my path on this issue. >