0s autopkgtest [18:48:03]: starting date and time: 2025-11-17 18:48:03+0000 0s autopkgtest [18:48:03]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [18:48:03]: host juju-7f2275-prod-proposed-migration-environment-15; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.8ctmywy0/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-ppc64el --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-15@bos03-ppc64el-8.secgroup --name adt-resolute-ppc64el-node-telegram-bot-api-20251117-184803-juju-7f2275-prod-proposed-migration-environment-15-1fc4b42b-4485-4e35-bfa4-5b8a4257aae5 --image adt/ubuntu-resolute-ppc64el-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-15 --net-id=net_prod-proposed-migration-ppc64el -e TERM=linux --mirror=http://ftpmaster.internal/ubuntu/ 3s Creating nova instance adt-resolute-ppc64el-node-telegram-bot-api-20251117-184803-juju-7f2275-prod-proposed-migration-environment-15-1fc4b42b-4485-4e35-bfa4-5b8a4257aae5 from image adt/ubuntu-resolute-ppc64el-server-20251117.img (UUID c6f5b741-c77a-45db-84cb-f00b40e77676)... 56s autopkgtest [18:48:59]: testbed dpkg architecture: ppc64el 56s autopkgtest [18:48:59]: testbed apt version: 3.1.11 56s autopkgtest [18:48:59]: @@@@@@@@@@@@@@@@@@@@ test bed setup 56s autopkgtest [18:48:59]: testbed release detected to be: None 57s autopkgtest [18:49:00]: updating testbed package index (apt update) 57s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [87.8 kB] 58s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 58s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 58s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 58s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [9852 B] 58s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [73.2 kB] 58s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [22.9 kB] 58s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [779 kB] 58s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el Packages [135 kB] 58s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/restricted ppc64el Packages [940 B] 58s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/universe ppc64el Packages [501 kB] 59s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse ppc64el Packages [11.0 kB] 59s Fetched 1622 kB in 2s (1004 kB/s) 60s Reading package lists... 60s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 60s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 61s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 61s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 62s Reading package lists... 62s Reading package lists... 62s Building dependency tree... 62s Reading state information... 62s Calculating upgrade... 62s The following packages will be upgraded: 62s apt libapt-pkg7.0 libcrypt-dev libcrypt1 usbutils 62s 5 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 62s Need to get 3180 kB of archives. 62s After this operation, 118 kB of additional disk space will be used. 62s Get:1 http://ftpmaster.internal/ubuntu resolute/main ppc64el libcrypt-dev ppc64el 1:4.5.1-1 [162 kB] 62s Get:2 http://ftpmaster.internal/ubuntu resolute/main ppc64el libcrypt1 ppc64el 1:4.5.1-1 [125 kB] 63s Get:3 http://ftpmaster.internal/ubuntu resolute/main ppc64el libapt-pkg7.0 ppc64el 3.1.12 [1286 kB] 63s Get:4 http://ftpmaster.internal/ubuntu resolute/main ppc64el apt ppc64el 3.1.12 [1516 kB] 64s Get:5 http://ftpmaster.internal/ubuntu resolute/main ppc64el usbutils ppc64el 1:019-1 [91.5 kB] 64s dpkg-preconfigure: unable to re-open stdin: No such file or directory 64s Fetched 3180 kB in 2s (1790 kB/s) 64s (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 ... 81022 files and directories currently installed.) 64s Preparing to unpack .../libcrypt-dev_1%3a4.5.1-1_ppc64el.deb ... 64s Unpacking libcrypt-dev:ppc64el (1:4.5.1-1) over (1:4.4.38-1build1) ... 65s Preparing to unpack .../libcrypt1_1%3a4.5.1-1_ppc64el.deb ... 65s Unpacking libcrypt1:ppc64el (1:4.5.1-1) over (1:4.4.38-1build1) ... 65s Setting up libcrypt1:ppc64el (1:4.5.1-1) ... 65s (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 ... 81022 files and directories currently installed.) 65s Preparing to unpack .../libapt-pkg7.0_3.1.12_ppc64el.deb ... 65s Unpacking libapt-pkg7.0:ppc64el (3.1.12) over (3.1.11) ... 65s Preparing to unpack .../apt_3.1.12_ppc64el.deb ... 65s Unpacking apt (3.1.12) over (3.1.11) ... 65s Preparing to unpack .../usbutils_1%3a019-1_ppc64el.deb ... 65s Unpacking usbutils (1:019-1) over (1:018-2) ... 65s Setting up usbutils (1:019-1) ... 65s Setting up libcrypt-dev:ppc64el (1:4.5.1-1) ... 65s Setting up libapt-pkg7.0:ppc64el (3.1.12) ... 65s Setting up apt (3.1.12) ... 66s Processing triggers for man-db (2.13.1-1) ... 69s Processing triggers for libc-bin (2.42-2ubuntu2) ... 69s autopkgtest [18:49:12]: upgrading testbed (apt dist-upgrade and autopurge) 70s Reading package lists... 70s Building dependency tree... 70s Reading state information... 70s Calculating upgrade... 70s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 71s Reading package lists... 71s Building dependency tree... 71s Reading state information... 71s Solving dependencies... 71s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 71s autopkgtest [18:49:14]: rebooting testbed after setup commands that affected boot 100s autopkgtest [18:49:43]: testbed running kernel: Linux 6.17.0-5-generic #5-Ubuntu SMP PREEMPT_DYNAMIC Mon Sep 22 10:02:41 UTC 2025 103s autopkgtest [18:49:46]: @@@@@@@@@@@@@@@@@@@@ apt-source node-telegram-bot-api 106s Get:1 http://ftpmaster.internal/ubuntu resolute/universe node-telegram-bot-api 2.0.1-3 (dsc) [2308 B] 106s Get:2 http://ftpmaster.internal/ubuntu resolute/universe node-telegram-bot-api 2.0.1-3 (tar) [2810 kB] 106s Get:3 http://ftpmaster.internal/ubuntu resolute/universe node-telegram-bot-api 2.0.1-3 (diff) [3968 B] 107s gpgv: Signature made Fri Nov 4 13:56:49 2022 UTC 107s gpgv: using RSA key 00DFE58B8B555779D1005EC9F6D74CA7C999EEE9 107s gpgv: Can't check signature: No public key 107s dpkg-source: warning: cannot verify inline signature for ./node-telegram-bot-api_2.0.1-3.dsc: no acceptable signature found 107s autopkgtest [18:49:50]: testing package node-telegram-bot-api version 2.0.1-3 107s autopkgtest [18:49:50]: build not needed 108s autopkgtest [18:49:51]: test command1: preparing testbed 108s Reading package lists... 108s Building dependency tree... 108s Reading state information... 108s Solving dependencies... 108s Some packages could not be installed. This may mean that you have 108s requested an impossible situation or if you are using the unstable 108s distribution that some required packages have not yet been created 108s or been moved out of Incoming. 108s The following information may help to resolve the situation: 108s 108s The following packages have unmet dependencies: 108s satisfy:command-line : Depends: node-telegram-bot-api but it is not going to be installed 108s Depends: nodejs but it is not going to be installed 108s E: Unable to satisfy dependencies. Reached two conflicting decisions: 108s 1. node-body-parser:ppc64el is selected for install because: 108s 1. satisfy:command-line:ppc64el=1 is selected for install 108s 2. satisfy:command-line:ppc64el Depends node-telegram-bot-api 108s 3. node-telegram-bot-api:ppc64el Depends node-body-parser 108s 2. node-body-parser:ppc64el is available in versions 2.2.0+~1.19.6-3, 1.20.3+~1.19.5-3 108s but none of the choices are installable: 108s - node-body-parser:ppc64el=2.2.0+~1.19.6-3 is not selected for install because: 108s 1. satisfy:command-line:ppc64el=1 is selected for install as above 108s 1-2. node-telegram-bot-api:ppc64el is selected for install as above 108s 3. node-telegram-bot-api:ppc64el Depends node-express 108s 4. node-express:ppc64el is available in version 4.21.2+~cs8.36.27-3 108s 5. node-body-parser:ppc64el=2.2.0+~1.19.6-3 Breaks node-express (< 5) 108s - node-body-parser:ppc64el=1.20.3+~1.19.5-3 is not selected for install 108s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 109s Reading package lists... 109s Building dependency tree... 109s Reading state information... 109s Solving dependencies... 109s Some packages could not be installed. This may mean that you have 109s requested an impossible situation or if you are using the unstable 109s distribution that some required packages have not yet been created 109s or been moved out of Incoming. 109s The following information may help to resolve the situation: 109s 109s The following packages have unmet dependencies: 109s satisfy:command-line : Depends: node-telegram-bot-api but it is not going to be installed 109s Depends: nodejs but it is not going to be installed 109s E: Unable to satisfy dependencies. Reached two conflicting decisions: 109s 1. node-body-parser:ppc64el is selected for install because: 109s 1. satisfy:command-line:ppc64el=1 is selected for install 109s 2. satisfy:command-line:ppc64el Depends node-telegram-bot-api 109s 3. node-telegram-bot-api:ppc64el Depends node-body-parser 109s 2. node-body-parser:ppc64el is available in versions 2.2.0+~1.19.6-3, 1.20.3+~1.19.5-3 109s but none of the choices are installable: 109s - node-body-parser:ppc64el=2.2.0+~1.19.6-3 is not selected for install because: 109s 1. satisfy:command-line:ppc64el=1 is selected for install as above 109s 1-2. node-telegram-bot-api:ppc64el is selected for install as above 109s 3. node-telegram-bot-api:ppc64el Depends node-express 109s 4. node-express:ppc64el is available in version 4.21.2+~cs8.36.27-3 109s 5. node-body-parser:ppc64el=2.2.0+~1.19.6-3 Breaks node-express (< 5) 109s - node-body-parser:ppc64el=1.20.3+~1.19.5-3 is not selected for install 109s command1 FAIL badpkg 109s blame: node-telegram-bot-api 109s 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. 109s autopkgtest [18:49:52]: test pkg-js-autopkgtest-require: preparing testbed 109s Reading package lists... 109s Building dependency tree... 109s Reading state information... 109s Solving dependencies... 109s Some packages could not be installed. This may mean that you have 109s requested an impossible situation or if you are using the unstable 109s distribution that some required packages have not yet been created 109s or been moved out of Incoming. 109s The following information may help to resolve the situation: 109s 109s The following packages have unmet dependencies: 110s satisfy:command-line : Depends: node-telegram-bot-api but it is not going to be installed 110s Depends: nodejs but it is not going to be installed 110s Depends: pkg-js-autopkgtest but it is not going to be installed 110s E: Unable to satisfy dependencies. Reached two conflicting decisions: 110s 1. node-body-parser:ppc64el is selected for install because: 110s 1. satisfy:command-line:ppc64el=1 is selected for install 110s 2. satisfy:command-line:ppc64el Depends node-telegram-bot-api 110s 3. node-telegram-bot-api:ppc64el Depends node-body-parser 110s 2. node-body-parser:ppc64el is available in versions 2.2.0+~1.19.6-3, 1.20.3+~1.19.5-3 110s but none of the choices are installable: 110s - node-body-parser:ppc64el=2.2.0+~1.19.6-3 is not selected for install because: 110s 1. satisfy:command-line:ppc64el=1 is selected for install as above 110s 1-2. node-telegram-bot-api:ppc64el is selected for install as above 110s 3. node-telegram-bot-api:ppc64el Depends node-express 110s 4. node-express:ppc64el is available in version 4.21.2+~cs8.36.27-3 110s 5. node-body-parser:ppc64el=2.2.0+~1.19.6-3 Breaks node-express (< 5) 110s - node-body-parser:ppc64el=1.20.3+~1.19.5-3 is not selected for install 110s pkg-js-autopkgtest-require FAIL badpkg 110s blame: node-telegram-bot-api 110s 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. 110s autopkgtest [18:49:53]: test pkg-js-autopkgtest: preparing testbed 130s Creating nova instance adt-resolute-ppc64el-node-telegram-bot-api-20251117-184803-juju-7f2275-prod-proposed-migration-environment-15-1fc4b42b-4485-4e35-bfa4-5b8a4257aae5 from image adt/ubuntu-resolute-ppc64el-server-20251117.img (UUID c6f5b741-c77a-45db-84cb-f00b40e77676)... 185s autopkgtest [18:51:08]: testbed dpkg architecture: ppc64el 185s autopkgtest [18:51:08]: testbed apt version: 3.1.11 186s autopkgtest [18:51:09]: @@@@@@@@@@@@@@@@@@@@ test bed setup 186s autopkgtest [18:51:09]: testbed release detected to be: resolute 187s autopkgtest [18:51:10]: updating testbed package index (apt update) 187s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [87.8 kB] 187s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 187s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 187s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 187s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [779 kB] 188s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [9852 B] 188s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [73.2 kB] 188s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [22.9 kB] 188s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el Packages [135 kB] 188s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/restricted ppc64el Packages [940 B] 188s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/universe ppc64el Packages [501 kB] 188s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse ppc64el Packages [11.0 kB] 188s Fetched 1622 kB in 1s (1354 kB/s) 189s Reading package lists... 190s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 190s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 190s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 190s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 191s Reading package lists... 191s Reading package lists... 191s Building dependency tree... 191s Reading state information... 191s Calculating upgrade... 191s The following packages will be upgraded: 191s apt libapt-pkg7.0 libcrypt-dev libcrypt1 usbutils 191s 5 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 191s Need to get 3180 kB of archives. 191s After this operation, 118 kB of additional disk space will be used. 191s Get:1 http://ftpmaster.internal/ubuntu resolute/main ppc64el libcrypt-dev ppc64el 1:4.5.1-1 [162 kB] 192s Get:2 http://ftpmaster.internal/ubuntu resolute/main ppc64el libcrypt1 ppc64el 1:4.5.1-1 [125 kB] 192s Get:3 http://ftpmaster.internal/ubuntu resolute/main ppc64el libapt-pkg7.0 ppc64el 3.1.12 [1286 kB] 192s Get:4 http://ftpmaster.internal/ubuntu resolute/main ppc64el apt ppc64el 3.1.12 [1516 kB] 193s Get:5 http://ftpmaster.internal/ubuntu resolute/main ppc64el usbutils ppc64el 1:019-1 [91.5 kB] 193s dpkg-preconfigure: unable to re-open stdin: No such file or directory 193s Fetched 3180 kB in 1s (2156 kB/s) 193s (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 ... 81022 files and directories currently installed.) 193s Preparing to unpack .../libcrypt-dev_1%3a4.5.1-1_ppc64el.deb ... 193s Unpacking libcrypt-dev:ppc64el (1:4.5.1-1) over (1:4.4.38-1build1) ... 193s Preparing to unpack .../libcrypt1_1%3a4.5.1-1_ppc64el.deb ... 193s Unpacking libcrypt1:ppc64el (1:4.5.1-1) over (1:4.4.38-1build1) ... 194s Setting up libcrypt1:ppc64el (1:4.5.1-1) ... 194s (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 ... 81022 files and directories currently installed.) 194s Preparing to unpack .../libapt-pkg7.0_3.1.12_ppc64el.deb ... 194s Unpacking libapt-pkg7.0:ppc64el (3.1.12) over (3.1.11) ... 194s Preparing to unpack .../apt_3.1.12_ppc64el.deb ... 194s Unpacking apt (3.1.12) over (3.1.11) ... 194s Preparing to unpack .../usbutils_1%3a019-1_ppc64el.deb ... 194s Unpacking usbutils (1:019-1) over (1:018-2) ... 194s Setting up usbutils (1:019-1) ... 194s Setting up libcrypt-dev:ppc64el (1:4.5.1-1) ... 194s Setting up libapt-pkg7.0:ppc64el (3.1.12) ... 194s Setting up apt (3.1.12) ... 195s Processing triggers for man-db (2.13.1-1) ... 197s Processing triggers for libc-bin (2.42-2ubuntu2) ... 197s autopkgtest [18:51:20]: upgrading testbed (apt dist-upgrade and autopurge) 198s Reading package lists... 198s Building dependency tree... 198s Reading state information... 198s Calculating upgrade... 199s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 199s Reading package lists... 199s Building dependency tree... 199s Reading state information... 199s Solving dependencies... 199s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 199s autopkgtest [18:51:22]: rebooting testbed after setup commands that affected boot 229s Reading package lists... 229s Building dependency tree... 229s Reading state information... 229s Solving dependencies... 229s Some packages could not be installed. This may mean that you have 229s requested an impossible situation or if you are using the unstable 229s distribution that some required packages have not yet been created 229s or been moved out of Incoming. 229s The following information may help to resolve the situation: 229s 229s The following packages have unmet dependencies: 229s satisfy:command-line : Depends: node-telegram-bot-api but it is not going to be installed 229s Depends: debhelper-compat (= 13) 229s Depends: dh-sequence-nodejs 229s Depends: node-axios but it is not going to be installed 229s Depends: node-bluebird but it is not going to be installed 229s Depends: node-body-parser but it is not going to be installed 229s Depends: node-express but it is not going to be installed 229s Depends: node-extend but it is not going to be installed 229s Depends: build-essential but it is not going to be installed 229s Depends: pkg-js-autopkgtest but it is not going to be installed 229s E: Unable to satisfy dependencies. Reached two conflicting decisions: 229s 1. node-body-parser:ppc64el is selected for install because: 229s 1. satisfy:command-line:ppc64el=1 is selected for install 229s 2. satisfy:command-line:ppc64el Depends node-body-parser 229s 2. node-body-parser:ppc64el is available in versions 2.2.0+~1.19.6-3, 1.20.3+~1.19.5-3 229s but none of the choices are installable: 229s - node-body-parser:ppc64el=2.2.0+~1.19.6-3 is not selected for install because: 229s 1. satisfy:command-line:ppc64el=1 is selected for install as above 229s 2. satisfy:command-line:ppc64el Depends node-express 229s 3. node-express:ppc64el is available in version 4.21.2+~cs8.36.27-3 229s 4. node-body-parser:ppc64el=2.2.0+~1.19.6-3 Breaks node-express (< 5) 229s - node-body-parser:ppc64el=1.20.3+~1.19.5-3 is not selected for install 229s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 230s Reading package lists... 230s Building dependency tree... 230s Reading state information... 230s Solving dependencies... 230s Some packages could not be installed. This may mean that you have 230s requested an impossible situation or if you are using the unstable 230s distribution that some required packages have not yet been created 230s or been moved out of Incoming. 230s The following information may help to resolve the situation: 230s 230s The following packages have unmet dependencies: 230s satisfy:command-line : Depends: node-telegram-bot-api but it is not going to be installed 230s Depends: debhelper-compat (= 13) 230s Depends: dh-sequence-nodejs 230s Depends: node-axios but it is not going to be installed 230s Depends: node-bluebird but it is not going to be installed 230s Depends: node-body-parser but it is not going to be installed 230s Depends: node-express but it is not going to be installed 230s Depends: node-extend but it is not going to be installed 230s Depends: build-essential but it is not going to be installed 230s Depends: pkg-js-autopkgtest but it is not going to be installed 230s E: Unable to satisfy dependencies. Reached two conflicting decisions: 230s 1. node-body-parser:ppc64el is selected for install because: 230s 1. satisfy:command-line:ppc64el=1 is selected for install 230s 2. satisfy:command-line:ppc64el Depends node-body-parser 230s 2. node-body-parser:ppc64el is available in versions 2.2.0+~1.19.6-3, 1.20.3+~1.19.5-3 230s but none of the choices are installable: 230s - node-body-parser:ppc64el=2.2.0+~1.19.6-3 is not selected for install because: 230s 1. satisfy:command-line:ppc64el=1 is selected for install as above 230s 2. satisfy:command-line:ppc64el Depends node-express 230s 3. node-express:ppc64el is available in version 4.21.2+~cs8.36.27-3 230s 4. node-body-parser:ppc64el=2.2.0+~1.19.6-3 Breaks node-express (< 5) 230s - node-body-parser:ppc64el=1.20.3+~1.19.5-3 is not selected for install 230s pkg-js-autopkgtest FAIL badpkg 230s blame: node-telegram-bot-api 230s 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. 230s autopkgtest [18:51:53]: @@@@@@@@@@@@@@@@@@@@ summary 230s command1 FAIL badpkg 230s blame: node-telegram-bot-api 230s 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. 230s pkg-js-autopkgtest-require FAIL badpkg 230s blame: node-telegram-bot-api 230s 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. 230s pkg-js-autopkgtest FAIL badpkg 230s blame: node-telegram-bot-api 230s 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.