| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |\ \ \ \
| | | | | |
| | | | | |
| | | | | | |
into maint
|
| | | | | | |
|
| | |/ / / |
|
| |\ \ \ \ |
|
| | |/ / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Previously we were not passing through the SSL protocol specified in the
client's bcfg2.conf which caused it to unconditionally be set to
xmlrpc/ssl. While this appears to automagically work with newer versions
of openssl, the version in e.g. centos5 will fail if the server is set
to use TLSv1.
This commit passes through the setting from the client's bcfg2.conf so
that older clients can talk to servers which are set to TLSv1 (in order
to mitigate the effects of POODLE).
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| |\ \ \ \
| | |/ / /
| |/| | | |
YUM: Add options to enable and disable Yum plugins
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Adds two options you can define:
* disabled_plugins: A comma-separated list of plugins to disable
* enabled_plugins: A comma-separated list of plugins to enable
This allows you to run bcfg2 with certain plugins enabled or disabled
when they're not set that way in the yum configuration. This is
useful because the Bcfg2 YUM plugin is initialized before it can read
in any files that might overwrite yum plugin configuration.
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| | | | |
|
| |\ \ \
| | | | |
| | | | |
| | | | | |
https://github.com/fennm/bcfg2 into maint
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |/ / /
| | | |
| | | |
| | | | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| |\ \ \ |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
breaking
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Instead of doing a partially complete Install() method for SYSV,
implements a custom _get_package_command that will use the
_sysv_pkg_path attribute added by the pkgmogrify call.
This will allow the installs to complete. Unfortunately, the
single-pass install will still fail if there are any packages with an
http:// URL. The pkgadd invocation for 'device' sources doesn't take
multiple packages and the 'datastream' invocation doesn't handle packages
with an HTTP URL. Finally, there is no reliable standard naming
convention for SYSV datastream files, so the simplename attribute is
re-used.
There is a known issue with this patch - if any packages specified in
the PackageList have an http url, the single-pass install will produce
an error like:
Trying single pass package install for pkgtype sysv
pkgadd: ERROR: Failure occurred with http(s) negotiation: <'Peername' doesn't match 'host' or no matching entry>
pkgadd: ERROR: unable to download package datastream from <http://install1.d.stor.en.desres.deshaw.com/jumpstart10U10/packages>.
Single Pass Failed
because the command that results isn't valid syntax for pkgadd. A
workaround would be to add code to skip the single-pass install if any
packages had the simplename attribute, or by checking the url for the
presence of 'http'. I'm not sure if that should be fixed or if this is
reasonable in this case.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
pkgadd has different syntax for different sources (datastream and file
system format) which makes using a single pkgtool variable difficult.
Also, SYSV packages in datastream format don't necessarily have uniform
names. Therefore, use the existing 'simplename' attribute to specify
the datastream file name.
|
| | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The "Essential" field in the package control fields could be "yes" or "no".
Only yes sould define the package as essential. The value "no" sould be
handled same as not having the field at all.
|
| |\ \ \ \
| | | | | |
| | | | | | |
Server/Admin: fatal errors should go to stderr
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
If an error occurs, that leads to an termination of the process,
this error should be printed to stderr.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| |\ \ \ \ \
| | |_|/ / /
| |/| | | | |
Use PYVERSION in Makefile and gen-prototypes consistently
|
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
PYVERSION is already being set in the Makefile but wasn't being used
when setup.py gets invoked.
Use PYVERSION in gen-prototypes to generate complete packages.
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \
| | | | | |
| | | | | | |
Doc: fix repeated word in AWSTags docs
|
| | | | | | |
|
| |/ / / / |
|
| | | | |
| | | | |
| | | | | |
This fixes a subtle bug by enforcing that it's a tuple of 2-tuples rather than just a single 2-tuple.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Options/Types: add abbility to set empty lists
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
We have some lists with default values, so someone maybe want to set an empty
list from the config. Previously this was not possible, because an empty string
results in a list with an empty string as element. This fixes this problem.
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Options unit tests
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
The database name is sometimes a path (SQLite) and sometimes not
(MySQL, PostgreSQL). This introduces a new Option type,
RepositoryMacroOption, that expands <repository> macros without
canonicalizing the path, so SQLite users can use <repository> in their
settings but MySQL users' database name settings will not be destroyed
by path canonicalization.
The unfortunate downside is that SQLite users can't use ~ in their
database name.
|