0s autopkgtest [13:01:58]: starting date and time: 2026-01-29 13:01:58+0000 0s autopkgtest [13:01:58]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [13:01:58]: host juju-7f2275-prod-proposed-migration-environment-2; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.l1e3w88o/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 libgnomekbd --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-2@sto01-12.secgroup --name adt-resolute-i386-libgnomekbd-20260129-130157-juju-7f2275-prod-proposed-migration-environment-2-7fec25ba-85ab-439a-a6c4-a594f2019cfe --image adt/ubuntu-resolute-amd64-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-2 --net-id=net_prod-autopkgtest-workers-amd64 -e TERM=linux --mirror=http://ftpmaster.internal/ubuntu/ 3s Creating nova instance adt-resolute-i386-libgnomekbd-20260129-130157-juju-7f2275-prod-proposed-migration-environment-2-7fec25ba-85ab-439a-a6c4-a594f2019cfe from image adt/ubuntu-resolute-amd64-server-20260129.img (UUID c052dd91-e629-41e8-9bf0-bad94c4bd713)... 76s autopkgtest [13:03:14]: testbed dpkg architecture: amd64 76s autopkgtest [13:03:14]: testbed apt version: 3.1.14 76s autopkgtest [13:03:14]: @@@@@@@@@@@@@@@@@@@@ test bed setup 76s autopkgtest [13:03:14]: testbed release detected to be: None 77s autopkgtest [13:03:15]: updating testbed package index (apt update) 77s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [124 kB] 77s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 77s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 77s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 77s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [2820 B] 77s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [1074 kB] 77s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [25.4 kB] 77s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [106 kB] 77s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main i386 Packages [114 kB] 77s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 Packages [132 kB] 77s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 c-n-f Metadata [4360 B] 77s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/restricted i386 Packages [3696 B] 77s Get:13 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 Packages [12.3 kB] 78s Get:14 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 c-n-f Metadata [336 B] 78s Get:15 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 Packages [872 kB] 78s Get:16 http://ftpmaster.internal/ubuntu resolute-proposed/universe i386 Packages [357 kB] 78s Get:17 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 c-n-f Metadata [23.0 kB] 78s Get:18 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 Packages [23.2 kB] 78s Get:19 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse i386 Packages [3336 B] 78s Get:20 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 c-n-f Metadata [1036 B] 78s Fetched 2880 kB in 1s (3817 kB/s) 79s Reading package lists... 79s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 79s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 79s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 79s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 80s Reading package lists... 80s Reading package lists... 80s Building dependency tree... 80s Reading state information... 80s Calculating upgrade... 80s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 80s autopkgtest [13:03:18]: upgrading testbed (apt dist-upgrade and autopurge) 80s Reading package lists... 81s Building dependency tree... 81s Reading state information... 81s Calculating upgrade... 81s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 81s Reading package lists... 81s Building dependency tree... 81s Reading state information... 81s Solving dependencies... 81s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 83s autopkgtest [13:03:21]: testbed running kernel: Linux 6.18.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 12 16:49:02 UTC 2026 83s autopkgtest [13:03:21]: @@@@@@@@@@@@@@@@@@@@ apt-source libgnomekbd 86s Get:1 http://ftpmaster.internal/ubuntu resolute/universe libgnomekbd 3.28.1-3 (dsc) [2622 B] 86s Get:2 http://ftpmaster.internal/ubuntu resolute/universe libgnomekbd 3.28.1-3 (tar) [155 kB] 86s Get:3 http://ftpmaster.internal/ubuntu resolute/universe libgnomekbd 3.28.1-3 (diff) [10.3 kB] 86s gpgv: Signature made Fri Sep 12 21:33:56 2025 UTC 86s gpgv: using RSA key 4D0BE12F0E4776D8AACE9696E66C775AEBFE6C7D 86s gpgv: Can't check signature: No public key 86s dpkg-source: warning: cannot verify inline signature for ./libgnomekbd_3.28.1-3.dsc: no acceptable signature found 86s autopkgtest [13:03:24]: testing package libgnomekbd version 3.28.1-3 86s autopkgtest [13:03:24]: build not needed 87s autopkgtest [13:03:25]: test libgnomekbd-dev: preparing testbed 87s Reading package lists... 87s Building dependency tree... 87s Reading state information... 87s Solving dependencies... 87s Some packages could not be installed. This may mean that you have 87s requested an impossible situation or if you are using the unstable 87s distribution that some required packages have not yet been created 87s or been moved out of Incoming. 87s The following information may help to resolve the situation: 87s 87s The following packages have unmet dependencies: 87s satisfy:command-line : Depends: libgnomekbd-dev:i386 but it is not installable 87s Depends: pkgconf but it is not going to be installed 87s Depends: build-essential:amd64 87s Depends: crossbuild-essential-i386:amd64 87s Depends: libc-dev:i386 87s Depends: libstdc++-dev:i386 87s E: Unable to satisfy dependencies. Reached two conflicting assignments: 87s 1. satisfy:command-line:amd64=1 is selected for install 87s 2. satisfy:command-line:amd64 Depends libgnomekbd-dev:i386 87s but none of the choices are installable: 87s [no choices] 87s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 87s Reading package lists... 88s Building dependency tree... 88s Reading state information... 88s Solving dependencies... 88s Some packages could not be installed. This may mean that you have 88s requested an impossible situation or if you are using the unstable 88s distribution that some required packages have not yet been created 88s or been moved out of Incoming. 88s The following information may help to resolve the situation: 88s 88s The following packages have unmet dependencies: 88s satisfy:command-line : Depends: libgnomekbd-dev:i386 but it is not installable 88s Depends: pkgconf but it is not going to be installed 88s Depends: build-essential:amd64 88s Depends: crossbuild-essential-i386:amd64 88s Depends: libc-dev:i386 88s Depends: libstdc++-dev:i386 88s E: Unable to satisfy dependencies. Reached two conflicting assignments: 88s 1. satisfy:command-line:amd64=1 is selected for install 88s 2. satisfy:command-line:amd64 Depends libgnomekbd-dev:i386 88s but none of the choices are installable: 88s [no choices] 88s libgnomekbd-dev FAIL badpkg 88s blame: libgnomekbd 88s 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. 88s autopkgtest [13:03:26]: @@@@@@@@@@@@@@@@@@@@ summary 88s libgnomekbd-dev FAIL badpkg 88s blame: libgnomekbd 88s 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.