0s autopkgtest [16:39:04]: starting date and time: 2025-11-17 16:39:04+0000 0s autopkgtest [16:39:04]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [16:39:04]: host juju-7f2275-prod-proposed-migration-environment-15; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.u2juj6kj/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-cpu2-ram4-disk20-amd64 --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-15@sto01-3.secgroup --name adt-resolute-amd64-node-telegram-bot-api-20251117-163904-juju-7f2275-prod-proposed-migration-environment-15-33ff2a6f-58a8-4dbc-9202-002b92636775 --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/ 4s Creating nova instance adt-resolute-amd64-node-telegram-bot-api-20251117-163904-juju-7f2275-prod-proposed-migration-environment-15-33ff2a6f-58a8-4dbc-9202-002b92636775 from image adt/ubuntu-resolute-amd64-server-20251117.img (UUID 9762b0cc-7c5b-4854-acd5-cc74ad0de8c6)... 46s autopkgtest [16:39:50]: testbed dpkg architecture: amd64 46s autopkgtest [16:39:50]: testbed apt version: 3.1.11 46s autopkgtest [16:39:50]: @@@@@@@@@@@@@@@@@@@@ test bed setup 46s autopkgtest [16:39:50]: testbed release detected to be: None 47s autopkgtest [16:39:51]: updating testbed package index (apt update) 47s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [87.8 kB] 47s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 47s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 47s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 47s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [9848 B] 47s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [81.5 kB] 47s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [839 kB] 48s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [22.9 kB] 48s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 Packages [159 kB] 48s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/main i386 Packages [118 kB] 48s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 c-n-f Metadata [3236 B] 48s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 Packages [64.6 kB] 48s Get:13 http://ftpmaster.internal/ubuntu resolute-proposed/restricted i386 Packages [3744 B] 48s Get:14 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 c-n-f Metadata [336 B] 48s Get:15 http://ftpmaster.internal/ubuntu resolute-proposed/universe i386 Packages [271 kB] 48s Get:16 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 Packages [585 kB] 48s Get:17 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 c-n-f Metadata [20.1 kB] 48s Get:18 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse i386 Packages [6516 B] 48s Get:19 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 Packages [13.4 kB] 48s Get:20 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 c-n-f Metadata [680 B] 50s Fetched 2286 kB in 1s (2285 kB/s) 50s Reading package lists... 51s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 51s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 51s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 51s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 51s Reading package lists... 51s Reading package lists... 51s Building dependency tree... 51s Reading state information... 51s Calculating upgrade... 51s The following packages will be upgraded: 51s usbutils 52s 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 52s Need to get 83.9 kB of archives. 52s After this operation, 0 B of additional disk space will be used. 52s Get:1 http://ftpmaster.internal/ubuntu resolute/main amd64 usbutils amd64 1:019-1 [83.9 kB] 52s dpkg-preconfigure: unable to re-open stdin: No such file or directory 52s Fetched 83.9 kB in 0s (0 B/s) 52s (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 ... 83372 files and directories currently installed.) 52s Preparing to unpack .../usbutils_1%3a019-1_amd64.deb ... 52s Unpacking usbutils (1:019-1) over (1:018-2) ... 52s Setting up usbutils (1:019-1) ... 52s Processing triggers for man-db (2.13.1-1) ... 53s autopkgtest [16:39:57]: upgrading testbed (apt dist-upgrade and autopurge) 53s Reading package lists... 53s Building dependency tree... 53s Reading state information... 53s Calculating upgrade... 53s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 53s Reading package lists... 53s Building dependency tree... 53s Reading state information... 53s Solving dependencies... 53s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 56s autopkgtest [16:40:00]: testbed running kernel: Linux 6.17.0-5-generic #5-Ubuntu SMP PREEMPT_DYNAMIC Mon Sep 22 10:00:33 UTC 2025 56s autopkgtest [16:40:00]: @@@@@@@@@@@@@@@@@@@@ apt-source node-telegram-bot-api 57s Get:1 http://ftpmaster.internal/ubuntu resolute/universe node-telegram-bot-api 2.0.1-3 (dsc) [2308 B] 57s Get:2 http://ftpmaster.internal/ubuntu resolute/universe node-telegram-bot-api 2.0.1-3 (tar) [2810 kB] 57s Get:3 http://ftpmaster.internal/ubuntu resolute/universe node-telegram-bot-api 2.0.1-3 (diff) [3968 B] 57s gpgv: Signature made Fri Nov 4 13:56:49 2022 UTC 57s gpgv: using RSA key 00DFE58B8B555779D1005EC9F6D74CA7C999EEE9 57s gpgv: Can't check signature: No public key 57s dpkg-source: warning: cannot verify inline signature for ./node-telegram-bot-api_2.0.1-3.dsc: no acceptable signature found 57s autopkgtest [16:40:01]: testing package node-telegram-bot-api version 2.0.1-3 58s autopkgtest [16:40:02]: build not needed 58s autopkgtest [16:40:02]: test command1: preparing testbed 58s Reading package lists... 58s Building dependency tree... 58s Reading state information... 58s Solving dependencies... 58s Some packages could not be installed. This may mean that you have 58s requested an impossible situation or if you are using the unstable 58s distribution that some required packages have not yet been created 58s or been moved out of Incoming. 58s The following information may help to resolve the situation: 58s 58s The following packages have unmet dependencies: 59s satisfy:command-line : Depends: node-telegram-bot-api but it is not going to be installed 59s Depends: nodejs but it is not going to be installed 59s E: Unable to satisfy dependencies. Reached two conflicting decisions: 59s 1. node-body-parser:amd64 is selected for install because: 59s 1. satisfy:command-line:amd64=1 is selected for install 59s 2. satisfy:command-line:amd64 Depends node-telegram-bot-api 59s 3. node-telegram-bot-api:amd64 Depends node-body-parser 59s 2. node-body-parser:amd64 is available in versions 2.2.0+~1.19.6-3, 1.20.3+~1.19.5-3 59s but none of the choices are installable: 59s - node-body-parser:amd64=2.2.0+~1.19.6-3 is not selected for install because: 59s 1. satisfy:command-line:amd64=1 is selected for install as above 59s 1-2. node-telegram-bot-api:amd64 is selected for install as above 59s 3. node-telegram-bot-api:amd64 Depends node-express 59s 4. node-express:amd64 is available in version 4.21.2+~cs8.36.27-3 59s 5. node-body-parser:amd64=2.2.0+~1.19.6-3 Breaks node-express (< 5) 59s - node-body-parser:amd64=1.20.3+~1.19.5-3 is not selected for install 59s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 59s Reading package lists... 59s Building dependency tree... 59s Reading state information... 59s Solving dependencies... 59s Some packages could not be installed. This may mean that you have 59s requested an impossible situation or if you are using the unstable 59s distribution that some required packages have not yet been created 59s or been moved out of Incoming. 59s The following information may help to resolve the situation: 59s 59s The following packages have unmet dependencies: 59s satisfy:command-line : Depends: node-telegram-bot-api but it is not going to be installed 59s Depends: nodejs but it is not going to be installed 59s E: Unable to satisfy dependencies. Reached two conflicting decisions: 59s 1. node-body-parser:amd64 is selected for install because: 59s 1. satisfy:command-line:amd64=1 is selected for install 59s 2. satisfy:command-line:amd64 Depends node-telegram-bot-api 59s 3. node-telegram-bot-api:amd64 Depends node-body-parser 59s 2. node-body-parser:amd64 is available in versions 2.2.0+~1.19.6-3, 1.20.3+~1.19.5-3 59s but none of the choices are installable: 59s - node-body-parser:amd64=2.2.0+~1.19.6-3 is not selected for install because: 59s 1. satisfy:command-line:amd64=1 is selected for install as above 59s 1-2. node-telegram-bot-api:amd64 is selected for install as above 59s 3. node-telegram-bot-api:amd64 Depends node-express 59s 4. node-express:amd64 is available in version 4.21.2+~cs8.36.27-3 59s 5. node-body-parser:amd64=2.2.0+~1.19.6-3 Breaks node-express (< 5) 59s - node-body-parser:amd64=1.20.3+~1.19.5-3 is not selected for install 59s command1 FAIL badpkg 59s blame: node-telegram-bot-api 59s 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. 59s autopkgtest [16:40:03]: test pkg-js-autopkgtest-require: preparing testbed 59s Reading package lists... 59s Building dependency tree... 59s Reading state information... 60s Solving dependencies... 60s Some packages could not be installed. This may mean that you have 60s requested an impossible situation or if you are using the unstable 60s distribution that some required packages have not yet been created 60s or been moved out of Incoming. 60s The following information may help to resolve the situation: 60s 60s The following packages have unmet dependencies: 60s satisfy:command-line : Depends: node-telegram-bot-api but it is not going to be installed 60s Depends: nodejs but it is not going to be installed 60s Depends: pkg-js-autopkgtest but it is not going to be installed 60s E: Unable to satisfy dependencies. Reached two conflicting decisions: 60s 1. node-body-parser:amd64 is selected for install because: 60s 1. satisfy:command-line:amd64=1 is selected for install 60s 2. satisfy:command-line:amd64 Depends node-telegram-bot-api 60s 3. node-telegram-bot-api:amd64 Depends node-body-parser 60s 2. node-body-parser:amd64 is available in versions 2.2.0+~1.19.6-3, 1.20.3+~1.19.5-3 60s but none of the choices are installable: 60s - node-body-parser:amd64=2.2.0+~1.19.6-3 is not selected for install because: 60s 1. satisfy:command-line:amd64=1 is selected for install as above 60s 1-2. node-telegram-bot-api:amd64 is selected for install as above 60s 3. node-telegram-bot-api:amd64 Depends node-express 60s 4. node-express:amd64 is available in version 4.21.2+~cs8.36.27-3 60s 5. node-body-parser:amd64=2.2.0+~1.19.6-3 Breaks node-express (< 5) 60s - node-body-parser:amd64=1.20.3+~1.19.5-3 is not selected for install 60s pkg-js-autopkgtest-require FAIL badpkg 60s blame: node-telegram-bot-api 60s 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. 60s autopkgtest [16:40:04]: test pkg-js-autopkgtest: preparing testbed 78s Creating nova instance adt-resolute-amd64-node-telegram-bot-api-20251117-163904-juju-7f2275-prod-proposed-migration-environment-15-33ff2a6f-58a8-4dbc-9202-002b92636775 from image adt/ubuntu-resolute-amd64-server-20251117.img (UUID 9762b0cc-7c5b-4854-acd5-cc74ad0de8c6)... 117s autopkgtest [16:41:01]: testbed dpkg architecture: amd64 117s autopkgtest [16:41:01]: testbed apt version: 3.1.11 118s autopkgtest [16:41:02]: @@@@@@@@@@@@@@@@@@@@ test bed setup 118s autopkgtest [16:41:02]: testbed release detected to be: resolute 118s autopkgtest [16:41:02]: updating testbed package index (apt update) 119s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [87.8 kB] 119s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 119s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 119s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 119s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [22.9 kB] 119s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [779 kB] 119s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [73.2 kB] 119s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [9852 B] 119s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 Packages [153 kB] 119s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/main i386 Packages [113 kB] 119s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 c-n-f Metadata [3236 B] 119s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/restricted i386 Packages [3744 B] 119s Get:13 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 Packages [64.6 kB] 119s Get:14 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 c-n-f Metadata [336 B] 119s Get:15 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 Packages [543 kB] 119s Get:16 http://ftpmaster.internal/ubuntu resolute-proposed/universe i386 Packages [254 kB] 119s Get:17 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 c-n-f Metadata [20.1 kB] 119s Get:18 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 Packages [13.4 kB] 119s Get:19 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse i386 Packages [6516 B] 119s Get:20 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 c-n-f Metadata [680 B] 121s Fetched 2149 kB in 1s (2315 kB/s) 121s Reading package lists... 122s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [87.8 kB] 122s Get:2 http://ftpmaster.internal/ubuntu resolute InRelease [87.8 kB] 122s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 122s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 122s Fetched 176 kB in 0s (559 kB/s) 123s Reading package lists... 123s Reading package lists... 123s Building dependency tree... 123s Reading state information... 123s Calculating upgrade... 123s The following packages will be upgraded: 123s apt libapt-pkg7.0 libcrypt-dev libcrypt1 libunwind8 usbutils 123s 6 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 123s Need to get 2978 kB of archives. 123s After this operation, 46.1 kB of additional disk space will be used. 123s Get:1 http://ftpmaster.internal/ubuntu resolute/main amd64 libcrypt-dev amd64 1:4.5.1-1 [122 kB] 123s Get:2 http://ftpmaster.internal/ubuntu resolute/main amd64 libcrypt1 amd64 1:4.5.1-1 [90.7 kB] 123s Get:3 http://ftpmaster.internal/ubuntu resolute/main amd64 libapt-pkg7.0 amd64 3.1.12 [1148 kB] 123s Get:4 http://ftpmaster.internal/ubuntu resolute/main amd64 apt amd64 3.1.12 [1474 kB] 123s Get:5 http://ftpmaster.internal/ubuntu resolute/main amd64 usbutils amd64 1:019-1 [83.9 kB] 123s Get:6 http://ftpmaster.internal/ubuntu resolute/main amd64 libunwind8 amd64 1.8.3-0ubuntu1 [59.6 kB] 124s dpkg-preconfigure: unable to re-open stdin: No such file or directory 124s Fetched 2978 kB in 1s (5737 kB/s) 124s (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 ... 83372 files and directories currently installed.) 124s Preparing to unpack .../libcrypt-dev_1%3a4.5.1-1_amd64.deb ... 124s Unpacking libcrypt-dev:amd64 (1:4.5.1-1) over (1:4.4.38-1build1) ... 124s Preparing to unpack .../libcrypt1_1%3a4.5.1-1_amd64.deb ... 124s Unpacking libcrypt1:amd64 (1:4.5.1-1) over (1:4.4.38-1build1) ... 124s Setting up libcrypt1:amd64 (1:4.5.1-1) ... 124s (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 ... 83372 files and directories currently installed.) 124s Preparing to unpack .../libapt-pkg7.0_3.1.12_amd64.deb ... 124s Unpacking libapt-pkg7.0:amd64 (3.1.12) over (3.1.11) ... 124s Preparing to unpack .../archives/apt_3.1.12_amd64.deb ... 124s Unpacking apt (3.1.12) over (3.1.11) ... 124s Preparing to unpack .../usbutils_1%3a019-1_amd64.deb ... 124s Unpacking usbutils (1:019-1) over (1:018-2) ... 124s Preparing to unpack .../libunwind8_1.8.3-0ubuntu1_amd64.deb ... 124s Unpacking libunwind8:amd64 (1.8.3-0ubuntu1) over (1.8.1-0.1ubuntu1) ... 124s Setting up libunwind8:amd64 (1.8.3-0ubuntu1) ... 124s Setting up usbutils (1:019-1) ... 124s Setting up libcrypt-dev:amd64 (1:4.5.1-1) ... 124s Setting up libapt-pkg7.0:amd64 (3.1.12) ... 124s Setting up apt (3.1.12) ... 125s Processing triggers for man-db (2.13.1-1) ... 126s Processing triggers for libc-bin (2.42-2ubuntu2) ... 126s autopkgtest [16:41:10]: upgrading testbed (apt dist-upgrade and autopurge) 126s Reading package lists... 127s Building dependency tree... 127s Reading state information... 127s Calculating upgrade... 127s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 127s Reading package lists... 127s Building dependency tree... 127s Reading state information... 127s Solving dependencies... 127s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 127s autopkgtest [16:41:11]: rebooting testbed after setup commands that affected boot 157s Reading package lists... 157s Building dependency tree... 157s Reading state information... 157s Solving dependencies... 157s Some packages could not be installed. This may mean that you have 157s requested an impossible situation or if you are using the unstable 157s distribution that some required packages have not yet been created 157s or been moved out of Incoming. 157s The following information may help to resolve the situation: 157s 157s The following packages have unmet dependencies: 157s satisfy:command-line : Depends: node-telegram-bot-api but it is not going to be installed 157s Depends: debhelper-compat (= 13) 157s Depends: dh-sequence-nodejs 157s Depends: node-axios but it is not going to be installed 157s Depends: node-bluebird but it is not going to be installed 157s Depends: node-body-parser but it is not going to be installed 157s Depends: node-express but it is not going to be installed 157s Depends: node-extend but it is not going to be installed 157s Depends: build-essential but it is not going to be installed 157s Depends: pkg-js-autopkgtest but it is not going to be installed 157s E: Unable to satisfy dependencies. Reached two conflicting decisions: 157s 1. node-body-parser:amd64 is selected for install because: 157s 1. satisfy:command-line:amd64=1 is selected for install 157s 2. satisfy:command-line:amd64 Depends node-body-parser 157s 2. node-body-parser:amd64 is available in versions 2.2.0+~1.19.6-3, 1.20.3+~1.19.5-3 157s but none of the choices are installable: 157s - node-body-parser:amd64=2.2.0+~1.19.6-3 is not selected for install because: 157s 1. satisfy:command-line:amd64=1 is selected for install as above 157s 2. satisfy:command-line:amd64 Depends node-express 157s 3. node-express:amd64 is available in version 4.21.2+~cs8.36.27-3 157s 4. node-body-parser:amd64=2.2.0+~1.19.6-3 Breaks node-express (< 5) 157s - node-body-parser:amd64=1.20.3+~1.19.5-3 is not selected for install 157s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 157s Reading package lists... 157s Building dependency tree... 157s Reading state information... 157s Solving dependencies... 157s Some packages could not be installed. This may mean that you have 157s requested an impossible situation or if you are using the unstable 157s distribution that some required packages have not yet been created 157s or been moved out of Incoming. 157s The following information may help to resolve the situation: 157s 157s The following packages have unmet dependencies: 157s satisfy:command-line : Depends: node-telegram-bot-api but it is not going to be installed 157s Depends: debhelper-compat (= 13) 157s Depends: dh-sequence-nodejs 157s Depends: node-axios but it is not going to be installed 157s Depends: node-bluebird but it is not going to be installed 157s Depends: node-body-parser but it is not going to be installed 157s Depends: node-express but it is not going to be installed 157s Depends: node-extend but it is not going to be installed 157s Depends: build-essential but it is not going to be installed 157s Depends: pkg-js-autopkgtest but it is not going to be installed 157s E: Unable to satisfy dependencies. Reached two conflicting decisions: 157s 1. node-body-parser:amd64 is selected for install because: 157s 1. satisfy:command-line:amd64=1 is selected for install 157s 2. satisfy:command-line:amd64 Depends node-body-parser 157s 2. node-body-parser:amd64 is available in versions 2.2.0+~1.19.6-3, 1.20.3+~1.19.5-3 157s but none of the choices are installable: 157s - node-body-parser:amd64=2.2.0+~1.19.6-3 is not selected for install because: 157s 1. satisfy:command-line:amd64=1 is selected for install as above 157s 2. satisfy:command-line:amd64 Depends node-express 157s 3. node-express:amd64 is available in version 4.21.2+~cs8.36.27-3 157s 4. node-body-parser:amd64=2.2.0+~1.19.6-3 Breaks node-express (< 5) 157s - node-body-parser:amd64=1.20.3+~1.19.5-3 is not selected for install 158s pkg-js-autopkgtest FAIL badpkg 158s blame: node-telegram-bot-api 158s 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. 158s autopkgtest [16:41:42]: @@@@@@@@@@@@@@@@@@@@ summary 158s command1 FAIL badpkg 158s blame: node-telegram-bot-api 158s 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. 158s pkg-js-autopkgtest-require FAIL badpkg 158s blame: node-telegram-bot-api 158s 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. 158s pkg-js-autopkgtest FAIL badpkg 158s blame: node-telegram-bot-api 158s 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.