On Thursday, December 13, 2012 6:51:57 PM UTC-6, Jakov Sosic wrote:
>
> IMHO it's a really bad practice to mix
> different packaging systems and that practice will byte you, sooner or
> later.
>
+1
John
--
You received this message because you are subscribed to the Google Groups
"Puppet
On 11/28/2012 05:58 PM, Jeff McCune wrote:
Jakov,
I'm really sorry to step in on this one but our ruby should fully
support gems installed using the gem command. I understand it's not
ideal and that RPM's are definitely preferable. I encourage people to
use RPMs whenever possible in this situati
Thanks Jeff for pointing out that the EPEL maintainer and the puppet labs
maintainer should have been coordinating on rubygem-json. (It's the same
guyme. I'm an idiot).
Mike
On Wed, Nov 28, 2012 at 11:37 AM, Brian Jolly wrote:
> That worked for me. Thanks!!!
>
>
> On Wed, Nov 28, 2012 a
For me as well! Thanks for all the help!!
On Nov 28, 2012, at 2:37 PM, Brian Jolly wrote:
> That worked for me. Thanks!!!
>
>
> On Wed, Nov 28, 2012 at 11:18 AM, Matthaus Owens
> wrote:
> The problem was that our el5 rubygem-json package was the el6 src
> rebuilt, without the patch, agains
That worked for me. Thanks!!!
On Wed, Nov 28, 2012 at 11:18 AM, Matthaus Owens wrote:
> The problem was that our el5 rubygem-json package was the el6 src
> rebuilt, without the patch, against ruby 1.8.5. Rebuilding the
> rubygem-json package against the ruby 1.8.7 packages in our
> dependencies
The problem was that our el5 rubygem-json package was the el6 src
rebuilt, without the patch, against ruby 1.8.5. Rebuilding the
rubygem-json package against the ruby 1.8.7 packages in our
dependencies repo resolved the parser.so linking errors. I've included
the ldd of the parser.so before and aft
On Fri, Nov 23, 2012 at 2:46 PM, Alaric wrote:
> Hi,
>
> I'm having a weird issue and was wondering if anyone else had run into it. I
> recently upgraded from puppet 2.7 -> 3.0.1 After cleaning up some gems on my
> puppet master everything seemed to be working ok. I had originally used the
>
Jakov,
I'm really sorry to step in on this one but our ruby should fully
support gems installed using the gem command. I understand it's not
ideal and that RPM's are definitely preferable. I encourage people to
use RPMs whenever possible in this situation. However, I'm deeply
concerned that we may
On Tue, Nov 27, 2012 at 3:53 PM, Alaric wrote:
>
> Swing and a miss... even after verifying and manually removing any gems, and
> any cached gems, reinstalling effected packages and verifying, I still get
> the same error...
Are you able to reduce this down to a specific module or class that
trig
On Tuesday, November 27, 2012 8:37:22 PM UTC-6, Brian Jolly wrote:
>
> I am experiencing the same problem with a 3.0.1 install.
>
> If I set "enable_inventory_service: false" there are no problems.
>
> ruby: symbol lookup error:
> /usr/lib/ruby/gems/1.8/gems/json-1.5.1/ext/json/ext/json/ext/par
On 11/27/2012 03:09 PM, Alaric wrote:
> Yup, I get the same error:
>
> /usr/bin/ruby: symbol lookup error:
> /usr/lib64/ruby/site_ruby/1.8/x86_64-linux/json/ext/parser.so: undefined
> symbol: RSTRING_PTR
Upgrade to the ruby provided by puppetlabs repo (RHEL 5 has older
version), and don't mix
I am experiencing the same problem with a 3.0.1 install.
If I set "enable_inventory_service: false" there are no problems.
ruby: symbol lookup error:
/usr/lib/ruby/gems/1.8/gems/json-1.5.1/ext/json/ext/json/ext/parser.so:
undefined symbol: RSTRING_PTR
ruby 1.8.7 (2012-06-29 patchlevel 370) [x
On Tuesday, November 27, 2012 9:53:35 AM UTC-6, alaric wrote:
>
>
> On Nov 27, 2012, at 9:57 AM, Alaric >
> wrote:
>
>
> On Nov 27, 2012, at 9:45 AM, jcbollinger >
> wrote:
>
>
>
> On Tuesday, November 27, 2012 8:27:37 AM UTC-6, Matthew Burgess wrote:
>>
>> On Tue, Nov 27, 2012 at 2:09 PM, Alar
On Nov 27, 2012, at 9:57 AM, Alaric wrote:
>
> On Nov 27, 2012, at 9:45 AM, jcbollinger wrote:
>
>>
>>
>> On Tuesday, November 27, 2012 8:27:37 AM UTC-6, Matthew Burgess wrote:
>> On Tue, Nov 27, 2012 at 2:09 PM, Alaric wrote:
>> > Yup, I get the same error:
>> >
>> > /usr/bin/ruby: sym
On Nov 27, 2012, at 9:45 AM, jcbollinger wrote:
>
>
> On Tuesday, November 27, 2012 8:27:37 AM UTC-6, Matthew Burgess wrote:
> On Tue, Nov 27, 2012 at 2:09 PM, Alaric wrote:
> > Yup, I get the same error:
> >
> > /usr/bin/ruby: symbol lookup error:
> > /usr/lib64/ruby/site_ruby/1.8/x86_64
On Tue, Nov 27, 2012 at 2:45 PM, jcbollinger wrote:
>
>
> On Tuesday, November 27, 2012 8:27:37 AM UTC-6, Matthew Burgess wrote:
>>
>> On Tue, Nov 27, 2012 at 2:09 PM, Alaric wrote:
>> > Yup, I get the same error:
>> >
>> > /usr/bin/ruby: symbol lookup error:
>> > /usr/lib64/ruby/site_ruby/1.8/x8
On Tuesday, November 27, 2012 8:27:37 AM UTC-6, Matthew Burgess wrote:
>
> On Tue, Nov 27, 2012 at 2:09 PM, Alaric >
> wrote:
> > Yup, I get the same error:
> >
> > /usr/bin/ruby: symbol lookup error:
> /usr/lib64/ruby/site_ruby/1.8/x86_64-linux/json/ext/parser.so: undefined
> symbol: RSTRI
On Tue, Nov 27, 2012 at 2:09 PM, Alaric wrote:
> Yup, I get the same error:
>
> /usr/bin/ruby: symbol lookup error:
> /usr/lib64/ruby/site_ruby/1.8/x86_64-linux/json/ext/parser.so: undefined
> symbol: RSTRING_PTR
>
>
> My one thought is that maybe my version stdlib is old... I checked and it's
On Nov 26, 2012, at 10:29 PM, Michael Stahnke wrote:
> On Mon, Nov 26, 2012 at 2:16 PM, Alaric wrote:
>>
>> On Nov 26, 2012, at 4:46 PM, Michael Stahnke wrote:
>>
>>>
>>> I tried to reproduce this and just couldn't. Does this happen on
>>> other systems?
>>>
>>> Is there any more informa
On Mon, Nov 26, 2012 at 2:16 PM, Alaric wrote:
>
> On Nov 26, 2012, at 4:46 PM, Michael Stahnke wrote:
>
>>
>> I tried to reproduce this and just couldn't. Does this happen on
>> other systems?
>>
>> Is there any more information you could think of?
>>
>
>
> Sadly, it's happening on every RHEL5
On Nov 26, 2012, at 4:46 PM, Michael Stahnke wrote:
>
> I tried to reproduce this and just couldn't. Does this happen on
> other systems?
>
> Is there any more information you could think of?
>
Sadly, it's happening on every RHEL5 system I have! All packages are either
RedHat or EPEL, o
On Fri, Nov 23, 2012 at 2:46 PM, Alaric wrote:
> Hi,
>
> I'm having a weird issue and was wondering if anyone else had run into it. I
> recently upgraded from puppet 2.7 -> 3.0.1 After cleaning up some gems on my
> puppet master everything seemed to be working ok. I had originally used the
>
Hi,
I'm having a weird issue and was wondering if anyone else had run into it. I
recently upgraded from puppet 2.7 -> 3.0.1 After cleaning up some gems on my
puppet master everything seemed to be working ok. I had originally used the
EPEL repo's to deploy puppet, but switched to the Puppet L
23 matches
Mail list logo
