On Tue, Jan 14, 2014 at 10:22 AM, Mike Gaboury wrote:
> That helped. Thanks. The key was to have the version in the title. I
> had 'Puppet' and needed 'Puppet 3.4.2'.
>
This works because when puppet is installed, its DisplayName property in
the registry is "Puppet". So when you specify "Puppe
That helped. Thanks. The key was to have the version in the title. I had
'Puppet' and needed 'Puppet 3.4.2'.
So this appears to be an inconsistency or, more likely, a lack of
understanding on Windows packages and versioning (I'm a Linux guy). I have
a module to deploy Java. To get that to
I use:
if ( $puppetversion != "3.3.1" ) {
package { "Puppet 3.3.1":
source => "software01\\autorepo\$\\Puppet\\puppet-3.3.1.msi",
install_options => [ '/quiet',
'/norestart','PUPPET_MASTER_SERVER=puppet.example.dk']
}
}
to ensure a specific version on all windows hosts.
--
Yo
I am trying to update Puppet itself and the new version is not installing.
It appears that the UpgradeCode between Puppet 3.2.3 and 3.4.2 are
identical {2AD3D11C-61B3-4710-B106-B4FDEC5FA358}. Is this expected or an
oversight? If it is expected, how is the best way to upgrade Puppet with
Puppe
Dear Rob and Josh,
Indeed it was all about a custom build msi being unable to upgrade himself.
All the packages have the same UpgradeCode, so I will keep investigating.
Thank you both for your time.
Lorenzo
On Thursday, October 31, 2013 5:00:24 AM UTC+1, Josh Cooper wrote:
>
> Hi Lorenzo,
>
>
Hi Lorenzo,
On Wed, Oct 30, 2013 at 11:54 AM, Rob Reynolds wrote:
> I am curious if you have also looked at the other package providers that
> are out there - http://forge.puppetlabs.com/modules?q=windows+package
> I can tell you that the chocolatey provider does allow ensure => latest.
> Also
I am curious if you have also looked at the other package providers that
are out there - http://forge.puppetlabs.com/modules?q=windows+package
I can tell you that the chocolatey provider does allow ensure => latest.
Also the version on github is being improved to add source in addition to
other thi
Thanks Rob for guiding me.
The ensure => latest feature is not ready yet, because it requires an
upgradeable provider.
What seems to be solved is ensure => '0.0.1'.
At the link you provide they made the windows provider versionable. (That
requires facter version => 1.7.3-rc1)
I managed to ap
Take a look at https://projects.puppetlabs.com/issues/21133. I'm not sure
if there is an ensure => latest yet or not.
On Wed, Oct 23, 2013 at 9:12 AM, Lorenzo Jesús Cubero
wrote:
>
> Hey! I would like to be able of upgrade a windows application just copying
> the .msi file into a ../module/files
Hey! I would like to be able of upgrade a windows application just copying
the .msi file into a ../module/files directory, without having to modify
any manifest.
Something like:
file { 'C:\\files\\packages\\Package.msi':
ensure => present,
source =>
10 matches
Mail list logo
