Bug#842300: autopkgtest: not clear what should be in d/t/control to make /tmp/autopkgtest-reboot work

[Simon McVittie]

Package: autopkgtest
Version: 4.1
Severity: normal
Tags: patch

It isn't completely clear what a test author should do if they want to
reboot the machine: isolation-machine doesn't necessarily seem to
guarantee the ability to reboot, although perhaps in practice it always
does. In the virtualization abstraction, 'reboot' is a separate capability.

The attached patch is one way to resolve this, by adding a 'needs-reboot'
Restriction which maps directly to the 'reboot' capability.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages autopkgtest depends on:
ii  apt-utils       1.3.1
ii  libdpkg-perl    1.18.10
ii  procps          2:3.3.12-2
ii  python3         3.5.1-4
ii  python3-debian  0.1.29

Versions of packages autopkgtest recommends:
ii  autodep8  0.8

Versions of packages autopkgtest suggests:
pn  lxc          <none>
pn  lxd-client   <none>
ii  qemu-system  1:2.7+dfsg-1
ii  qemu-utils   1:2.7+dfsg-1
ii  schroot      1.6.10-2+b1

-- no debconf information
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0003-Add-needs-reboot-restriction.patch
Type: text/x-diff
Size: 2172 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/autopkgtest-devel/attachments/20161027/c4b4fd24/attachment-0001.patch>