Issue #5319 has been updated by Nigel Kersten.
Nick Moffitt wrote: > So puppet will not officially support anything but perfect packages? That > seems limiting. That's not quite a fair characterization of our position Nick. As Peter said, it opens up a whole can of worms once we do this, because it breaks a fundamental assumption in Puppet. The assumption is that we are delivering a catalog that is internally self-consistent. You appear to be saying something like this. "I want State A and State B, even though State A and State B are in conflict with one another" The right answer is in #4067. Puppet needs to be made aware of the conflict, and represent the actual state of the world, which is that these things are in conflict, and there is no correct answer. Let me move away from packages and imagine we're talking about files. Do you expect Puppet to be able to cope with two File resources, one which ensures the file is absent, and another that ensures the file is present? We obviously don't have a perfect line in the sand here. The reality is that we're sysadmins and we work in a messy field, full of complications and inconsistencies. We need to absorb *some* of this in Puppet, but we can't absorb too much of it, otherwise we end up breaking the fundamental way Puppet works. I'm not yet convinced we need to absorb this particular case, but our dialog is still open here :) You haven't addressed the responsefile option yet either. Why can't you have a human work out what the correct responses are to make a package install work (and leave you in a consistent state) and then represent those responses in the responsefile? ---------------------------------------- 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.
