issue with configuring a debian installation with debconf set to low priority both at the beginning and after the base system is installed

2021-04-06 Thread Nick Gawronski 
Hi, I had written about this to mailing lists several years ago but 
never got the proper bug number as I think the bug was reported.  I 
often like to run the installation at low priority so I can configure 
everything correctly at the start of the installation process and so 
that when the system reboots into the newly installed system things are 
all setup and ready to go. After the base system is installed I then 
exicute a shell and chroot into /target and run dpkg-reconfigure adduser 
to tell it not to have system readable home directories.  If I then do 
dpkg-reconfigure debconf still in the chroot and set it to low priority 
the installation continues up until it gets to the pam profiles 
selection screen.  No matter what I select here even when everything is 
selected the system tells me that no pam profiles are enabled for the 
system and would grant all users access with authenticating which is not 
allowed.  I can not preceed past this screen as even trying to go to 
another shell and change the priority back to medium will not work as I 
am still stuck at that screen when I return to the console.  I also 
think that if a user sets the priority to low in the installation 
process that at least for the installation even in the target the 
priority remain at that setting and if a user wants to change it back to 
medium they could do this after the installation.  How would I be able 
to submit further information on how to get the proper information to 
someone so it could be looked into and get fixed?  Nick Gawronski

Re: issue with configuring a debian installation with debconf set to low priority both at the beginning and after the base system is installed

2021-04-06 Thread Samuel Thibault 
Nick Gawronski, le mar. 06 avril 2021 16:22:27 -0500, a ecrit:
> How would I be able to submit further information on how to get the
> proper information to someone so it could be looked into and get
> fixed?

You can report a bug against the debian-installer package. Sending what
you sent in your previous email should be already a good start.

Samuel