The other issues you had were caused by a bug in the facter port and
should be fixed now with sysutils/rubygem-facter 1.6.18_2. Please
update and let me know if you have any further issues.
It's all good now, many thanks
___
Moving to ruby 1.9 by following the instructions in UPDATING breaks puppet.
When updating with portmaster, at install time it says 'could not load
facter; cannot install' and exits. I had to manually run 'gem install
facter', then puppet installed. However, 'service puppetmaster status'
was
Moving to ruby 1.9 by following the instructions in UPDATING breaks
puppet.
Sorry for the breakage, I'll take a look.
Steve
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any
Moving to ruby 1.9 by following the instructions in UPDATING breaks
puppet.
When updating with portmaster, at install time it says 'could not load
facter; cannot install' and exits. I had to manually run 'gem install
facter', then puppet installed.
It's better to install via the port so
When updating with portmaster, at install time it says 'could not load
facter; cannot install' and exits. I had to manually run 'gem install
facter', then puppet installed.
It's better to install via the port so that the package management knows
it's there. This could be causing the later
It would probably be best to kill puppet before the upgrade.
This is definitely the problem here. I'm afraid you'll have to
manually kill it here, since the old rc script has been deinstalled.
You'll only have to do it this once.
Not a problem (except for UPDATING), but since
Actually the problem is just the facter port. Steve Wills is working on
a fix. You can skip deleting the ruby packages; just delete the facter
package or wait for the fix to be committed.
Bryan
On 5/31/2013 4:25 PM, Bryan Drewery wrote:
Delete the built ruby-1.8 and ruby-1.9 packages from your
Delete the built ruby-1.8 and ruby-1.9 packages from your package
repository. The bulk build your set again. This will fix all ports
depending on ruby to rebuild with the new default.
Poudriere is supposed to catch this case by default in 3.0.x, but
somehow missed it. Historically this was needed
On 05/31/13 21:02, bw.mail.lists wrote:
It would probably be best to kill puppet before the upgrade.
This is definitely the problem here. I'm afraid you'll have to
manually kill it here, since the old rc script has been
deinstalled. You'll only have to do it this once.
Not a
