0s autopkgtest [17:08:07]: starting date and time: 2025-11-17 17:08:07+0000 0s autopkgtest [17:08:07]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [17:08:07]: host juju-7f2275-prod-proposed-migration-environment-15; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.o8vqv12f/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:gearman-server --apt-upgrade gearman-server --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 --env=ADT_TEST_TRIGGERS=gearman-server/1.130.1-5 -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-15@bos03-arm64-6.secgroup --name adt-resolute-arm64-gearman-server-20251117-170807-juju-7f2275-prod-proposed-migration-environment-15-1e32fa46-10a0-41ef-8137-d36b585670e3 --image adt/ubuntu-resolute-arm64-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-15 --net-id=net_prod-proposed-migration -e TERM=linux --mirror=http://ftpmaster.internal/ubuntu/ 4s Creating nova instance adt-resolute-arm64-gearman-server-20251117-170807-juju-7f2275-prod-proposed-migration-environment-15-1e32fa46-10a0-41ef-8137-d36b585670e3 from image adt/ubuntu-resolute-arm64-server-20251117.img (UUID 1cd33fbb-18df-4c5a-b8f0-2dcb25269485)... 76s autopkgtest [17:09:23]: testbed dpkg architecture: arm64 76s autopkgtest [17:09:23]: testbed apt version: 3.1.11 77s autopkgtest [17:09:24]: @@@@@@@@@@@@@@@@@@@@ test bed setup 77s autopkgtest [17:09:24]: testbed release detected to be: None 78s autopkgtest [17:09:25]: updating testbed package index (apt update) 78s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [87.8 kB] 78s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 78s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 78s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 79s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [22.9 kB] 79s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [9852 B] 79s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [73.2 kB] 79s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [779 kB] 79s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main arm64 Packages [143 kB] 79s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/main arm64 c-n-f Metadata [3224 B] 79s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/restricted arm64 Packages [107 kB] 79s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/restricted arm64 c-n-f Metadata [324 B] 79s Get:13 http://ftpmaster.internal/ubuntu resolute-proposed/universe arm64 Packages [517 kB] 79s Get:14 http://ftpmaster.internal/ubuntu resolute-proposed/universe arm64 c-n-f Metadata [17.1 kB] 79s Get:15 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse arm64 Packages [12.5 kB] 79s Get:16 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse arm64 c-n-f Metadata [576 B] 80s Fetched 1774 kB in 1s (1572 kB/s) 81s Reading package lists... 82s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 82s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 82s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 82s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 83s Reading package lists... 83s Reading package lists... 83s Building dependency tree... 83s Reading state information... 83s Calculating upgrade... 84s The following packages will be upgraded: 84s apt libapt-pkg7.0 libcrypt-dev libcrypt1 usbutils 84s 5 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 84s Need to get 2764 kB of archives. 84s After this operation, 104 kB of additional disk space will be used. 84s Get:1 http://ftpmaster.internal/ubuntu resolute/main arm64 libcrypt-dev arm64 1:4.5.1-1 [123 kB] 84s Get:2 http://ftpmaster.internal/ubuntu resolute/main arm64 libcrypt1 arm64 1:4.5.1-1 [88.3 kB] 84s Get:3 http://ftpmaster.internal/ubuntu resolute/main arm64 libapt-pkg7.0 arm64 3.1.12 [1063 kB] 85s Get:4 http://ftpmaster.internal/ubuntu resolute/main arm64 apt arm64 3.1.12 [1407 kB] 85s Get:5 http://ftpmaster.internal/ubuntu resolute/main arm64 usbutils arm64 1:019-1 [81.7 kB] 85s dpkg-preconfigure: unable to re-open stdin: No such file or directory 85s Fetched 2764 kB in 1s (2507 kB/s) 86s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 88137 files and directories currently installed.) 86s Preparing to unpack .../libcrypt-dev_1%3a4.5.1-1_arm64.deb ... 86s Unpacking libcrypt-dev:arm64 (1:4.5.1-1) over (1:4.4.38-1build1) ... 86s Preparing to unpack .../libcrypt1_1%3a4.5.1-1_arm64.deb ... 86s Unpacking libcrypt1:arm64 (1:4.5.1-1) over (1:4.4.38-1build1) ... 86s Setting up libcrypt1:arm64 (1:4.5.1-1) ... 86s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 88137 files and directories currently installed.) 86s Preparing to unpack .../libapt-pkg7.0_3.1.12_arm64.deb ... 86s Unpacking libapt-pkg7.0:arm64 (3.1.12) over (3.1.11) ... 86s Preparing to unpack .../archives/apt_3.1.12_arm64.deb ... 86s Unpacking apt (3.1.12) over (3.1.11) ... 87s Preparing to unpack .../usbutils_1%3a019-1_arm64.deb ... 87s Unpacking usbutils (1:019-1) over (1:018-2) ... 87s Setting up usbutils (1:019-1) ... 87s Setting up libcrypt-dev:arm64 (1:4.5.1-1) ... 87s Setting up libapt-pkg7.0:arm64 (3.1.12) ... 87s Setting up apt (3.1.12) ... 87s Processing triggers for man-db (2.13.1-1) ... 90s Processing triggers for libc-bin (2.42-2ubuntu2) ... 90s autopkgtest [17:09:37]: upgrading testbed (apt dist-upgrade and autopurge) 91s Reading package lists... 91s Building dependency tree... 91s Reading state information... 91s Calculating upgrade... 92s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 92s Reading package lists... 92s Building dependency tree... 92s Reading state information... 92s Solving dependencies... 93s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 93s autopkgtest [17:09:40]: rebooting testbed after setup commands that affected boot 122s autopkgtest [17:10:09]: testbed running kernel: Linux 6.17.0-5-generic #5-Ubuntu SMP PREEMPT_DYNAMIC Mon Sep 22 09:50:31 UTC 2025 125s autopkgtest [17:10:12]: @@@@@@@@@@@@@@@@@@@@ apt-source gearman-server 127s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed/universe gearman-server 1.130.1-5 (dsc) [2478 B] 127s Get:2 http://ftpmaster.internal/ubuntu resolute-proposed/universe gearman-server 1.130.1-5 (tar) [17.6 kB] 127s Get:3 http://ftpmaster.internal/ubuntu resolute-proposed/universe gearman-server 1.130.1-5 (diff) [5932 B] 127s gpgv: Signature made Sun Sep 28 16:39:00 2025 UTC 127s gpgv: using RSA key D1E1316E93A760A8104D85FABB3A68018649AA06 127s gpgv: Can't check signature: No public key 127s dpkg-source: warning: cannot verify inline signature for ./gearman-server_1.130.1-5.dsc: no acceptable signature found 127s autopkgtest [17:10:14]: testing package gearman-server version 1.130.1-5 127s autopkgtest [17:10:14]: build not needed 128s autopkgtest [17:10:15]: test autodep8-perl-build-deps: preparing testbed 128s Reading package lists... 128s Building dependency tree... 128s Reading state information... 128s Solving dependencies... 128s Some packages could not be installed. This may mean that you have 128s requested an impossible situation or if you are using the unstable 128s distribution that some required packages have not yet been created 128s or been moved out of Incoming. 128s The following information may help to resolve the situation: 128s 128s The following packages have unmet dependencies: 129s satisfy:command-line : Depends: gearman-server but it is not going to be installed 129s Depends: debhelper-compat (= 13) 129s Depends: libdanga-socket-perl but it is not going to be installed 129s Depends: libgearman-client-perl but it is not going to be installed 129s Depends: libtest-script-perl but it is not going to be installed 129s Depends: build-essential but it is not going to be installed 129s Depends: pkg-perl-autopkgtest but it is not going to be installed 129s E: Unable to satisfy dependencies. Reached two conflicting decisions: 129s 1. gearman-server:arm64 is selected for install because: 129s 1. satisfy:command-line:arm64=1 is selected for install 129s 2. satisfy:command-line:arm64 Depends gearman-server 129s 2. gearman-server:arm64 is available in versions 1.130.1-5, 1.130.1-2 129s but none of the choices are installable: 129s - gearman-server:arm64=1.130.1-5 is not selected for install because: 129s 1. satisfy:command-line:arm64=1 is selected for install as above 129s 2. satisfy:command-line:arm64 Depends libgearman-client-perl 129s 3. libgearman-client-perl:arm64 is available in version 2.004.015-1 129s 4. gearman-server:arm64=1.130.1-5 Breaks libgearman-client-perl (< 2.004.015-2) 129s - gearman-server:arm64=1.130.1-2 is not selected for install 129s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 129s Reading package lists... 129s Building dependency tree... 129s Reading state information... 130s Solving dependencies... 130s Some packages could not be installed. This may mean that you have 130s requested an impossible situation or if you are using the unstable 130s distribution that some required packages have not yet been created 130s or been moved out of Incoming. 130s The following information may help to resolve the situation: 130s 130s The following packages have unmet dependencies: 130s satisfy:command-line : Depends: gearman-server but it is not going to be installed 130s Depends: debhelper-compat (= 13) 130s Depends: libdanga-socket-perl but it is not going to be installed 130s Depends: libgearman-client-perl but it is not going to be installed 130s Depends: libtest-script-perl but it is not going to be installed 130s Depends: build-essential but it is not going to be installed 130s Depends: pkg-perl-autopkgtest but it is not going to be installed 130s E: Unable to satisfy dependencies. Reached two conflicting decisions: 130s 1. gearman-server:arm64 is selected for install because: 130s 1. satisfy:command-line:arm64=1 is selected for install 130s 2. satisfy:command-line:arm64 Depends gearman-server 130s 2. gearman-server:arm64 is available in versions 1.130.1-5, 1.130.1-2 130s but none of the choices are installable: 130s - gearman-server:arm64=1.130.1-5 is not selected for install because: 130s 1. satisfy:command-line:arm64=1 is selected for install as above 130s 2. satisfy:command-line:arm64 Depends libgearman-client-perl 130s 3. libgearman-client-perl:arm64 is available in version 2.004.015-1 130s 4. gearman-server:arm64=1.130.1-5 Breaks libgearman-client-perl (< 2.004.015-2) 130s - gearman-server:arm64=1.130.1-2 is not selected for install 130s autopkgtest [17:10:17]: test autodep8-perl: preparing testbed 130s autodep8-perl-build-deps FAIL badpkg 130s blame: gearman-server 130s 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. 150s Creating nova instance adt-resolute-arm64-gearman-server-20251117-170807-juju-7f2275-prod-proposed-migration-environment-15-1e32fa46-10a0-41ef-8137-d36b585670e3 from image adt/ubuntu-resolute-arm64-server-20251117.img (UUID 1cd33fbb-18df-4c5a-b8f0-2dcb25269485)... 206s autopkgtest [17:11:33]: testbed dpkg architecture: arm64 206s autopkgtest [17:11:33]: testbed apt version: 3.1.11 207s autopkgtest [17:11:34]: @@@@@@@@@@@@@@@@@@@@ test bed setup 207s autopkgtest [17:11:34]: testbed release detected to be: resolute 208s autopkgtest [17:11:35]: updating testbed package index (apt update) 208s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [87.8 kB] 208s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 209s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 209s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 209s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [779 kB] 209s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [73.2 kB] 209s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [9852 B] 209s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [22.9 kB] 209s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main arm64 Packages [143 kB] 209s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/main arm64 c-n-f Metadata [3224 B] 209s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/restricted arm64 Packages [107 kB] 209s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/restricted arm64 c-n-f Metadata [324 B] 209s Get:13 http://ftpmaster.internal/ubuntu resolute-proposed/universe arm64 Packages [517 kB] 210s Get:14 http://ftpmaster.internal/ubuntu resolute-proposed/universe arm64 c-n-f Metadata [17.1 kB] 210s Get:15 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse arm64 Packages [12.5 kB] 210s Get:16 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse arm64 c-n-f Metadata [576 B] 211s Fetched 1774 kB in 2s (985 kB/s) 212s Reading package lists... 213s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 213s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 213s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 213s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 214s Reading package lists... 215s Reading package lists... 215s Building dependency tree... 215s Reading state information... 215s Calculating upgrade... 216s The following packages will be upgraded: 216s apt libapt-pkg7.0 libcrypt-dev libcrypt1 usbutils 217s 5 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 217s Need to get 2764 kB of archives. 217s After this operation, 104 kB of additional disk space will be used. 217s Get:1 http://ftpmaster.internal/ubuntu resolute/main arm64 libcrypt-dev arm64 1:4.5.1-1 [123 kB] 217s Get:2 http://ftpmaster.internal/ubuntu resolute/main arm64 libcrypt1 arm64 1:4.5.1-1 [88.3 kB] 217s Get:3 http://ftpmaster.internal/ubuntu resolute/main arm64 libapt-pkg7.0 arm64 3.1.12 [1063 kB] 218s Get:4 http://ftpmaster.internal/ubuntu resolute/main arm64 apt arm64 3.1.12 [1407 kB] 218s Get:5 http://ftpmaster.internal/ubuntu resolute/main arm64 usbutils arm64 1:019-1 [81.7 kB] 219s dpkg-preconfigure: unable to re-open stdin: No such file or directory 219s Fetched 2764 kB in 2s (1387 kB/s) 219s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 88137 files and directories currently installed.) 219s Preparing to unpack .../libcrypt-dev_1%3a4.5.1-1_arm64.deb ... 219s Unpacking libcrypt-dev:arm64 (1:4.5.1-1) over (1:4.4.38-1build1) ... 220s Preparing to unpack .../libcrypt1_1%3a4.5.1-1_arm64.deb ... 220s Unpacking libcrypt1:arm64 (1:4.5.1-1) over (1:4.4.38-1build1) ... 220s Setting up libcrypt1:arm64 (1:4.5.1-1) ... 220s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 88137 files and directories currently installed.) 220s Preparing to unpack .../libapt-pkg7.0_3.1.12_arm64.deb ... 220s Unpacking libapt-pkg7.0:arm64 (3.1.12) over (3.1.11) ... 220s Preparing to unpack .../archives/apt_3.1.12_arm64.deb ... 220s Unpacking apt (3.1.12) over (3.1.11) ... 220s Preparing to unpack .../usbutils_1%3a019-1_arm64.deb ... 220s Unpacking usbutils (1:019-1) over (1:018-2) ... 221s Setting up usbutils (1:019-1) ... 221s Setting up libcrypt-dev:arm64 (1:4.5.1-1) ... 221s Setting up libapt-pkg7.0:arm64 (3.1.12) ... 221s Setting up apt (3.1.12) ... 222s Processing triggers for man-db (2.13.1-1) ... 224s Processing triggers for libc-bin (2.42-2ubuntu2) ... 224s autopkgtest [17:11:51]: upgrading testbed (apt dist-upgrade and autopurge) 226s Reading package lists... 226s Building dependency tree... 226s Reading state information... 227s Calculating upgrade... 228s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 228s Reading package lists... 229s Building dependency tree... 229s Reading state information... 229s Solving dependencies... 230s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 230s autopkgtest [17:11:57]: rebooting testbed after setup commands that affected boot 267s Reading package lists... 268s Building dependency tree... 268s Reading state information... 268s Solving dependencies... 268s Some packages could not be installed. This may mean that you have 268s requested an impossible situation or if you are using the unstable 268s distribution that some required packages have not yet been created 268s or been moved out of Incoming. 268s The following information may help to resolve the situation: 268s 268s The following packages have unmet dependencies: 268s satisfy:command-line : Depends: gearman-server but it is not going to be installed 268s Depends: pkg-perl-autopkgtest but it is not going to be installed 268s E: Unable to satisfy dependencies. Reached two conflicting decisions: 268s 1. gearman-server:arm64 is selected for install because: 268s 1. satisfy:command-line:arm64=1 is selected for install 268s 2. satisfy:command-line:arm64 Depends gearman-server 268s 2. gearman-server:arm64 is available in versions 1.130.1-5, 1.130.1-2 268s but none of the choices are installable: 268s - gearman-server:arm64=1.130.1-5 is not selected for install because: 268s 1. satisfy:command-line:arm64=1 is selected for install as above 268s 1-2. gearman-server:arm64 is selected for install as above 268s 3. gearman-server:arm64 Depends libgearman-client-perl 268s 4. libgearman-client-perl:arm64 is available in version 2.004.015-1 268s 5. gearman-server:arm64=1.130.1-5 Breaks libgearman-client-perl (< 2.004.015-2) 268s - gearman-server:arm64=1.130.1-2 is not selected for install 268s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 268s Reading package lists... 269s Building dependency tree... 269s Reading state information... 269s Solving dependencies... 269s Some packages could not be installed. This may mean that you have 269s requested an impossible situation or if you are using the unstable 269s distribution that some required packages have not yet been created 269s or been moved out of Incoming. 269s The following information may help to resolve the situation: 269s 269s The following packages have unmet dependencies: 269s satisfy:command-line : Depends: gearman-server but it is not going to be installed 269s Depends: pkg-perl-autopkgtest but it is not going to be installed 269s E: Unable to satisfy dependencies. Reached two conflicting decisions: 269s 1. gearman-server:arm64 is selected for install because: 269s 1. satisfy:command-line:arm64=1 is selected for install 269s 2. satisfy:command-line:arm64 Depends gearman-server 269s 2. gearman-server:arm64 is available in versions 1.130.1-5, 1.130.1-2 269s but none of the choices are installable: 269s - gearman-server:arm64=1.130.1-5 is not selected for install because: 269s 1. satisfy:command-line:arm64=1 is selected for install as above 269s 1-2. gearman-server:arm64 is selected for install as above 269s 3. gearman-server:arm64 Depends libgearman-client-perl 269s 4. libgearman-client-perl:arm64 is available in version 2.004.015-1 269s 5. gearman-server:arm64=1.130.1-5 Breaks libgearman-client-perl (< 2.004.015-2) 269s - gearman-server:arm64=1.130.1-2 is not selected for install 269s autodep8-perl FAIL badpkg 269s blame: gearman-server 269s 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. 269s autopkgtest [17:12:36]: test autodep8-perl-recommends: preparing testbed 269s Reading package lists... 270s Building dependency tree... 270s Reading state information... 270s Solving dependencies... 270s Some packages could not be installed. This may mean that you have 270s requested an impossible situation or if you are using the unstable 270s distribution that some required packages have not yet been created 270s or been moved out of Incoming. 270s The following information may help to resolve the situation: 270s 270s The following packages have unmet dependencies: 270s satisfy:command-line : Depends: gearman-server but it is not going to be installed 270s Depends: pkg-perl-autopkgtest but it is not going to be installed 270s E: Unable to satisfy dependencies. Reached two conflicting decisions: 270s 1. gearman-server:arm64 is selected for install because: 270s 1. satisfy:command-line:arm64=1 is selected for install 270s 2. satisfy:command-line:arm64 Depends gearman-server 270s 2. gearman-server:arm64 is available in versions 1.130.1-5, 1.130.1-2 270s but none of the choices are installable: 270s - gearman-server:arm64=1.130.1-5 is not selected for install because: 270s 1. satisfy:command-line:arm64=1 is selected for install as above 270s 1-2. gearman-server:arm64 is selected for install as above 270s 3. gearman-server:arm64 Depends libgearman-client-perl 270s 4. libgearman-client-perl:arm64 is available in version 2.004.015-1 270s 5. gearman-server:arm64=1.130.1-5 Breaks libgearman-client-perl (< 2.004.015-2) 270s - gearman-server:arm64=1.130.1-2 is not selected for install 270s autodep8-perl-recommends FAIL badpkg 270s blame: gearman-server 270s 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. 270s autopkgtest [17:12:37]: @@@@@@@@@@@@@@@@@@@@ summary 270s autodep8-perl-build-deps FAIL badpkg 270s blame: gearman-server 270s 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. 270s autodep8-perl FAIL badpkg 270s blame: gearman-server 270s 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. 270s autodep8-perl-recommends FAIL badpkg 270s blame: gearman-server 270s 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.