Hi,
is it possible that the packages for Debian Jessie are still not available
on the repository?
Please
see: http://apt.puppetlabs.com/dists/jessie/main/binary-amd64/Packages
I'm trying to install puppet on some new installed servers, and I couldn't
find the packages related to Debian
unattended-upgrades with the proper Allowed-Origins
and let the system upgrade the packages for you.
Cheers,
Raphaël
On Tuesday, February 24, 2015 at 4:28:32 PM UTC+1, Ximena Cardinali wrote:
Hello There,
I'm trying to write a module to update certain vulnerable packages in
Debian Systems
Hello There,
I'm trying to write a module to update certain vulnerable packages in
Debian Systems.
My idea is to update them only and only if they are *installed*. Is there
any exec command or any other tricks that you may know to do that?
So far, I've got the basics: :$
package {
I just want to upgrade specific Packages.
The idea is something like : ensure=latest, onlyif=present
Cheers,
Ximena.
On Tuesday, 24 February 2015 16:43:06 UTC+1, David Schmitt wrote:
On 2015-02-24 16:28, Ximena Cardinali wrote:
Hello There,
I'm trying to write a module to update
while MEDIUMTEXT is
16MB.
Ramin
On 7/9/2014 4:48 AM, Ximena Cardinali wrote:
Hello,
I had to apply also this other Solution:
mysql describe report_logs;
+---+--+--+-+-++
| Field | Type | Null | Key | Default
(0.00 sec)
mysql
For now, everything is working as expected. We will see in a few days, or
after puppetdb Upgrade.
X.
On Monday, 16 June 2014 16:55:25 UTC+2, Ximena Cardinali wrote:
Hello There,
I've been struggling the last days with this issue. The situation is
happening since I've
Hello, sorry to bring this back.
I just have a question, did you just changed the path of /usr/bin/ruby or
did you did something else to make it work?
Thanks in advance,
X.
On Friday, 4 October 2013 01:04:22 UTC+2, Matt Zagrabelny wrote:
On Thu, Oct 3, 2013 at 5:45 PM, Juan Sierra Pons
Hello There, have you found a solution for this?
I'll appreciate your help.
Regards,
X.
On Friday, 31 May 2013 09:04:12 UTC+2, Thomas Dahlberg wrote:
I found the solution. Dashboard does not play well with ruby 1.9.3.
I will try the rails3 branch and see if it works better.
/Thomas
On
Me again, I've changed the link of /etc/alternatives/ruby (Debian) to
point to ruby1.8 and everything looks good now on the Dashboard!
Thanks! :)
On Monday, 23 June 2014 15:37:59 UTC+2, Ximena Cardinali wrote:
Hello, sorry to bring this back.
I just have a question, did you just changed
Me again, I've changed the link of /etc/alternatives/ruby (Debian) to
point to ruby1.8 and everything looks good now on the Dashboard!
Thanks! :)
On Monday, 23 June 2014 15:45:06 UTC+2, Ximena Cardinali wrote:
Hello There, have you found a solution for this?
I'll appreciate your help
Hello There,
I've been struggling the last days with this issue. The situation is
happening since I've upgrade Puppet to 3.6.0.
*- Problem:*
On Puppet-Dashboard all Hosts are shown as *Unresponsive* and thousand of
tasks are queued as *Failed*.
*- Environment:*
OS: Debian Wheezy
11 matches
Mail list logo
