Hello community,
here is the log from the commit of package corosync for openSUSE:Factory
checked in at 2017-03-20 17:04:13
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/corosync (Old)
and /work/SRC/openSUSE:Factory/.corosync.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "corosync"
Mon Mar 20 17:04:13 2017 rev:35 rq:479176 version:2.4.2
Changes:
--------
--- /work/SRC/openSUSE:Factory/corosync/corosync.changes 2017-03-03
14:38:50.437885807 +0100
+++ /work/SRC/openSUSE:Factory/.corosync.new/corosync.changes 2017-03-20
17:04:16.214708691 +0100
@@ -2 +2 @@
-Tue Feb 28 04:52:04 UTC 2017 - b...@suse.com
+Tue Mar 14 07:14:58 UTC 2017 - b...@suse.com
@@ -6,0 +7 @@
+ 0001-logconfig.c-make-logging.syslog_priority-and-logging.patch
New:
----
0001-logconfig.c-make-logging.syslog_priority-and-logging.patch
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ corosync.spec ++++++
--- /var/tmp/diff_new_pack.SZx3qr/_old 2017-03-20 17:04:17.510525722 +0100
+++ /var/tmp/diff_new_pack.SZx3qr/_new 2017-03-20 17:04:17.514525157 +0100
@@ -61,6 +61,7 @@
Patch7: corosync-start-stop-level.patch
Patch8: disable-build-html-docs.patch
Patch9: 0001-Logsys-Change-logsys-syslog_priority-priority.patch
+Patch10: 0001-logconfig.c-make-logging.syslog_priority-and-logging.patch
BuildRoot: %{_tmppath}/%{name}-%{version}-build
# openais is indeed gone and should be uninstalled. Yes, we do not
@@ -129,6 +130,7 @@
%patch7 -p1
%patch8 -p1
%patch9 -p1
+%patch10 -p1
%build
%if %{with_runautogen}
++++++ 0001-logconfig.c-make-logging.syslog_priority-and-logging.patch ++++++
>From 5f47e2a8583995cdd80297d4493ce019b02edb14 Mon Sep 17 00:00:00 2001
From: Bin Liu <b...@suse.com>
Date: Fri, 10 Mar 2017 15:22:13 +0800
Subject: [PATCH] logconfig.c: make logging.syslog_priority and
logging.logfile_priority to info
logfile_priority and syslog_priority could be modified by
logging.logger_subsys.{logfile_priority|syslog_priority}. which could
lead to the following output(which are at notice level):
corosync[21419]: [QUORUM] Using quorum provider corosync_votequorum
corosync[21419]: [QUORUM] Members[1]: 1084777643
corosync[21419]: [QUORUM] This node is within the primary component
and will provide service.
corosync[21419]: [QUORUM] Members[3]: 1084777563 1084777584 1084777643
even the syslog_priority is warning. This patch could avoid the
overwrite.
---
exec/logconfig.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/exec/logconfig.c b/exec/logconfig.c
index a4d348a..6d0bed6 100644
--- a/exec/logconfig.c
+++ b/exec/logconfig.c
@@ -401,7 +401,7 @@ static int corosync_main_config_set (
goto parse_error;
}
}
- else {
+ else if(strcmp(key_name, "logging.syslog_priority") == 0){
if (logsys_config_syslog_priority_set(subsys,
logsys_priority_id_get("info")) < 0) {
error_reason = "unable to set syslog level";
@@ -449,7 +449,7 @@ static int corosync_main_config_set (
goto parse_error;
}
}
- else {
+ else if(strcmp(key_name,"logging.logfile_priority") == 0){
if (logsys_config_logfile_priority_set(subsys,
logsys_priority_id_get("info")) < 0) {
error_reason = "unable to set syslog level";
--
2.6.6
