Ubuntu
autopkgtest package

autopkgtest 2.5.4 source package in Ubuntu

Changelog

autopkgtest (2.5.4) unstable; urgency=medium


  * Only clean up binary if we built them ourselves. adt-run previously
    removed debs specified with --binary.

 -- Martin Pitt <email address hidden>  Thu, 19 Dec 2013 16:18:03 +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.4.dsc 1.7 KiB bcf344aa04c4bb010efa4978e8597b385eb99b331ce19e61fad9be1828f23c0a
autopkgtest_2.5.4.tar.gz 88.2 KiB aab769cf3a81349e96f75cc49792cda69511d271df1803a7693ca1cc338518ea

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.