Bug#851504: freedombox-setup: debconf prompts during install, and default answers lead to setup failures

Just to mention, an alternative to the patches I proposed: We could move the LDAP setup (admin setup and creating organizational units) from setup to first-run. This would only require some changes in the plinth package. This would also fix the CI issue (first-run isn't tested by CI). And should

Bug#851504: freedombox-setup: debconf prompts during install, and default answers lead to setup failures

On Tue, 17 Jan 2017 08:57:22 +0100 Petter Reinholdtsen wrote: > > Good. Was there any leftover processes after the setup? The purpose of > policy-rc.d is to not leave any stray processes behind. :) > In that case, I would suggest to modify setup, but keep a copy of the

Bug#851504: freedombox-setup: debconf prompts during install, and default answers lead to setup failures

[James Valleroy] > I'm able to run setup successfully (with this patch) in a chroot (setup > using schroot). > > I also tested building images using freedom-maker with the patched > freedombox-setup. Good. Was there any leftover processes after the setup? The purpose of policy-rc.d is to not

Bug#851504: freedombox-setup: debconf prompts during install, and default answers lead to setup failures

On Mon, 16 Jan 2017 16:48:05 +0100 Petter Reinholdtsen wrote: > [James Valleroy] > > I would like to propose the following change: Don't set policy-rc.d in > > the setup script in this package. > > Will this affect the autopkgtest script? What about building freedombox > in a

Bug#851504: freedombox-setup: debconf prompts during install, and default answers lead to setup failures

On 01/16/2017 09:18 PM, Petter Reinholdtsen wrote: > [James Valleroy] >> I would like to propose the following change: Don't set policy-rc.d >> in the setup script in this package. > > Will this affect the autopkgtest script? We are running 'setup' script from tests can this will ready to daemon

Bug#851504: freedombox-setup: debconf prompts during install, and default answers lead to setup failures

[James Valleroy] > I would like to propose the following change: Don't set policy-rc.d in > the setup script in this package. Will this affect the autopkgtest script? What about building freedombox in a chroot? Does it matter? -- Happy hacking Petter Reinholdtsen

Bug#851504: freedombox-setup: debconf prompts during install, and default answers lead to setup failures

I would like to propose the following change: Don't set policy-rc.d in the setup script in this package. I believe the policy-rc.d setting was added for images built using freedom-maker. But freedom-maker sets it's own policy-rc.d:

Bug#851504: freedombox-setup: debconf prompts during install, and default answers lead to setup failures

Some more information: 1) If I don't install a desktop environment, then the issue still occurs. But the default debconf settings for nslcd look more normal in this case. 2) I noticed that running "plinth --setup-no-install users" did not have the same error. So I tried removing all the

Bug#851504: freedombox-setup: debconf prompts during install, and default answers lead to setup failures

Just a note, the debconf prompts for these packages can be avoided by setting these environment variables: export DEBIAN_FRONTEND=noninteractive export DEBCONF_NONINTERACTIVE_SEEN=true We may want to add these to the install instructions (https://wiki.debian.org/FreedomBox/Hardware/Debian). But

Bug#851504: freedombox-setup: debconf prompts during install, and default answers lead to setup failures

Package: freedombox-setup Severity: important I tested install/setup of freedombox-setup on a fresh Debian install. I used Stretch RC1 installer and selected XFCE desktop during the install. When I install freedombox-setup, I get several debconf prompts (default values listed in parens): *