| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
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>
|
|
|
|
| |
This reverts commit 611ce16c8cef81a6fc754c46dcb5cbe618b20b67.
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
|
|
| |
Address ticket #955 and attempt to capture the exceptions that
may possibly be generated from Yum or Yum's plugins and return
some sort of error message.
|
|
|
|
|
|
| |
This make the YUMng verification behavior like the APT tool. Before
hand we just turned off package checksums which only worked with
very new versions of Yum.
|
|
|
|
| |
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>
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
|
|
| |
on irc)
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
|
|
| |
Add a "-t NAME" option which reports the total (and good) number of
managed entries on the host NAME. Also, allow for specifying "total",
"good", and "bad" fields via --fields and --sort.
|
|
|
|
|
| |
bcfg2-reports now shows modified entries if it's called with
--modifiedentry, -m, or -s.
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
| |
The client now also transmits diffs of files which include non-US-ASCII
data (using the encoding setting from Options.py), unless they look like
binary files. In the past, non-ASCII files were transmitted as Base64
blobs.
In addition, "bcfg2 -I" no longer refuses to display non-ASCII diffs.
Resolves ticket #999.
|
|
|
|
|
|
|
| |
Currently, client reports don't include diffs of files which aren't
US-ASCII encoded. The client transmits such files as Base64 blobs. As
we'd like to change that, this commit teaches the server to properly
handle non-ASCII diffs.
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
|
|
| |
Add documentation for the "decision" option to the bcfg2.conf(5) man
page. Also, note that it can be overridden using "-l none" on the
bcfg2(1) command line.
|
|
|
|
| |
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>
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| |
|
|
|
|
| |
an ugly stack trace if a file fails to validate
|
| |
|
|
|
|
|
| |
These accesses are triggered by <Package> configuration entries which
don't have the "version" attribute set to "auto" or "any".
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 5d69ff7e966c4ffa911c78d11a6879b48e90aef8.
As the "rawconfig" variable now holds a UTF-8 encoded string, it would
have to be decoded before re-encoding it using a different encoding.
However, the cached configuration shouldn't be written using a non-UTF-8
encoding anyway, as "bcfg2 -f <configuration>" currently doesn't accept
any other encodings. (If this is to be changed, the XML encoding
declaration of the configuration would have to be adjusted accordingly.)
|
| |
|
|
|
|
|
|
| |
that are very similar and could be merged
added text wrapping to bcfg2-lint error handling
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
| |
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
|
|
|
| |
It appears as though Python 2 kept around variables assigned within a
list comprehensions which caused this to go unnoticed.
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|
|
|
|
| |
Replaces PluginExecutionError with Bcfg2.Server.Plugin.PluginExecutionError. Reported by emias.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
The client receives the configuration specification as a Unicode string
and then hands it over to the XML() function, which expects a UTF-8
encoded string. Therefore, the configuration specification is now
converted to UTF-8.
Resolves ticket #1009.
|
|
|
|
| |
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>
|
| |
|
|
|
|
| |
Signed-off-by: Sol Jerome <sol.jerome@gmail.com>
|