Jobs could be initiated out of order if
1. Priority/basic configured AND
2. Sched/builtin (First-in First-out) configured AND
3. Job preemption configured AND
4. Multiple partitions with different priorities
bug 373

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