I
know Debian is quite conservative about package versions so I can imagine
many platforms that are in no need for this feature but I also think has to
be quite some people in similar situation...
The puppet version we are currently using is 2.7.21-1puppetlabs1 and for
now it's not running in
t option for us.
Thanks!
sjr
On Thursday, May 16, 2013 7:25:57 AM UTC+2, Lelutin wrote:
>
> Hey there,
>
> On 15/05/13 08:24 PM, sjr wrote:
> > The thing is we would like to be able to specify a version for the
> > package and tell dpkg to hold it to prevent unwanted upgrades (
ling a new package I can enforce a version and hold it. But from my
minor mod to a proper patch...there is still much work to do, so that's why
I was looking for comments, opinions, and so on about this feature
I probably didn't explain myself well enough in my first email :-)
sjr.
Thanks!
I'll continue the discussion there after opening the issue :-)
sjr.
On Saturday, May 18, 2013 1:18:07 AM UTC+2, Lelutin wrote:
>
> On 17/05/13 03:45 AM, sjr wrote:
> > I have done a quick&dirty hack to the APT provider and it works when
> > installing a
Hi,
I've been doing some tests with some internal methods just to mess a little
and learn a bit about puppet internals but found myself in a situation
which I don't really understand and I was hoping someone around could help
me to get it.
I have a test module with the following init.pp:
clas
emplate is evaluated before all this resources are
present in the catalog...am I wrong? Is that expected behavior?
Thanks.
Sergio.
On Tuesday, September 10, 2013 3:23:47 PM UTC+2, jcbollinger wrote:
>
>
>
> On Monday, September 9, 2013 6:13:46 PM UTC-5, sjr wrote:
>>
>>
Hi John,
On Wednesday, September 11, 2013 3:35:07 PM UTC+2, jcbollinger wrote:
>
>
>
> On Tuesday, September 10, 2013 8:53:10 AM UTC-5, sjr wrote:
>>
>> Hi John,
>>
>> thanks for your answer, first of all I must say I just wanted to
>> experiment and
