autopkgtest 2.5.6 source package in Ubuntu

Changelog

autopkgtest (2.5.6) unstable; urgency=medium


  * Adjust "su" calls to explicitly specify /bin/sh as shell, as recent
    base-passwd disables them now for system users. (Closes: #734740)

 -- Martin Pitt <email address hidden>  Thu, 09 Jan 2014 15:21:44 +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.5.6.dsc 1.7 KiB e56e227edf06012c51adbdeee21658919abc6618795c2f1fb3e466c12d9d9016
autopkgtest_2.5.6.tar.gz 89.3 KiB d2ac733327e5f3844aa6a736ef7c50a74cc12f49aeb63189bb1ab41aacbf2b6a

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.