[Bug 224626] sysutils/puppetserver: puppetserver has an incorrect hardcoded path to rubygem-facter

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Wed Dec 27 23:46:30 UTC 2017


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224626

            Bug ID: 224626
           Summary: sysutils/puppetserver: puppetserver has an incorrect
                    hardcoded path to rubygem-facter
           Product: Ports & Packages
           Version: Latest
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs at FreeBSD.org
          Reporter: rainbow at purlinux.org

Created attachment 189147
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=189147&action=edit
Quick and dirty script to create an appropriate symlink to the system ruby
version of rfacter

Currently, sysutils/puppetserver is broken (will not run, complains about not
being able to find facter, in logs,) unless you have the rubygem
facter version 2.4.6 installed, as it's hardcoded into the default
config for puppetserver:
/usr/local/etc/puppetserver/conf.d/puppetserver.conf:8
        /usr/local/lib/ruby/gems/2.3/gems/facter-2.4.6/lib,

The current version of rfacter in ports is 2.5.0

Updating this line to /usr/local/lib/ruby/gems/2.3/gems/facter-2.5.0/lib
causes the service to function correctly.

I have attached a script that extracts the current installed default version of
ruby, the currently installed rubygem-facter version, and creates a symlink
from the appropriate location to
/usr/local/lib/ruby/gems/default/gems/facter/lib

It's a bit quick and dirty but it gets the job done.

With this, either running on update/install of sysutils/puppetserver or
sysutils/rubygem-facter, and updating the the config file to use the symlink,
it would resolve this issue.

--- Comment #1 from Bugzilla Automation <bugzilla at FreeBSD.org> ---
Maintainer informed via mail

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list