Hi,
But for this to work, the Puppet run needs to run aptitude update to
pick up the new package name. Running the update periodically isn't
enough, but running an update on every catalog run is just overkill.
I understand your concern here, but have you done the timing tests?
How long
For the past week, I have been trying to figure out the best way to do
package management with Puppet on an Ubuntu system. I have studied many
solutons I found on the web, but none of them seem to do exactly what I want.
I am not sure if somebody proposed this already, but may be you can
use
On Sep 7, 2010, at 1:22 AM, Martijn Grendelman wrote:
Hi,
But for this to work, the Puppet run needs to run aptitude update to
pick up the new package name. Running the update periodically isn't
enough, but running an update on every catalog run is just overkill.
I understand your
Patrick kc7...@gmail.com writes:
On Sep 7, 2010, at 1:22 AM, Martijn Grendelman wrote:
But for this to work, the Puppet run needs to run aptitude update to pick
up the new package name. Running the update periodically isn't enough,
but running an update on every catalog run is just overkill.
On 05-09-10 12:02, Marcin Owsiany wrote:
On Tue, Aug 31, 2010 at 04:03:35PM +0200, Martijn Grendelman wrote:
What I would like, is for Puppet to run `aptitude update` before it
installs or upgrades packages.
FYI you're likely to encounter problems when using aptitude provider for
package
On Tue, Aug 31, 2010 at 3:35 PM, Martijn Grendelman
mart...@grendelman.net wrote:
But for this to work, the Puppet run needs to run aptitude update to
pick up the new package name. Running the update periodically isn't
enough, but running an update on every catalog run is just overkill.
I
On 01.09.2010 01:35, Martijn Grendelman wrote:
Mathias Gug schreef:
I am not sure how I said I want to do an update before /every/ package
install. Once at the start of a Puppet-run, /IF/ one or more packages
need to be installed, would suffice.
You may run into a chicken-egg problem.
On Mon, Sep 6, 2010 at 10:56 AM, Silviu Paragina sil...@paragina.ro wrote:
As it was said earlier if you have a ensure = latest you should probably
have (also) a cron job for updates.
I think it's much more difficult to manage multiple schedules, and to
deal with inconsistencies when people
On 06.09.2010 21:03, Nigel Kersten wrote:
On Mon, Sep 6, 2010 at 10:56 AM, Silviu Paraginasil...@paragina.ro wrote:
As it was said earlier if you have a ensure = latest you should probably
have (also) a cron job for updates.
I think it's much more difficult to manage multiple schedules,
On Mon, Sep 6, 2010 at 11:52 AM, Silviu Paragina sil...@paragina.ro wrote:
On 06.09.2010 21:03, Nigel Kersten wrote:
On Mon, Sep 6, 2010 at 10:56 AM, Silviu Paraginasil...@paragina.ro
wrote:
As it was said earlier if you have a ensure = latest you should
probably
have (also) a cron job
On Tue, Aug 31, 2010 at 04:03:35PM +0200, Martijn Grendelman wrote:
What I would like, is for Puppet to run `aptitude update` before it
installs or upgrades packages.
FYI you're likely to encounter problems when using aptitude provider for
package management. See Debian bugs #445034 #445035
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/31/2010 06:41 PM, Trevor Hemsley wrote:
Actually nothing to do with the content of this post but is anyone else
getting a lot of mails from puppet-users at least twice? This particular
one came through 3 times with the same timestamp and
On Tue, Aug 31, 2010 at 10:03 AM, Martijn Grendelman
mart...@grendelman.net wrote:
What I would like, is for Puppet to run `aptitude update` before it
installs or upgrades packages. That doesn't seem out of the ordinary to
me, but I can't make it work in Puppet.
The run stages of puppet 2.6
On Tue, Aug 31, 2010 at 7:03 AM, Martijn Grendelman
mart...@grendelman.net wrote:
Hi,
For the past week, I have been trying to figure out the best way to do
package management with Puppet on an Ubuntu system. I have studied many
solutons I found on the web, but none of them seem to do exactly
Hi Nigel Kersten,
Thank you for your elaborate answer. I am not sure how to proceed, though...
What I would like, is for Puppet to run `aptitude update` before it
installs or upgrades packages. That doesn't seem out of the ordinary to
me, but I can't make it work in Puppet.
The approach I
On Tue, Aug 31, 2010 at 1:02 PM, Martijn Grendelman
mart...@grendelman.net wrote:
Hi Nigel Kersten,
Thank you for your elaborate answer. I am not sure how to proceed, though...
What I would like, is for Puppet to run `aptitude update` before it
installs or upgrades packages. That doesn't
* Martijn Grendelman martijn at grendelman.net [2010/08/31 22:02]:
What I would like, is for Puppet to run `aptitude update` before
it installs or upgrades packages. That doesn't seem out of the
ordinary to me, but I can't make it work in Puppet.
I would do the `aptitude update` in cron,
On Tue, Aug 31, 2010 at 1:41 PM, Darren Chamberlain dar...@boston.com wrote:
* Martijn Grendelman martijn at grendelman.net [2010/08/31 22:02]:
What I would like, is for Puppet to run `aptitude update` before
it installs or upgrades packages. That doesn't seem out of the
ordinary to me, but I
Hi,
Excerpts from Martijn Grendelman's message of Tue Aug 31 16:02:43 -0400 2010:
Hi Nigel Kersten,
What I would like, is for Puppet to run `aptitude update` before it
installs or upgrades packages. That doesn't seem out of the ordinary to
me, but I can't make it work in Puppet.
The
Mathias Gug schreef:
I am not sure how I said I want to do an update before /every/ package
install. Once at the start of a Puppet-run, /IF/ one or more packages
need to be installed, would suffice.
You may run into a chicken-egg problem. Packages that are configured as
ensure = latest can
20 matches
Mail list logo
