Hmm, okay.
On 04/23/2014 12:44 PM, shlo.af...@gmail.com wrote:
> The output contain :
>
>
> warning: Package libstdc++ found in both yum and yum; skipping the
> yum version
I can reproduce the effect. I suspect this happens when yum presents
several different versions of a packa
The output contain :
warning: Package libstdc++ found in both yum and yum; skipping the yum
version
.
package { 'libstdc++':
ensure => '4.4.7-4.el6',
}
other packages ...
On Wednesday, April 23, 2014 1:22:05 PM UTC+3, Felix.Frank wrote:
>
> On 04/23/2014 08:25 AM, shlo@gm
On 04/23/2014 08:25 AM, shlo.af...@gmail.com wrote:
>
> Hi,
> I did not understand what you mean, I can tell what I did:
> I run on one computer the command:
> puppet resource package
> I took the output and put it in puppet. Run puppet on another computer
> and I got this error.
> Thanks.
T
Hi,
I did not understand what you mean, I can tell what I did:
I run on one computer the command:
puppet resource package
I took the output and put it in puppet. Run puppet on another computer and
I got this error.
Thanks.
On Wednesday, April 16, 2014 3:46:30 PM UTC+3, Felix.Frank wrote:
>
Interesting use case. Sounds like we may be lacking a feature here.
Shlo, is the yum command working when you paste it just the way puppet
issues it, or are you skipping all the fancy parameters of puppet's?
Cheers,
Felix
On 03/05/2014 11:30 AM, Flamarion Jorge wrote:
> Hi,
>
> I have same "pro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I have same "problem" and my workaround, until discovery solution,has
been to use a "exec" function and run yum command.
This works for me.
Flamarion Jorge
Em 05/03/14 03:42, shlo.af...@gmail.com escreveu:
>
>
> Hi I want to install same pa
Hi
I want to install same package with a 2 different version like:
libstdc++-4.4.7-3.el6.i686
libstdc++-4.4.7-3.el6.x86_64
I put it in puppet init file and when I run puppet I get:
err: /Package[libstdc++]/ensure: change from 4.4.7-3.el6 to
4.4.7-4.el6.i686 failed: Could not update: Executi
