OK, I unmerged and re-emerged the package and I get the same message. I also verified that all remnants of the ruby puppet stuff was gone from site_ruby before I reinstalled.
I'm fairly certain that it's not my manifests as this error seems to occur in the phase where puppet is gathering it's plugins and I tried running puppetd on a server with no node defs, no classes, etc... same thing I'll cc: the package maintainer. Maybe he's seen it before. Maybe the gem at http://distfiles.gentoo.org/distfiles/puppet-2.6.2.gem is bad? On Nov 12, 11:57 am, Steve Neuharth <steve.neuha...@gmail.com> wrote: > jeez, sorry... gentoo. This is on gentoo, not ubuntu, so I used > portage. > > I suppose I could try to scrub my puppetmaster of everything puppet > related and reinstall... definitely not the ideal solution. I'll look > through the ruby libs and see if I can find any dupes first. > > thanks James. > > On Nov 12, 10:06 am, James Turnbull <ja...@puppetlabs.com> wrote: > > > Steve Neuharth wrote: > > > I've upgraded to puppet v2.6.2 on ubuntu (clients and server) and now > > > I get this error messages related to pluginsync: > > > How did you upgrade? I've seen this when files from previous versions > > hung around on the master/client too. > > > Regards > > > James > > > -- > > Puppet Labs -http://www.puppetlabs.com > > C: 503-734-8571 > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
