0s autopkgtest [12:49:18]: starting date and time: 2026-01-29 12:49:18+0000 0s autopkgtest [12:49:18]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [12:49:18]: host juju-7f2275-prod-proposed-migration-environment-15; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.oc8u78dc/out --timeout-copy=6000 --needs-internet=try -a i386 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:pkgconf --apt-upgrade idzebra --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 --env=ADT_TEST_TRIGGERS=pkgconf/2.5.1-2 -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest-cpu2-ram4-disk20-amd64 --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-15@sto01-14.secgroup --name adt-resolute-i386-idzebra-20260129-124918-juju-7f2275-prod-proposed-migration-environment-15-b24a14fd-a674-41f1-9690-b60f33da05b6 --image adt/ubuntu-resolute-amd64-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-15 --net-id=net_prod-autopkgtest-workers-amd64 -e TERM=linux --mirror=http://ftpmaster.internal/ubuntu/ 3s Creating nova instance adt-resolute-i386-idzebra-20260129-124918-juju-7f2275-prod-proposed-migration-environment-15-b24a14fd-a674-41f1-9690-b60f33da05b6 from image adt/ubuntu-resolute-amd64-server-20260129.img (UUID c052dd91-e629-41e8-9bf0-bad94c4bd713)... 78s autopkgtest [12:50:36]: testbed dpkg architecture: amd64 79s autopkgtest [12:50:37]: testbed apt version: 3.1.14 79s autopkgtest [12:50:37]: @@@@@@@@@@@@@@@@@@@@ test bed setup 79s autopkgtest [12:50:37]: testbed release detected to be: None 80s autopkgtest [12:50:38]: updating testbed package index (apt update) 80s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [124 kB] 80s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 80s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 80s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 80s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [2820 B] 80s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [106 kB] 80s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [1074 kB] 81s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [25.4 kB] 81s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 Packages [132 kB] 81s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/main i386 Packages [114 kB] 81s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 c-n-f Metadata [4360 B] 81s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/restricted i386 Packages [3696 B] 81s Get:13 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 Packages [12.3 kB] 81s Get:14 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 c-n-f Metadata [336 B] 81s Get:15 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 Packages [872 kB] 81s Get:16 http://ftpmaster.internal/ubuntu resolute-proposed/universe i386 Packages [357 kB] 81s Get:17 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 c-n-f Metadata [23.0 kB] 81s Get:18 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse i386 Packages [3336 B] 81s Get:19 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 Packages [23.2 kB] 82s Get:20 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 c-n-f Metadata [1036 B] 82s Fetched 2880 kB in 2s (1774 kB/s) 83s Reading package lists... 83s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 83s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 84s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 84s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 84s Reading package lists... 84s Reading package lists... 84s Building dependency tree... 84s Reading state information... 84s Calculating upgrade... 84s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 84s autopkgtest [12:50:42]: upgrading testbed (apt dist-upgrade and autopurge) 85s Reading package lists... 85s Building dependency tree... 85s Reading state information... 85s Calculating upgrade... 85s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 85s Reading package lists... 85s Building dependency tree... 85s Reading state information... 85s Solving dependencies... 85s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 87s autopkgtest [12:50:45]: testbed running kernel: Linux 6.18.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 12 16:49:02 UTC 2026 87s autopkgtest [12:50:45]: @@@@@@@@@@@@@@@@@@@@ apt-source idzebra 94s Get:1 http://ftpmaster.internal/ubuntu resolute/universe idzebra 2.2.8-2 (dsc) [3552 B] 94s Get:2 http://ftpmaster.internal/ubuntu resolute/universe idzebra 2.2.8-2 (tar) [1980 kB] 94s Get:3 http://ftpmaster.internal/ubuntu resolute/universe idzebra 2.2.8-2 (diff) [13.5 kB] 94s gpgv: Signature made Tue Nov 4 05:24:54 2025 UTC 94s gpgv: using RSA key 3A20813CA57946868C5152115AC61074C5E81BC4 94s gpgv: issuer "hmc@debian.org" 94s gpgv: Can't check signature: No public key 94s dpkg-source: warning: cannot verify inline signature for ./idzebra_2.2.8-2.dsc: no acceptable signature found 94s autopkgtest [12:50:52]: testing package idzebra version 2.2.8-2 95s autopkgtest [12:50:53]: build not needed 96s autopkgtest [12:50:54]: test libidzebra-2.0-dev: preparing testbed 96s Reading package lists... 96s Building dependency tree... 96s Reading state information... 96s Solving dependencies... 96s Some packages could not be installed. This may mean that you have 96s requested an impossible situation or if you are using the unstable 96s distribution that some required packages have not yet been created 96s or been moved out of Incoming. 96s The following information may help to resolve the situation: 96s 96s The following packages have unmet dependencies: 96s satisfy:command-line : Depends: libidzebra-2.0-dev:i386 but it is not installable 96s Depends: pkgconf but it is not going to be installed 96s Depends: build-essential:amd64 96s Depends: crossbuild-essential-i386:amd64 96s Depends: libc-dev:i386 96s Depends: libstdc++-dev:i386 96s E: Unable to satisfy dependencies. Reached two conflicting assignments: 97s 1. satisfy:command-line:amd64=1 is selected for install 97s 2. satisfy:command-line:amd64 Depends libidzebra-2.0-dev:i386 97s but none of the choices are installable: 97s [no choices] 97s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 97s Reading package lists... 97s Building dependency tree... 97s Reading state information... 97s Solving dependencies... 97s Some packages could not be installed. This may mean that you have 97s requested an impossible situation or if you are using the unstable 97s distribution that some required packages have not yet been created 97s or been moved out of Incoming. 97s The following information may help to resolve the situation: 97s 97s The following packages have unmet dependencies: 97s satisfy:command-line : Depends: libidzebra-2.0-dev:i386 but it is not installable 97s Depends: pkgconf but it is not going to be installed 97s Depends: build-essential:amd64 97s Depends: crossbuild-essential-i386:amd64 97s Depends: libc-dev:i386 97s Depends: libstdc++-dev:i386 97s E: Unable to satisfy dependencies. Reached two conflicting assignments: 97s 1. satisfy:command-line:amd64=1 is selected for install 97s 2. satisfy:command-line:amd64 Depends libidzebra-2.0-dev:i386 97s but none of the choices are installable: 97s [no choices] 97s libidzebra-2.0-dev FAIL badpkg 97s blame: idzebra 97s badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U. 97s autopkgtest [12:50:55]: @@@@@@@@@@@@@@@@@@@@ summary 97s libidzebra-2.0-dev FAIL badpkg 97s blame: idzebra 97s badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U.