Threw away NO_VAL conflicts will handle in subsequent commits.

%{_libdir} is /usr/lib64. Adding this can cause ordering
problems with the library search path, and is redundant.

And %{_libdir}/slurm is not needed by Slurm itself; it relies on
rpath to resolve the install location instead.

So, this is only useful on a non-standard install, in which case
it's best left to the site to decide how to handle this instead.

Bug 4344.

as to why SLURM_MPI_TYPE is uninitialized in a step.

Bug 4141

Bug 4141

When updating NumNodes, cpus, tasks, gres, memory, etc. need to adjusted
so that counts are correct.

Co-authored with Danny Auble

This requires changing the resv_id and then also updating that on all
the jobs.  Since this requires having the job write lock we spawn
a new thread instead of altering all the paths into
_advance_resv_time().

Bug 4246

Issue could be triggered when updating a partition node(s) with node(s)
that were already in the partition, incorrectly increasing the
node_record->part_cnt (number of associated partitions) and thus
incorrectly extending the array of pointers to partitions associated
with this node, leading to an array with repeated associated
partitions pointers.

Bug 4318.

On CLE 6.0 mungedir is /usr; a 'module unload' call then removes /usr/bin
from PATH which is rather inconvenient.

Bug 4334.

A slurmctld lock needs to at least have a node and partition write lock set
before set_cluster_tres() is called. The slurmctld "cold-restart" path
was not covered.

Bug 4318.

This needs to be an email address, but slurm-dev (now slurm-users)
will drop postings from non-subscribors. Just drop the setting instead.

Mailing list has been renamed. Update links.

Drop Gmane link, as they apparently stopped archiving things
over a year ago, and the relay point has now been dropped from
the slurm-users list.

Drop mentions of emailing slurm-dev from the FAQ. The mailing
list auto-discards anything from non-subscribors.

Accidentally committed in 1b743ca1.

Bug 4332.

Bug 4332.

Memory TRES was getting the pn_min_memroy value when updating the job.
But the TRES memory value is the total memory of the job
(e.g pn_min_memory * cpus || pn_min_memory * nodes).

Bug 4177

"information each job"

bug 4306

Continuation of 72305e30

Bug 4264
Bug 3837

This replaces 3 identical locations of that logic.

Bug 4172