autopkgtest 2.7 source package in Ubuntu

Changelog

autopkgtest (2.7) unstable; urgency=medium


  * adt-virt-lxc: Drop all the file-based checks for container bootup, and
    replace with "lxc-attach runlevel" to wait until the container booted to a
    numeric runlevel. This greatly simplifies the logic and drops the
    cloud-init requirement so that this runner is now suitable for Debian or
    debootstrap-based Ubuntu containers. (LP: #1273725)
  * adt-virt-lxc.1: Drop --gain-root in notes/example. It's unnecessary
    (adt-run will install fakeroot if missing) and confusing (as it's not
    related to LXC specifically and otherwise not really used/useful).
  * adt-virt-lxc.1: Add example how to create a Debian container, and some
    cleanup of obsolete commentary.
  * adt-virt-lxc: Add -s/--sudo option to run lxc-* commands through sudo; use
    this option if you run adt-run as normal user, but need to run the
    container itself as root (if you use LXC system-level containers).
    This drops the hardcoded sudo commands and thus the dependency on sudo,
    which is more palatable for Debian. (LP: #1273977)
  * adt-virt-lxc: Add -e shortcut for --ephemeral, as this is an option which
    you pretty much always want.
  * adt-virt-lxc.1: Move more important options to the top.
  * adt-virt-lxc: Stop hardcoding the "ubuntu" suggested normal user; instead,
    call "getent passwd" to detect the first user with uid >= 500. Don't
    advertise suggested-normal-user if none exists.
  * adt-run: Rearrange finalizing options and reading capabilities to happen
    after testbed opening. That allows the testbed to determine its full
    capablities in its open hook.
  * adt-run: Call dpkg-source --before-build for --unbuilt-tree arguments, to
    ensure that patches are applied for "3.0 (quilt)" source trees. This is
    useful to test *-buildpackage source trees where patches don't get
    applied. (LP: #1212208)

 -- Martin Pitt <email address hidden>  Fri, 31 Jan 2014 11:14:32 +0100

Upload details

Uploaded by:
Autopkgtest team
Uploaded to:
Sid
Original maintainer:
Autopkgtest team
Architectures:
all
Section:
devel
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Builds

Trusty: [FULLYBUILT] i386

Downloads

File Size SHA-256 Checksum
autopkgtest_2.7.dsc 1.7 KiB 58192115833bb5fecd35802888eaaba879ba5f487939a23e9294b967b53af094
autopkgtest_2.7.tar.gz 92.9 KiB d8fb258dfd4e7e4e3bcaaf661c7362172b1962dffeeb41339a9460dcbaab2ae5

Available diffs

No changes file available.

Binary packages built by this source

autopkgtest: automatic as-installed testing for Debian packages

 autopkgtest runs tests on binary packages. The tests are run on the
 package as installed on a testbed system (which may be found via a
 virtualisation or containment system). The tests are expected to be
 supplied in the corresponding Debian source package.
 .
 See autopkgtest(1) and /usr/share/doc/autopkgtest.
 Depending on which virtualization server you want to use, you need to
 install additional packages (schroot, lxc, lxd, or qemu-system)
 .
 For generating tests of well-known source packages such as Perl and Ruby
 libraries you should install the autodep8 package.

autopkgtest-xenlvm: autopkgtest Xen/LVM2 based testbed snapshot system

 Machinery for setting up a Xen domain which can be resumed over and
 over again, discarding changes made each time. This can be useful
 for automated testing and other advanced techniques; autopkgtest is
 able to make use of this machinery for its virtualisation needs.
 .
 You will need a working Xen setup to make use of this software. Your
 network administrator will need to provide support for the testbeds'
 networking requirements. See the README for documentation.