Ubuntu
autopkgtest package

autopkgtest 2.0.1ubuntu2 source package in Ubuntu

Changelog

autopkgtest (2.0.1ubuntu2) precise; urgency=low

  * Fix hashbang lines to use python instead of python2.6, and update
    debian/control to only depend on python (>= 2.6) instead of python2.6.
    See Debian #644332.
 -- Martin Pitt <email address hidden>   Fri, 11 Nov 2011 16:15:18 +0100

Upload details

Uploaded by:
Martin Pitt
Uploaded to:
Precise
Original maintainer:
Ubuntu Developers
Architectures:
all
Section:
devel
Urgency:
Low Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Builds

Precise: [FULLYBUILT] i386

Downloads

File Size SHA-256 Checksum
autopkgtest_2.0.1ubuntu2.tar.gz 74.5 KiB b6cbecf027633f78228ac1c91fe956cf01832148e4f1c3d80d7324670ca7edcb
autopkgtest_2.0.1ubuntu2.dsc 1.6 KiB 44b669f2ca042ca43749ecca205dff41f9ebd9a58aed93f86f53cce6627af95c

Available diffs

View changes file

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 adt-run(1) and /usr/share/doc/autopkgtest.
 Most modes of use require apt-ftparchive from the apt-utils package.
 Use of adt-virt-xenlvm requires the autopkgtest-xenlvm package too;
 Use of the pre-cooked adt-testreport-onepackage script requires curl.

autopkgtest-xenlvm: 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.