Patrick 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 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 underst
> 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
us
Hi,
Just to let you know how I implemented it in the end. Earlier I wrote:
> I have now solved my problem by using a custom provider for packages, that
> is based on the aptitude provider, but simply adds this:
>
> # See if we need to run aptitude update before installing this package
> if not F
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?
>
> H
On Mon, Sep 6, 2010 at 11:52 AM, Silviu Paragina wrote:
> On 06.09.2010 21:03, Nigel Kersten wrote:
>>
>> On Mon, Sep 6, 2010 at 10:56 AM, Silviu Paragina
>> wrote:
>>
>>> As it was said earlier if you have a ensure => latest you should
>>> probably
>>> have (also) a cron job for updates.
>>
>>
On 06.09.2010 21:03, Nigel Kersten wrote:
On Mon, Sep 6, 2010 at 10:56 AM, Silviu Paragina 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 inc
On Mon, Sep 6, 2010 at 10:56 AM, Silviu Paragina 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 manually run Puppe
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. Packages
On Tue, Aug 31, 2010 at 3:35 PM, 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.
I understand your concer
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
> pac
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
r
-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 s
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 => l
Nigel Kersten schreef:
> So I don't have it refreshonly. I'm perfectly happy with apt-get
> update etc running on every puppet run.
Ah, that explains ;-) But I was hoping that wouldn't be necessary.
> Are you using modules and environments? You will need to make sure the
> class is included somew
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
On Tue, Aug 31, 2010 at 1:41 PM, Darren Chamberlain wrote:
> * Martijn Grendelman [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
* Martijn Grendelman [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, outside of puppet, and
manag
On Tue, Aug 31, 2010 at 1:02 PM, Martijn Grendelman
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 seem out of the
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 app
On Tue, Aug 31, 2010 at 7:03 AM, Martijn Grendelman
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 what I want.
>
>
On Tue, Aug 31, 2010 at 10:03 AM, Martijn Grendelman
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 addresses this need.
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 same Message-Id.
On 31/08/2010 15:03, Martijn Grendelman wrote:
> Hi,
>
> For the past week, I have
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 what I want.
Among other things, I have tried everything that is discussed here:
http
24 matches
Mail list logo
