Updating CHANGELOG, conf/redhat/facter.spec for 2.0.0rc1 release.
(#14521) Ensure install only strips leading lib dir

Prior to this commit, install stripped out all instance of lib,
which was fine, but now we are vendoring code for facts, and we
need that directory to exist for the vendored so that the require
is correct and because that directory contains the license.
(#14521) Ensure install propagates licenses

Prior to Facter 2.0, we weren't vendoring code that specifically
required a license, so we didn't need to propagate licenses. Now
Facter 2.0 is vendoring code and we need to explicitly include
the license for that code.
Merge pull request #211 from hkenney/ticket/master/14521_install_strips_all_lib_dirs

(#14521) Fix install for vendored cfpropertylist code
Update CHANGELOG, conf/redhat/facter.spec for 2.0.0rc2
Update CHANGELOG, conf/redhat/facter.spec for 1.6.9
(#14582) Fix noise in LSB facts

Redirect LSB fact's stderr to /dev/null to prevent excess noise.
Merge remote-tracking branch 'remotes/hkenney/ticket/1.6.x/14582_fix_noise_in_lsb_facts' into 1.6.x

* remotes/hkenney/ticket/1.6.x/14582_fix_noise_in_lsb_facts:
  (#14582) Fix noise in LSB facts
(#13678) Add filename extension on absolute paths on windows

Running Facter::Util::Resolution.exec calls
Facter::Util::Resolution.which to get the absolute pathname to a binary.
If passing a relative path, puppet will check different search paths and
different filename extensions (like .com, .exe) to find the absolute
path on windows machines

For absolute paths the former behaviour was to just return true if the
path is a valid path to an executable, so "C:\Windows\System32\netsh"
was treated as invalid because it misses the correct extension
(netsh.exe) which caused the ipaddress6 fact to fail.

Change the behaviour of Facter::Util::Resolution.which to also try out
the different filename extensions if an absolute path is used.
(#13678) Remove deprecation msg triggerd by the ipaddress6 fact

Facter::Util::Resolution.exec tries to get the expanded path to the
binary by calling Facter::Util::Resolution.which. This works for
relative commands (if the command is found in PATH). If the binary
describes an absolute path on windows but lacks a filename extension
Facter::Util::Resolution.which will also try to find the correct
extension, so the final binary passes a File.executable? check.

However, this behaviour (passing an absolute path but omit the
extension) is marked as deprecated.

Remove every occurence of Facter::Util::Resolution.exec where a binary
is passed without the correct filename extension.
(14466) Warn when no facts found

Add `warnonce` message to Facter to alert user when no facts
were loaded.
Merge branch '1.6.x' into 2.0rc

* 1.6.x:
  (#14582) Fix noise in LSB facts
Merge branch '2.0rc'

* 2.0rc:
  (#14582) Fix noise in LSB facts
  Update CHANGELOG, conf/redhat/facter.spec for 1.6.9
  Update CHANGELOG, conf/redhat/facter.spec for 2.0.0rc2
  (#14521) Ensure install propagates licenses
  (#14521) Ensure install only strips leading lib dir
  Updating CHANGELOG, conf/redhat/facter.spec for 2.0.0rc1 release.
(#14466) Fix style issues
Merge pull request #214 from hkenney/ticket/2.x/14466_warn_when_no_facts_found

(14466) Warn when no facts found
Use git describe in Rakefile to determine pkg ver

This commit borrows from the puppet-dashboard tarball
generation rake task, using git describe to generate
the version string instead of using the hardcoded
value in lib/facter.rb. This allows the tarball task
to generate correctly named RC tarballs. Currently,
packaging RCs requires the manual renaming and tarring
of the generated directory. Because the built in rake/
PackageTask does not play well with long git-describe
strings, it is replaced with a different implementation
that can handle the longer git-describe version strings.
The gem package task still uses the rake built-in, so
the version string is santized for it.

Signed-off-by: Moses Mendoza <moses@puppetlabs.com>
Merge remote-tracking branch 'MosesMendoza/use_git_describe_for_version_rake' into 1.6.x

* MosesMendoza/use_git_describe_for_version_rake:
  Use git describe in Rakefile to determine pkg ver
Merge branch '1.6.x' into 2.0rc

* 1.6.x:
  Use git describe in Rakefile to determine pkg ver
Merge branch '2.0rc' into 2.0.x

* 2.0rc:
  Use git describe in Rakefile to determine pkg ver
  (#14582) Fix noise in LSB facts
  Update CHANGELOG, conf/redhat/facter.spec for 1.6.9
Update CHANGELOG, conf/redhat/facter.spec for 2.0.0rc3