bcfg2-crypt: backported fixes in b5b26415161e715fe4d22d69328b06801ff7124d
bcfg2-crypt: Fixed variable name collision
Options: make "public" default pgsql database schema
Add probes.allowed_groups option to restrict group assignments.
testsuite: fixed unit tests for Probes allowed_groups option
doc: defined when probes allowed_groups setting was added
Probes: added missing docstring
doc: Remove unkept bcfg2.conf page

The man pages are stored in our documentation now so this is obsolete.

Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
misc/bcfg2.spec: lxml not required on the client

Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
Reporting: Remove wildcard imports

Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
bcfg2-lint: resolve XIncludes when parsing XML for validation
bcfg2.spec: Remove unnecessary replacement

Our cron job is smart enough to work in any libexec directory. These
replacements are unnecessary.

Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
doc: Update prerequisites

Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
Bundler: Fix parsing XML template output with encoding declaration

lxml 3.2.1 complains when you try to parse a unicode (in Python 2) or
string (in Python 3) containing an XML document with an encoding
declaration. Traceback:

ValueError: Unicode strings with encoding declaration are not
supported. Please use bytes input or XML fragments without
declaration.

This encodes the document as a string (in Python 2) or bytes (in
Python 3) to avoid the lxml error.  There may be other places this
happens, too, although in most other cases we should use
lxml.etree.parse() to parse a file, or we parse strings (in Python 2)
instead of unicode objects.
bcfg2-crypt: handle error when encrypting properties with multiple keys
testsuite: removed py2.5 from travis tests, no longer supported

http://about.travis-ci.org/blog/2013-11-18-upcoming-build-environment-updates/
bcfg2-admin: Restored missing "bcfg2-admin client add ... attrib=val" functionality
bcfg2-admin: added missing docstring
Core: Avoid starting server if database is enabled but cannot be used

Plugins that use the database often act quite differently depending on
whether or not the database is enabled.  If we start the server
without the database (e.g., the connection failed), then Very Strange
Things can happen.
testsuite: fixed unit tests for database fixes