bug 4443

bug 4441

Bug 4306.

Bug 4416

Continuation of d4a485d2

Fix regression added in commit 9df82091.

Bug 4406.

to fix issue where job ordering causes wrong unused wall.

The "order by" part of the original sql query was wrong.
I had a situation where I had 2 jobs in an updated reservation,
but instead of adding their times together, they were overwriting
their times. This happened because of the ordering of the rows, where
the reservation got split up because of the "order by job.time_start".

That was simply wrong.

Bug 4406

# Conflicts:
#	src/slurmd/slurmd/req.c

to start.

Bug 4434

Fix regression from commit 549e2372.

Bug 4423

Bug 4424.

This reverts commit 6bb79d85.

Bug 4405

Bug 4406

Bug 4405

Follow on to a37f8a1d for slurm.spec.

Avoid duplicating this logic in the Source and setup definitions.

Bug 4421.

%systemd_preun_with_restart was a typo, replace with
correct %systemd_postun_with_restart macro.

Bug 4421.

This reverts commit 29ac92fc.

Restore the expected and long-standing practice of having the main
slurm package own /etc/slurm.

Bug 4421.

Bug 4433.

since the ABI could change from one version to the other.

Bug 4435

Bug 4431

This primarily happens regularly if

PrologFlags=contain

Where the output has a nodename (and usually a number in it)

Normal output is

salloc: Granted job allocation 31159
1

but if the allocation is delayed you get output like

salloc: Granted job allocation 31161
salloc: Waiting for resource configuration
salloc: Nodes snowflake4 are ready for job
1
salloc: Relinquishing job allocation 31161

Where the test would key on the number in snowflake4 and fail.

This change makes it so the number has to be the first thing seen.

With the change to dynamic linking for libslurmfull, all
packages must match not just the API version but the exact
release. Set this for all sub-packages in accordance with the
Fedora packaging guidelines.

Bug 4426.

bug 4356

Continue to build with OpenSSL by default, which can be disabled
with --without openssl.

No behavioral change.

Bug 4428.

_top_priority() is used to determine at job allocation time (called from
job_allocate()) if any other job has a higher priority than the specified
job being allocated. If so, it sets the job state_reason to WAIT_PRIORITY.
This patch skips the priority comparison if the two jobs being compared
are pack job components from the same heterogeneous job.

Bug 4400.

Global replace operation made some undesired changes

bug 4247

in _unpack_node_info_members().

Bug 4389