Clearly not a problem caused by puppet but something I can't apparently deploy
with puppet unless someone has an idea.
Trying to automate a way to deploy mod_mono for apache
from CLI, the problem seems obvious...
apt-get install -y --assume-yes libapache2-mod-mono mono-apache-server
libmono-firebirdsql1.7-cil
a massive pile of packages installs and it finally arrives at the truth moment:
Configuration file `/etc/apache2/mods-available/mod_mono.conf'
==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : background this process to examine the situation
The default action is to keep your current version.
*** mod_mono.conf (Y/I/N/O/D/Z) [default=N] ?
So it appears that the same target, mod_mono.conf is being created both by
script and a file in the package itself and it appears that all of the '-y' or
'--assume-yes' logic in the command itself will not allow an install to
progress without an interactive answer to the question - the answer to which is
essentially meaningless because I can control the file anyway with puppet.
Anyone have an idea how to defeat well intentioned but defective packager logic?
--
Craig White ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ craig.wh...@ttiltd.com
1.800.869.6908 ~~~~~~~~~~~~~~~~~~~~~~~~~~~ www.ttiassessments.com
Need help communicating between generations at work to achieve your desired
success? Let us help!
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
