0s autopkgtest [17:17:22]: starting date and time: 2025-11-17 17:17:22+0000 0s autopkgtest [17:17:22]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [17:17:22]: host juju-7f2275-prod-proposed-migration-environment-20; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work._ugikofu/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:node-body-parser --apt-upgrade node-telegram-bot-api --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 '--env=ADT_TEST_TRIGGERS=node-body-parser/2.2.0+~1.19.6-3' -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-20@bos03-arm64-7.secgroup --name adt-resolute-arm64-node-telegram-bot-api-20251117-164700-juju-7f2275-prod-proposed-migration-environment-20-566dabad-5b0b-4dbe-9abf-5273f20f827f --image adt/ubuntu-resolute-arm64-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-20 --net-id=net_prod-proposed-migration -e TERM=linux --mirror=http://ftpmaster.internal/ubuntu/ 3s Creating nova instance adt-resolute-arm64-node-telegram-bot-api-20251117-164700-juju-7f2275-prod-proposed-migration-environment-20-566dabad-5b0b-4dbe-9abf-5273f20f827f from image adt/ubuntu-resolute-arm64-server-20251117.img (UUID 1cd33fbb-18df-4c5a-b8f0-2dcb25269485)... 60s autopkgtest [17:18:22]: testbed dpkg architecture: arm64 61s autopkgtest [17:18:23]: testbed apt version: 3.1.11 61s autopkgtest [17:18:23]: @@@@@@@@@@@@@@@@@@@@ test bed setup 61s autopkgtest [17:18:23]: testbed release detected to be: None 62s autopkgtest [17:18:24]: updating testbed package index (apt update) 62s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [87.8 kB] 62s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 62s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 63s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 63s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [779 kB] 63s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [9852 B] 63s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [73.2 kB] 63s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [22.9 kB] 63s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main arm64 Packages [143 kB] 63s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/main arm64 c-n-f Metadata [3224 B] 63s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/restricted arm64 Packages [107 kB] 63s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/restricted arm64 c-n-f Metadata [324 B] 63s Get:13 http://ftpmaster.internal/ubuntu resolute-proposed/universe arm64 Packages [517 kB] 63s Get:14 http://ftpmaster.internal/ubuntu resolute-proposed/universe arm64 c-n-f Metadata [17.1 kB] 63s Get:15 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse arm64 Packages [12.5 kB] 63s Get:16 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse arm64 c-n-f Metadata [576 B] 64s Fetched 1774 kB in 1s (1572 kB/s) 65s Reading package lists... 66s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 66s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 66s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 66s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 67s Reading package lists... 67s Reading package lists... 67s Building dependency tree... 67s Reading state information... 67s Calculating upgrade... 68s The following packages will be upgraded: 68s apt libapt-pkg7.0 libcrypt-dev libcrypt1 usbutils 68s 5 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 68s Need to get 2764 kB of archives. 68s After this operation, 104 kB of additional disk space will be used. 68s Get:1 http://ftpmaster.internal/ubuntu resolute/main arm64 libcrypt-dev arm64 1:4.5.1-1 [123 kB] 68s Get:2 http://ftpmaster.internal/ubuntu resolute/main arm64 libcrypt1 arm64 1:4.5.1-1 [88.3 kB] 68s Get:3 http://ftpmaster.internal/ubuntu resolute/main arm64 libapt-pkg7.0 arm64 3.1.12 [1063 kB] 69s Get:4 http://ftpmaster.internal/ubuntu resolute/main arm64 apt arm64 3.1.12 [1407 kB] 69s Get:5 http://ftpmaster.internal/ubuntu resolute/main arm64 usbutils arm64 1:019-1 [81.7 kB] 70s dpkg-preconfigure: unable to re-open stdin: No such file or directory 70s Fetched 2764 kB in 2s (1648 kB/s) 70s (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.) 70s Preparing to unpack .../libcrypt-dev_1%3a4.5.1-1_arm64.deb ... 70s Unpacking libcrypt-dev:arm64 (1:4.5.1-1) over (1:4.4.38-1build1) ... 70s Preparing to unpack .../libcrypt1_1%3a4.5.1-1_arm64.deb ... 70s Unpacking libcrypt1:arm64 (1:4.5.1-1) over (1:4.4.38-1build1) ... 70s Setting up libcrypt1:arm64 (1:4.5.1-1) ... 70s (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.) 71s Preparing to unpack .../libapt-pkg7.0_3.1.12_arm64.deb ... 71s Unpacking libapt-pkg7.0:arm64 (3.1.12) over (3.1.11) ... 71s Preparing to unpack .../archives/apt_3.1.12_arm64.deb ... 71s Unpacking apt (3.1.12) over (3.1.11) ... 71s Preparing to unpack .../usbutils_1%3a019-1_arm64.deb ... 71s Unpacking usbutils (1:019-1) over (1:018-2) ... 71s Setting up usbutils (1:019-1) ... 71s Setting up libcrypt-dev:arm64 (1:4.5.1-1) ... 71s Setting up libapt-pkg7.0:arm64 (3.1.12) ... 71s Setting up apt (3.1.12) ... 72s Processing triggers for man-db (2.13.1-1) ... 74s Processing triggers for libc-bin (2.42-2ubuntu2) ... 74s autopkgtest [17:18:36]: upgrading testbed (apt dist-upgrade and autopurge) 75s Reading package lists... 75s Building dependency tree... 75s Reading state information... 75s Calculating upgrade... 76s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 76s Reading package lists... 76s Building dependency tree... 76s Reading state information... 76s Solving dependencies... 77s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 77s autopkgtest [17:18:39]: rebooting testbed after setup commands that affected boot 109s autopkgtest [17:19:11]: testbed running kernel: Linux 6.17.0-5-generic #5-Ubuntu SMP PREEMPT_DYNAMIC Mon Sep 22 09:50:31 UTC 2025 112s autopkgtest [17:19:14]: @@@@@@@@@@@@@@@@@@@@ apt-source node-telegram-bot-api 115s Get:1 http://ftpmaster.internal/ubuntu resolute/universe node-telegram-bot-api 2.0.1-3 (dsc) [2308 B] 115s Get:2 http://ftpmaster.internal/ubuntu resolute/universe node-telegram-bot-api 2.0.1-3 (tar) [2810 kB] 115s Get:3 http://ftpmaster.internal/ubuntu resolute/universe node-telegram-bot-api 2.0.1-3 (diff) [3968 B] 115s gpgv: Signature made Fri Nov 4 13:56:49 2022 UTC 115s gpgv: using RSA key 00DFE58B8B555779D1005EC9F6D74CA7C999EEE9 115s gpgv: Can't check signature: No public key 115s dpkg-source: warning: cannot verify inline signature for ./node-telegram-bot-api_2.0.1-3.dsc: no acceptable signature found 115s autopkgtest [17:19:17]: testing package node-telegram-bot-api version 2.0.1-3 116s autopkgtest [17:19:18]: build not needed 116s autopkgtest [17:19:18]: test command1: preparing testbed 117s Reading package lists... 117s Building dependency tree... 117s Reading state information... 117s Solving dependencies... 117s Some packages could not be installed. This may mean that you have 117s requested an impossible situation or if you are using the unstable 117s distribution that some required packages have not yet been created 117s or been moved out of Incoming. 117s The following information may help to resolve the situation: 117s 117s The following packages have unmet dependencies: 117s satisfy:command-line : Depends: node-telegram-bot-api but it is not going to be installed 117s Depends: nodejs but it is not going to be installed 117s E: Unable to satisfy dependencies. Reached two conflicting decisions: 117s 1. node-body-parser:arm64 is selected for install because: 117s 1. satisfy:command-line:arm64=1 is selected for install 117s 2. satisfy:command-line:arm64 Depends node-telegram-bot-api 117s 3. node-telegram-bot-api:arm64 Depends node-body-parser 117s 2. node-body-parser:arm64 is available in versions 2.2.0+~1.19.6-3, 1.20.3+~1.19.5-3 117s but none of the choices are installable: 117s - node-body-parser:arm64=2.2.0+~1.19.6-3 is not selected for install because: 117s 1. satisfy:command-line:arm64=1 is selected for install as above 117s 1-2. node-telegram-bot-api:arm64 is selected for install as above 117s 3. node-telegram-bot-api:arm64 Depends node-express 117s 4. node-express:arm64 is available in version 4.21.2+~cs8.36.27-3 117s 5. node-body-parser:arm64=2.2.0+~1.19.6-3 Breaks node-express (< 5) 117s - node-body-parser:arm64=1.20.3+~1.19.5-3 is not selected for install 117s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 118s Reading package lists... 118s Building dependency tree... 118s Reading state information... 118s Solving dependencies... 118s Some packages could not be installed. This may mean that you have 118s requested an impossible situation or if you are using the unstable 118s distribution that some required packages have not yet been created 118s or been moved out of Incoming. 118s The following information may help to resolve the situation: 118s 118s The following packages have unmet dependencies: 119s satisfy:command-line : Depends: node-telegram-bot-api but it is not going to be installed 119s Depends: nodejs but it is not going to be installed 119s E: Unable to satisfy dependencies. Reached two conflicting decisions: 119s 1. node-body-parser:arm64 is selected for install because: 119s 1. satisfy:command-line:arm64=1 is selected for install 119s 2. satisfy:command-line:arm64 Depends node-telegram-bot-api 119s 3. node-telegram-bot-api:arm64 Depends node-body-parser 119s 2. node-body-parser:arm64 is available in versions 2.2.0+~1.19.6-3, 1.20.3+~1.19.5-3 119s but none of the choices are installable: 119s - node-body-parser:arm64=2.2.0+~1.19.6-3 is not selected for install because: 119s 1. satisfy:command-line:arm64=1 is selected for install as above 119s 1-2. node-telegram-bot-api:arm64 is selected for install as above 119s 3. node-telegram-bot-api:arm64 Depends node-express 119s 4. node-express:arm64 is available in version 4.21.2+~cs8.36.27-3 119s 5. node-body-parser:arm64=2.2.0+~1.19.6-3 Breaks node-express (< 5) 119s - node-body-parser:arm64=1.20.3+~1.19.5-3 is not selected for install 119s command1 FAIL badpkg 119s blame: node-telegram-bot-api 119s 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. 119s autopkgtest [17:19:21]: test pkg-js-autopkgtest-require: preparing testbed 120s Reading package lists... 120s Building dependency tree... 120s Reading state information... 120s Solving dependencies... 120s Some packages could not be installed. This may mean that you have 120s requested an impossible situation or if you are using the unstable 120s distribution that some required packages have not yet been created 120s or been moved out of Incoming. 120s The following information may help to resolve the situation: 120s 120s The following packages have unmet dependencies: 120s satisfy:command-line : Depends: node-telegram-bot-api but it is not going to be installed 120s Depends: nodejs but it is not going to be installed 120s Depends: pkg-js-autopkgtest but it is not going to be installed 120s E: Unable to satisfy dependencies. Reached two conflicting decisions: 120s 1. node-body-parser:arm64 is selected for install because: 120s 1. satisfy:command-line:arm64=1 is selected for install 120s 2. satisfy:command-line:arm64 Depends node-telegram-bot-api 120s 3. node-telegram-bot-api:arm64 Depends node-body-parser 120s 2. node-body-parser:arm64 is available in versions 2.2.0+~1.19.6-3, 1.20.3+~1.19.5-3 120s but none of the choices are installable: 120s - node-body-parser:arm64=2.2.0+~1.19.6-3 is not selected for install because: 120s 1. satisfy:command-line:arm64=1 is selected for install as above 120s 1-2. node-telegram-bot-api:arm64 is selected for install as above 120s 3. node-telegram-bot-api:arm64 Depends node-express 120s 4. node-express:arm64 is available in version 4.21.2+~cs8.36.27-3 120s 5. node-body-parser:arm64=2.2.0+~1.19.6-3 Breaks node-express (< 5) 120s - node-body-parser:arm64=1.20.3+~1.19.5-3 is not selected for install 120s pkg-js-autopkgtest-require FAIL badpkg 120s blame: node-telegram-bot-api 120s 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. 120s autopkgtest [17:19:22]: test pkg-js-autopkgtest: preparing testbed 128s Creating nova instance adt-resolute-arm64-node-telegram-bot-api-20251117-164700-juju-7f2275-prod-proposed-migration-environment-20-566dabad-5b0b-4dbe-9abf-5273f20f827f from image adt/ubuntu-resolute-arm64-server-20251117.img (UUID 1cd33fbb-18df-4c5a-b8f0-2dcb25269485)... 232s autopkgtest [17:21:14]: testbed dpkg architecture: arm64 232s autopkgtest [17:21:14]: testbed apt version: 3.1.11 233s autopkgtest [17:21:15]: @@@@@@@@@@@@@@@@@@@@ test bed setup 233s autopkgtest [17:21:15]: testbed release detected to be: resolute 234s autopkgtest [17:21:16]: updating testbed package index (apt update) 234s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [87.8 kB] 235s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 235s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 235s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 235s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [22.9 kB] 235s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [9852 B] 235s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [779 kB] 235s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [73.2 kB] 235s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main arm64 Packages [143 kB] 235s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/main arm64 c-n-f Metadata [3224 B] 235s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/restricted arm64 Packages [107 kB] 235s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/restricted arm64 c-n-f Metadata [324 B] 235s Get:13 http://ftpmaster.internal/ubuntu resolute-proposed/universe arm64 Packages [517 kB] 235s Get:14 http://ftpmaster.internal/ubuntu resolute-proposed/universe arm64 c-n-f Metadata [17.1 kB] 235s Get:15 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse arm64 Packages [12.5 kB] 235s Get:16 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse arm64 c-n-f Metadata [576 B] 238s Fetched 1774 kB in 1s (1207 kB/s) 239s Reading package lists... 240s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 240s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 240s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 240s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 242s Reading package lists... 242s Reading package lists... 242s Building dependency tree... 242s Reading state information... 243s Calculating upgrade... 243s The following packages will be upgraded: 243s apt libapt-pkg7.0 libcrypt-dev libcrypt1 usbutils 244s 5 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 244s Need to get 2764 kB of archives. 244s After this operation, 104 kB of additional disk space will be used. 244s Get:1 http://ftpmaster.internal/ubuntu resolute/main arm64 libcrypt-dev arm64 1:4.5.1-1 [123 kB] 244s Get:2 http://ftpmaster.internal/ubuntu resolute/main arm64 libcrypt1 arm64 1:4.5.1-1 [88.3 kB] 244s Get:3 http://ftpmaster.internal/ubuntu resolute/main arm64 libapt-pkg7.0 arm64 3.1.12 [1063 kB] 244s Get:4 http://ftpmaster.internal/ubuntu resolute/main arm64 apt arm64 3.1.12 [1407 kB] 245s Get:5 http://ftpmaster.internal/ubuntu resolute/main arm64 usbutils arm64 1:019-1 [81.7 kB] 245s dpkg-preconfigure: unable to re-open stdin: No such file or directory 245s Fetched 2764 kB in 1s (2284 kB/s) 246s (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.) 246s Preparing to unpack .../libcrypt-dev_1%3a4.5.1-1_arm64.deb ... 246s Unpacking libcrypt-dev:arm64 (1:4.5.1-1) over (1:4.4.38-1build1) ... 246s Preparing to unpack .../libcrypt1_1%3a4.5.1-1_arm64.deb ... 246s Unpacking libcrypt1:arm64 (1:4.5.1-1) over (1:4.4.38-1build1) ... 247s Setting up libcrypt1:arm64 (1:4.5.1-1) ... 247s (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.) 247s Preparing to unpack .../libapt-pkg7.0_3.1.12_arm64.deb ... 247s Unpacking libapt-pkg7.0:arm64 (3.1.12) over (3.1.11) ... 247s Preparing to unpack .../archives/apt_3.1.12_arm64.deb ... 247s Unpacking apt (3.1.12) over (3.1.11) ... 247s Preparing to unpack .../usbutils_1%3a019-1_arm64.deb ... 247s Unpacking usbutils (1:019-1) over (1:018-2) ... 247s Setting up usbutils (1:019-1) ... 247s Setting up libcrypt-dev:arm64 (1:4.5.1-1) ... 247s Setting up libapt-pkg7.0:arm64 (3.1.12) ... 247s Setting up apt (3.1.12) ... 249s Processing triggers for man-db (2.13.1-1) ... 252s Processing triggers for libc-bin (2.42-2ubuntu2) ... 253s autopkgtest [17:21:35]: upgrading testbed (apt dist-upgrade and autopurge) 254s Reading package lists... 255s Building dependency tree... 255s Reading state information... 255s Calculating upgrade... 256s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 256s Reading package lists... 256s Building dependency tree... 256s Reading state information... 257s Solving dependencies... 257s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 258s autopkgtest [17:21:40]: rebooting testbed after setup commands that affected boot 297s Reading package lists... 297s Building dependency tree... 297s Reading state information... 297s Solving dependencies... 297s Some packages could not be installed. This may mean that you have 297s requested an impossible situation or if you are using the unstable 297s distribution that some required packages have not yet been created 297s or been moved out of Incoming. 297s The following information may help to resolve the situation: 297s 297s The following packages have unmet dependencies: 298s satisfy:command-line : Depends: node-telegram-bot-api but it is not going to be installed 298s Depends: debhelper-compat (= 13) 298s Depends: dh-sequence-nodejs 298s Depends: node-axios but it is not going to be installed 298s Depends: node-bluebird but it is not going to be installed 298s Depends: node-body-parser but it is not going to be installed 298s Depends: node-express but it is not going to be installed 298s Depends: node-extend but it is not going to be installed 298s Depends: build-essential but it is not going to be installed 298s Depends: pkg-js-autopkgtest but it is not going to be installed 298s E: Unable to satisfy dependencies. Reached two conflicting decisions: 298s 1. node-body-parser:arm64 is selected for install because: 298s 1. satisfy:command-line:arm64=1 is selected for install 298s 2. satisfy:command-line:arm64 Depends node-body-parser 298s 2. node-body-parser:arm64 is available in versions 2.2.0+~1.19.6-3, 1.20.3+~1.19.5-3 298s but none of the choices are installable: 298s - node-body-parser:arm64=2.2.0+~1.19.6-3 is not selected for install because: 298s 1. satisfy:command-line:arm64=1 is selected for install as above 298s 2. satisfy:command-line:arm64 Depends node-express 298s 3. node-express:arm64 is available in version 4.21.2+~cs8.36.27-3 298s 4. node-body-parser:arm64=2.2.0+~1.19.6-3 Breaks node-express (< 5) 298s - node-body-parser:arm64=1.20.3+~1.19.5-3 is not selected for install 298s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 298s Reading package lists... 299s Building dependency tree... 299s Reading state information... 299s Solving dependencies... 299s Some packages could not be installed. This may mean that you have 299s requested an impossible situation or if you are using the unstable 299s distribution that some required packages have not yet been created 299s or been moved out of Incoming. 299s The following information may help to resolve the situation: 299s 299s The following packages have unmet dependencies: 299s satisfy:command-line : Depends: node-telegram-bot-api but it is not going to be installed 299s Depends: debhelper-compat (= 13) 299s Depends: dh-sequence-nodejs 299s Depends: node-axios but it is not going to be installed 299s Depends: node-bluebird but it is not going to be installed 299s Depends: node-body-parser but it is not going to be installed 299s Depends: node-express but it is not going to be installed 299s Depends: node-extend but it is not going to be installed 299s Depends: build-essential but it is not going to be installed 299s Depends: pkg-js-autopkgtest but it is not going to be installed 299s E: Unable to satisfy dependencies. Reached two conflicting decisions: 299s 1. node-body-parser:arm64 is selected for install because: 299s 1. satisfy:command-line:arm64=1 is selected for install 299s 2. satisfy:command-line:arm64 Depends node-body-parser 299s 2. node-body-parser:arm64 is available in versions 2.2.0+~1.19.6-3, 1.20.3+~1.19.5-3 299s but none of the choices are installable: 299s - node-body-parser:arm64=2.2.0+~1.19.6-3 is not selected for install because: 299s 1. satisfy:command-line:arm64=1 is selected for install as above 299s 2. satisfy:command-line:arm64 Depends node-express 299s 3. node-express:arm64 is available in version 4.21.2+~cs8.36.27-3 299s 4. node-body-parser:arm64=2.2.0+~1.19.6-3 Breaks node-express (< 5) 299s - node-body-parser:arm64=1.20.3+~1.19.5-3 is not selected for install 299s pkg-js-autopkgtest FAIL badpkg 299s blame: node-telegram-bot-api 299s 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. 299s autopkgtest [17:22:21]: @@@@@@@@@@@@@@@@@@@@ summary 299s command1 FAIL badpkg 299s blame: node-telegram-bot-api 299s 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. 299s pkg-js-autopkgtest-require FAIL badpkg 299s blame: node-telegram-bot-api 299s 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. 299s pkg-js-autopkgtest FAIL badpkg 299s blame: node-telegram-bot-api 299s 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.