Script 'mail_helper' called by obssrc
Hello community,
here is the log from the commit of package crmsh for openSUSE:Factory checked
in at 2022-10-17 14:57:57
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/crmsh (Old)
and /work/SRC/openSUSE:Factory/.crmsh.new.2275 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "crmsh"
Mon Oct 17 14:57:57 2022 rev:263 rq:1011285 version:4.4.1+20221014.0b04f693
Changes:
--------
--- /work/SRC/openSUSE:Factory/crmsh/crmsh.changes 2022-09-30
17:58:32.589344640 +0200
+++ /work/SRC/openSUSE:Factory/.crmsh.new.2275/crmsh.changes 2022-10-17
14:57:59.394126158 +0200
@@ -1,0 +2,12 @@
+Fri Oct 14 01:52:53 UTC 2022 - xli...@suse.com
+
+- Update to version 4.4.1+20221014.0b04f693:
+ * crm.8.adoc: spelling (recipients, embellishments)
+
+-------------------------------------------------------------------
+Fri Oct 14 01:08:15 UTC 2022 - xli...@suse.com
+
+- Update to version 4.4.1+20221013.11edd97f:
+ * Dev: Dockerfile: update the Dockerfile for updating parallax
+
+-------------------------------------------------------------------
Old:
----
crmsh-4.4.1+20220928.3480aa0d.tar.bz2
New:
----
crmsh-4.4.1+20221014.0b04f693.tar.bz2
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ crmsh.spec ++++++
--- /var/tmp/diff_new_pack.6avHmn/_old 2022-10-17 14:58:00.010127341 +0200
+++ /var/tmp/diff_new_pack.6avHmn/_new 2022-10-17 14:58:00.018127356 +0200
@@ -36,7 +36,7 @@
Summary: High Availability cluster command-line interface
License: GPL-2.0-or-later
Group: %{pkg_group}
-Version: 4.4.1+20220928.3480aa0d
+Version: 4.4.1+20221014.0b04f693
Release: 0
URL: http://crmsh.github.io
Source0: %{name}-%{version}.tar.bz2
++++++ _servicedata ++++++
--- /var/tmp/diff_new_pack.6avHmn/_old 2022-10-17 14:58:00.066127449 +0200
+++ /var/tmp/diff_new_pack.6avHmn/_new 2022-10-17 14:58:00.070127456 +0200
@@ -9,7 +9,7 @@
</service>
<service name="tar_scm">
<param name="url">https://github.com/ClusterLabs/crmsh.git</param>
- <param
name="changesrevision">3081582137d44f867222d7161eebca796d2c3293</param>
+ <param
name="changesrevision">626f3c90ac626ab6a3d967208bc9186002127740</param>
</service>
</servicedata>
(No newline at EOF)
++++++ crmsh-4.4.1+20220928.3480aa0d.tar.bz2 ->
crmsh-4.4.1+20221014.0b04f693.tar.bz2 ++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/crmsh-4.4.1+20220928.3480aa0d/Dockerfile
new/crmsh-4.4.1+20221014.0b04f693/Dockerfile
--- old/crmsh-4.4.1+20220928.3480aa0d/Dockerfile 2022-09-28
10:37:09.000000000 +0200
+++ new/crmsh-4.4.1+20221014.0b04f693/Dockerfile 2022-10-14
03:36:24.000000000 +0200
@@ -13,6 +13,10 @@
RUN zypper -n install make autoconf automake vim which libxslt-tools mailx
iproute2 iputils bzip2 openssh tar file glibc-locale-base firewalld
libopenssl1_1 dos2unix iptables
RUN zypper -n install python3 python3-lxml python3-python-dateutil
python3-parallax python3-setuptools python3-PyYAML python3-curses python3-behave
RUN zypper -n install csync2 libglue-devel corosync corosync-qdevice pacemaker
booth corosync-qnetd
+RUN zypper --non-interactive up zypper
+RUN zypper ar -f -G
https://download.opensuse.org/repositories/network:/ha-clustering:/Factory/SLE_15_SP4
repo_nhf
+RUN zypper --non-interactive refresh
+RUN zypper --non-interactive up --allow-vendor-change -y python3-parallax
RUN mkdir -p /root/.ssh && chmod 0700 /root/.ssh
RUN echo "$ssh_prv_key" > /root/.ssh/id_rsa && chmod 600 /root/.ssh/id_rsa
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/crmsh-4.4.1+20220928.3480aa0d/doc/crm.8.adoc
new/crmsh-4.4.1+20221014.0b04f693/doc/crm.8.adoc
--- old/crmsh-4.4.1+20220928.3480aa0d/doc/crm.8.adoc 2022-09-28
10:37:09.000000000 +0200
+++ new/crmsh-4.4.1+20221014.0b04f693/doc/crm.8.adoc 2022-10-14
03:36:24.000000000 +0200
@@ -2111,7 +2111,7 @@
Set the node status to maintenance. This is equivalent to the
cluster-wide `maintenance-mode` property but puts just one node
-into the maintenance mode. If there are maintenaned resources on
+into the maintenance mode. If there are maintained resources on
the node, the user will be proposed to remove the maintenance
property from them.
@@ -2158,7 +2158,7 @@
[[cmdhelp_node_show,show node]]
==== `show`
-Show a node definition. If the node parameter is omitted then all
+Show a node definition. If the node parameter is omitted, then all
nodes are shown.
Usage:
@@ -2173,7 +2173,7 @@
[[cmdhelp_node_status-attr,manage status attributes]]
==== `status-attr`
-Edit node attributes which are in the CIB status section, i.e.
+Edit node attributes which are in the CIB status section, i.e.,
attributes which hold properties of a more volatile nature. One
typical example is attribute generated by the `pingd` utility.
@@ -2342,7 +2342,7 @@
Some resource management commands, such as `resource stop`, when
the target resource is a group, may not always produce desired
result. Each element, group and the primitive members, can have a
-meta attribute and those attributes may end up with conflicting
+meta-attribute and those attributes may end up with conflicting
values. Consider the following construct:
...............
crm(live)# configure show svc fs virtual-ip
@@ -2575,10 +2575,9 @@
- `fencing_topology`
-Finally, there are the cluster properties, resource meta
-attributes defaults, and operations defaults. All are just a set
-of attributes. These attributes are managed by the following
-commands:
+Finally, there are the cluster properties, resource meta-attributes
+defaults, and operations defaults. All are just a set of attributes.
+These attributes are managed by the following commands:
- `property`
- `rsc_defaults`
@@ -2635,12 +2634,12 @@
external scripts used with ClusterMon resources can be used as alert
scripts, since the interface is compatible.
-Each alert may have a number of receipients configured. These will be
+Each alert may have a number of recipients configured. These will be
passed to the script as arguments. The first recipient will also be
passed as the +CRM_alert_recipient+ environment variable, for
compatibility with existing scripts that only support one recipient.
-The available meta attributes are +timeout+ (default 30s) and
+The available meta-attributes are +timeout+ (default 30s) and
+timestamp-format+ (default `"%H:%M:%S.%06N"`).
Some configurations may require each recipient to be delimited by
@@ -2736,7 +2735,7 @@
The `clone` command creates a resource clone. It may contain a
single primitive resource or one group of resources.
-+Promotable clones+ are clone resources with the +promotable=true+ meta
attribute for the given promotable resources.
++Promotable clones+ are clone resources with the +promotable=true+
meta-attribute for the given promotable resources.
It's used to deprecate the master-slave resources.
Usage:
@@ -2980,7 +2979,7 @@
probably not as useful as the configuration language. The
presentation is somewhat different from what would be displayed
by the `show` command---each element is shown on a single line,
-i.e. there are no backslashes and no other embelishments.
+i.e., there are no backslashes and no other embellishments.
Don't forget to put quotes around the filter if it contains
spaces.
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/crmsh-4.4.1+20220928.3480aa0d/test/testcases/ra.exp
new/crmsh-4.4.1+20221014.0b04f693/test/testcases/ra.exp
--- old/crmsh-4.4.1+20220928.3480aa0d/test/testcases/ra.exp 2022-09-28
10:37:09.000000000 +0200
+++ new/crmsh-4.4.1+20221014.0b04f693/test/testcases/ra.exp 2022-10-14
03:36:24.000000000 +0200
@@ -76,6 +76,8 @@
Eg. node1:1;node2:2,3 would tell the cluster to use port 1 for node1 and
ports 2 and 3 for node2
pcmk_host_list (string): A list of machines controlled by this device
(Optional unless pcmk_host_check=static-list).
+ Eg. node1,node2,node3
+
pcmk_host_check (string, [dynamic-list]): How to determine which machines are
controlled by the device.
Allowed values: dynamic-list (query the device via the 'list' command),
static-list (check the pcmk_host_list attribute), status (query the device via
the 'status' command), none (assume every device can fence every machine)
