Issue #5319 has been updated by Nigel Kersten.
"At times there are packages with catastrophic failure modes when they are run noninteractively, particularly when working with dpkg" Is the bug here that the dpkg provider doesn't set DEBCONF_FRONTEND to be non-interactive? even though the apt and aptitude providers do? If a package has a catastrophic failure when run non-interactively and you've set DEBCONF FRONTEND, isn't that a bug in the package, not in Puppet? ---------------------------------------- Feature #5319: ensure => selected for packages requiring interactive installation (dpkg/apt provider at least) https://projects.puppetlabs.com/issues/5319 Author: Nick Moffitt Status: Needs design decision Priority: Normal Assignee: Nigel Kersten Category: package Target version: Affected Puppet version: Keywords: Branch: At times there are packages with catastrophic failure modes when they are run noninteractively, particularly when working with dpkg. As a result I propose the following option in package providers, presented from a dpkg standpoint. If a package resource is ensure => selected, it will have exactly the same status behavior as ensure => installed, but the installation process will run 'echo "${packagename} install" | /usr/bin/dpkg --set-selections'. This will cause the package to be installed the next time an administrator interactively runs "apt-get dselect-upgrade". This allows configuration changes for a particular package to be held back until that package is installed interactively. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
