These seem to be due to a problem within rpmbuild and the slurm.spec
file appears good

Check for build errors and warnings

functions accordingly.

Conflicts:
	src/slurmd/slurmstepd/req.c

For instance we need to pack completing jobs where they weren't packed
before.

Conflicts:
	RELEASE_NOTES

RELEASE_NOTES and news.html files changes. No content added or
removed

If both AllowAccount (or QOS) and DenyAccount are specified then
only enforce the AllowAccount parameter. The other parameter is
ignored.

accounting_storage/filetxt.

This adds allow_account_array and deny_account_array fields to the
slurmctld partition record. Enforcement is done at job submit time.

erroneously on a bluegene system.

This reverts the following two commits:
d84bdaea
25051e48
While they work as designed, we probably do not want to provide
support for the DenyGroups option

The AllowGroups and DenyGroups configuration parameters only apply
to the effective group ID of the job. Previously any user with
access to any allowed group was permitted to use the partition.

My patch for 366 still has a bug in that the step number in the
job file is incorrect.
Bug 368

Bug 366