Testing the apt-pocket proposed lxc launch ubuntu:kinetic timscontainer lxc exec timscontainer bash # Testing the wrong version sudo apt install -t kinetic autopkgtest exit # Back to my machine sudo autopkgtest-buildvm-ubuntu-cloud -a amd64 -r mantic -s 15G lxc file push autopkgtest-mantic-amd64.img timscontainer/ # back to container lxc exec timscontainer bash sudo autopkgtest --setup-commands="apt-get update" --apt-pocket=proposed isc-dhcp -- qemu --ram-size=1536 --cpus 2 ./autopkgtest-mantic-amd64.img
Output verifies the version fetched isn't from proposed: autopkgtest [14:47:12]: testbed dpkg architecture: amd64 autopkgtest [14:47:14]: testbed running kernel: Linux 6.2.0-21-generic #21-Ubuntu SMP PREEMPT_DYNAMIC Fri Apr 14 12:34:02 UTC 2023 autopkgtest [14:47:15]: @@@@@@@@@@@@@@@@@@@@ apt-source isc-dhcp Get:1 http://archive.ubuntu.com/ubuntu mantic/main isc-dhcp 4.4.3-P1-1ubuntu1 (dsc) [2,969 B] Get:2 http://archive.ubuntu.com/ubuntu mantic/main isc-dhcp 4.4.3-P1-1ubuntu1 (tar) [10.1 MB] Get:3 http://archive.ubuntu.com/ubuntu mantic/main isc-dhcp 4.4.3-P1-1ubuntu1 (asc) [874 B] Get:4 http://archive.ubuntu.com/ubuntu mantic/main isc-dhcp 4.4.3-P1-1ubuntu1 (diff) [128 kB] gpgv: Signature made Mon 28 Nov 2022 02:38:12 PM GMT gpgv: using RSA key 25E3FF2D7F469DBE7D0D4E50AFCFEC8E669CE1C2 gpgv: Can't check signature: No public key dpkg-source: warning: cannot verify inline signature for ./isc-dhcp_4.4.3-P1-1ubuntu1.dsc: no acceptable signature found autopkgtest [14:47:44]: testing package isc-dhcp version 4.4.3-P1-1ubuntu1 # Now testing to make sure with the correct version it works sudo apt remove --purge autopkgtest add "deb http://archive.ubuntu.com/ubuntu kinetic-proposed main restricted" to /etc/apt/sources.list apt update sudo apt install -t kinetic-proposed autopkgtest apt list --installed | grep autopkgtest WARNING: apt does not have a stable CLI interface. Use with caution in scripts. autopkgtest/kinetic-proposed,now 5.28ubuntu0.22.10.0 all [installed] sudo autopkgtest --setup-commands="apt-get update" --apt-pocket=proposed isc-dhcp -- qemu --ram-size=1536 --cpus 2 ./autopkgtest-mantic-amd64.img Relevant output: autopkgtest [15:06:08]: testbed dpkg architecture: amd64 autopkgtest [15:06:15]: testbed running kernel: Linux 6.2.0-21-generic #21-Ubuntu SMP PREEMPT_DYNAMIC Fri Apr 14 12:34:02 UTC 2023 autopkgtest [15:06:15]: @@@@@@@@@@@@@@@@@@@@ apt-source isc-dhcp Get:1 http://archive.ubuntu.com/ubuntu mantic-proposed/main isc-dhcp 4.4.3-P1-1ubuntu2 (dsc) [2,969 B] Get:2 http://archive.ubuntu.com/ubuntu mantic-proposed/main isc-dhcp 4.4.3-P1-1ubuntu2 (tar) [10.1 MB] Get:3 http://archive.ubuntu.com/ubuntu mantic-proposed/main isc-dhcp 4.4.3-P1-1ubuntu2 (asc) [874 B] Get:4 http://archive.ubuntu.com/ubuntu mantic-proposed/main isc-dhcp 4.4.3-P1-1ubuntu2 (diff) [129 kB] gpgv: Signature made Thu 11 May 2023 03:13:31 PM BST gpgv: using RSA key D98F377EB47CC6DD257A9A07E564B9C275BDD52E gpgv: Can't check signature: No public key dpkg-source: warning: cannot verify inline signature for ./isc-dhcp_4.4.3-P1-1ubuntu2.dsc: no acceptable signature found rmadison output to verify correct version: rmadison isc-dhcp isc-dhcp | 4.2.4-7ubuntu12 | trusty | source isc-dhcp | 4.2.4-7ubuntu12.12 | trusty-security | source isc-dhcp | 4.2.4-7ubuntu12.13 | trusty-updates | source isc-dhcp | 4.3.3-5ubuntu12 | xenial | source isc-dhcp | 4.3.3-5ubuntu12.9 | xenial-security | source isc-dhcp | 4.3.3-5ubuntu12.10 | xenial-updates | source isc-dhcp | 4.3.5-3ubuntu7 | bionic | source isc-dhcp | 4.3.5-3ubuntu7.4 | bionic-security | source isc-dhcp | 4.3.5-3ubuntu7.4 | bionic-updates | source isc-dhcp | 4.4.1-2.1ubuntu5 | focal | source isc-dhcp | 4.4.1-2.1ubuntu5.20.04.4 | focal-security | source isc-dhcp | 4.4.1-2.1ubuntu5.20.04.5 | focal-updates | source isc-dhcp | 4.4.1-2.3ubuntu2 | jammy | source isc-dhcp | 4.4.1-2.3ubuntu2.3 | jammy-security | source isc-dhcp | 4.4.1-2.3ubuntu2.4 | jammy-updates | source isc-dhcp | 4.4.3-2ubuntu4 | kinetic | source isc-dhcp | 4.4.3-P1-1ubuntu1 | lunar | source isc-dhcp | 4.4.3-P1-1ubuntu1 | mantic | source isc-dhcp | 4.4.3-P1-1ubuntu2 | mantic-proposed | source So it looks like the --apt-pocket changes worked. -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to autopkgtest in Ubuntu. https://bugs.launchpad.net/bugs/2015285 Title: [SRU Exception] Backport 5.28 to kinetic Status in autopkgtest package in Ubuntu: New Status in autopkgtest source package in Kinetic: Fix Committed Bug description: [Impact] This SRU has two specific impacts: cross-architecture testing, and pocket pinning. There may be unknown impacts in backporting the version in lunar to kinetic (5.25->5.28). Initially, the patches were added to Jammy and Kinetic to provide the cross-architecture testing and pocket pinning in https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2002455 but we have since decided to go ahead and backport the version of lunar that include these patches, back to kinetic. (We similarly backported the 5.28 version in lunar to jammy in https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2008026) Below is a summary of the two initially sought after impacts. 1. cross-architecture testing autopkgtest currently does not have the -a ARCH capability needed to permit cross-architecture testing. This is notably useful for i386 local testing [0] and was noted to be missing since the focal release. The goal is to be able to create an amd64 VM where autopkgtest can run on an i386 package. There was an existing patchset for this functionality from ~3 years ago that needed tweaking and is in a working state now[1]. 2. pocket pinning (blurb copied from commit[2]) Ubuntu is switching to NotAutomatic: yes for the proposed pocket: the change is already operative on >= Lunar and under consideration for older stable releases. This means that by default packages from -proposed won't be installed unless explicitly requested. The change is meant to make it easier for end users to keep -proposed enabled (for SRU verification or individual package installation) without manually adding a pin to avoid pulling in all of -proposed. However when running autopkgtests with --apt-pocket=proposed we do want to pull in all the pocket, so let's always give it Pin-Priority: 500. This is similar to what Launchpad does with the buildds. Note: This change does not really treat -proposed in a special way: any pocket will get Pin-Priority: 500. It makes sense to keep the tool behavior consistent, and we're not aware of cases where this could be cause issues. [0] https://wiki.ubuntu.com/i386 [1] https://code.launchpad.net/~ubuntu-release/autopkgtest/+git/development/+merge/376169 [2] https://git.launchpad.net/~ubuntu-release/autopkgtest/+git/development/commit/?id=c92df58ae5f3bc55aa58bbfb93ca60cb38b2615c [ Test Plan ] 1. cross-architecture testing Create an amd64 VM where autopkgtest can run on an i386 package: ## Generate the VM $ sudo autopkgtest-buildvm-ubuntu-cloud -a amd64 -r kinetic -s 15G ## Run autopkgtest on the i386 vlc package, finishes quickly ## Note that you should run the autopkgtest binary directly (so use the path to your ## runner/autopkgtest) and point to the .img file created in the last step $ sudo ~/autopkgtest-5.25ubuntu1/runner/autopkgtest --setup-commands="dpkg --add-architecture i386; apt-get update" --architecture i386 vlc -- qemu --ram-size=1536 --cpus 2 ~/autopkgtest-kinetic-amd64.img A passing result looks like autopkgtest setting up the testbed and launching the tests while a failing result looks something like this: autopkgtest: error: unrecognized arguments: --architecture 2. pocket pinning testing Using the --apt-pocket=proposed option, you should see that the proposed pocket is used when running autopkgtests. Also if there are any packages in proposed, then you should be able to track the pocket and update without pulling in any proposed packages. [ Where problems could occur ] 1. cross-architecture testing It is possible for the img file to find itself in a bad state, affecting the tests run, but simply recreating the VM is a quick fix. Without this patchset i386 testing less accessible, since i386 hardware is required, so the improvement greatly outweighs potentially introduced risk. 2. pocket pinning We are not aware of any issues that may arise from this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2015285/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
