* Update README_server.txt and README_pejacevic.txt after setting up a
  piuparts master/slave system from packages myself.
  and include all commands piupartss needs to run as root in
  conf/piuparts-slave.sudoers.
* Update instances/piuparts.conf* to match what is in use for
  piuparts.debian.org today. Add two new systems, goldwasser and lamarr, as
  examples taken from piuparts development.

Drop conf/piuparts-master.sudoers from debian/piuparts-master.examples
and modify conf/piuparts-slave.sudoers to only allow the piupartss user
to run /usr/sbin/piuparts as root - that's "all that's needed" anyway.

add debian/changelog entry for Iain changes (thanks!) and remove mine about whats obsolete now. yay!

Iain Lane authored Oct 20, 2014 and Holger Levsen committed Oct 20, 2014

Now that we're using distro-info, this test will break whenever the
devel release changes, and the fix to use distro-info wouldn't be a good
test.

i'm not yet convinced this is a useful test

Leo Iannacone authored Jul 15, 2014 and Holger Levsen committed Jul 15, 2014

do hard-linking with --existing-chroot option if orig chroot and destination dir are on the same device instead of copying files

See #752256 for a discussion why this was reverted and why it would be
useful to have this still...

This reverts commit 73478066.

Select this commit for further de-chaffing of the JSON summary.

Remaining sections are currently:

experimental
jessie
sid
sid2experimental
sid-nodoc
testing2sid

There is a desire in the DDPO integration to add value to the Piuparts
column by showing more detail in the failures, and to winnow out chaff
in the reporting.

The details on how to do this are not fully developed. In the
meantime, as a first, interim, step, configure p.d.o to remove summary
reporting for section tests involving oldstable and older.

... to make the role more clear - it assigns sections to summary.json
categories.