> This seems fine, as long as you smoke test each time (or have CI?) before uploading.
Tests run during package build and autopkgtest has an autopkgtest for itself too (http://autopkgtest.ubuntu.com/packages/a/autopkgtest/ -- does that make some logic circuits explode?). We use the latest autopkgtest in production on a trusty host. I know several users who run the latest versions on vivid and wily (which is where this backport request is coming from), but we don't have systematic automatic testing of the QEMU and LXC backends on these releases. I can commit to manually giving these a spin on my own machine before I issue a backport request, though. > Do you want to try preparing and uploading the source package using backportpackage? Done now, for trusty, vivid, and wily. Thanks! ** Also affects: wily-backports Importance: Undecided Status: New ** Also affects: vivid-backports Importance: Undecided Status: New ** Changed in: trusty-backports Status: New => In Progress ** Changed in: vivid-backports Status: New => In Progress ** Changed in: wily-backports Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Backporters, which is subscribed to trusty-backports. Matching subscriptions: ubuntu-backporters https://bugs.launchpad.net/bugs/1513992 Title: Please continuously backport autopkgtest (main) from xenial To manage notifications about this bug go to: https://bugs.launchpad.net/trusty-backports/+bug/1513992/+subscriptions -- ubuntu-backports mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
