0s autopkgtest [17:58:59]: starting date and time: 2026-01-22 17:58:59+0000 0s autopkgtest [17:58:59]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [17:58:59]: host juju-7f2275-prod-proposed-migration-environment-20; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.n7j1a_ti/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:python3-defaults --apt-upgrade vtk9 --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 --env=ADT_TEST_TRIGGERS=python3-defaults/3.14.2-1 -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest-cpu2-ram4-disk20-ppc64el --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-20@sto01-ppc64el-14.secgroup --name adt-resolute-ppc64el-vtk9-20260122-175859-juju-7f2275-prod-proposed-migration-environment-20-034b352c-61f3-4cc8-bd8d-f99cb3485a55 --image adt/ubuntu-resolute-ppc64el-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-20 --net-id=net_prod-autopkgtest-workers-ppc64el -e TERM=linux --mirror=http://ftpmaster.internal/ubuntu/ 4s Creating nova instance adt-resolute-ppc64el-vtk9-20260122-175859-juju-7f2275-prod-proposed-migration-environment-20-034b352c-61f3-4cc8-bd8d-f99cb3485a55 from image adt/ubuntu-resolute-ppc64el-server-20260122.img (UUID 987e5803-394f-43eb-a969-151b6b75a57a)... 53s autopkgtest [17:59:52]: testbed dpkg architecture: ppc64el 54s autopkgtest [17:59:53]: testbed apt version: 3.1.12 54s autopkgtest [17:59:53]: @@@@@@@@@@@@@@@@@@@@ test bed setup 54s autopkgtest [17:59:53]: testbed release detected to be: None 55s autopkgtest [17:59:54]: updating testbed package index (apt update) 55s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [124 kB] 55s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 55s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 55s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 55s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [2820 B] 55s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [80.9 kB] 55s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [19.2 kB] 55s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [815 kB] 55s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el Packages [103 kB] 55s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/universe ppc64el Packages [618 kB] 56s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse ppc64el Packages [4644 B] 56s Fetched 1768 kB in 1s (3424 kB/s) 56s Reading package lists... 57s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 57s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 57s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 57s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 58s Reading package lists... 58s Reading package lists... 58s Building dependency tree... 58s Reading state information... 58s Calculating upgrade... 58s The following packages were automatically installed and are no longer required: 58s python3.13 python3.13-minimal 58s Use 'sudo apt autoremove' to remove them. 58s The following NEW packages will be installed: 58s libpython3.14-minimal libpython3.14-stdlib python3.14 python3.14-minimal 58s The following packages will be upgraded: 58s libpython3-stdlib python3 python3-gdbm python3-minimal 58s 4 upgraded, 4 newly installed, 0 to remove and 0 not upgraded. 58s Need to get 6966 kB of archives. 58s After this operation, 27.7 MB of additional disk space will be used. 58s Get:1 http://ftpmaster.internal/ubuntu resolute/main ppc64el libpython3.14-minimal ppc64el 3.14.2-1 [921 kB] 59s Get:2 http://ftpmaster.internal/ubuntu resolute/main ppc64el python3.14-minimal ppc64el 3.14.2-1 [2712 kB] 59s Get:3 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el python3-gdbm ppc64el 3.14.2-1 [11.1 kB] 59s Get:4 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el python3-minimal ppc64el 3.14.2-1 [28.2 kB] 59s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el python3 ppc64el 3.14.2-1 [22.9 kB] 59s Get:6 http://ftpmaster.internal/ubuntu resolute/main ppc64el libpython3.14-stdlib ppc64el 3.14.2-1 [2444 kB] 59s Get:7 http://ftpmaster.internal/ubuntu resolute/main ppc64el python3.14 ppc64el 3.14.2-1 [816 kB] 59s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el libpython3-stdlib ppc64el 3.14.2-1 [10.9 kB] 59s dpkg-preconfigure: unable to re-open stdin: No such file or directory 59s Fetched 6966 kB in 0s (22.7 MB/s) 59s Selecting previously unselected package libpython3.14-minimal:ppc64el. 59s (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 ... 120824 files and directories currently installed.) 59s Preparing to unpack .../libpython3.14-minimal_3.14.2-1_ppc64el.deb ... 59s Unpacking libpython3.14-minimal:ppc64el (3.14.2-1) ... 60s Selecting previously unselected package python3.14-minimal. 60s Preparing to unpack .../python3.14-minimal_3.14.2-1_ppc64el.deb ... 60s Unpacking python3.14-minimal (3.14.2-1) ... 60s Preparing to unpack .../python3-gdbm_3.14.2-1_ppc64el.deb ... 60s Unpacking python3-gdbm (3.14.2-1) over (3.13.9-1) ... 60s Setting up libpython3.14-minimal:ppc64el (3.14.2-1) ... 60s Setting up python3.14-minimal (3.14.2-1) ... 61s (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 ... 121166 files and directories currently installed.) 61s Preparing to unpack .../python3-minimal_3.14.2-1_ppc64el.deb ... 61s Unpacking python3-minimal (3.14.2-1) over (3.13.7-1) ... 61s Setting up python3-minimal (3.14.2-1) ... 62s (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 ... 121166 files and directories currently installed.) 62s Preparing to unpack .../python3_3.14.2-1_ppc64el.deb ... 62s running python pre-rtupdate hooks for python3.14... 62s Unpacking python3 (3.14.2-1) over (3.13.7-1) ... 62s Selecting previously unselected package libpython3.14-stdlib:ppc64el. 62s Preparing to unpack .../libpython3.14-stdlib_3.14.2-1_ppc64el.deb ... 62s Unpacking libpython3.14-stdlib:ppc64el (3.14.2-1) ... 63s Selecting previously unselected package python3.14. 63s Preparing to unpack .../python3.14_3.14.2-1_ppc64el.deb ... 63s Unpacking python3.14 (3.14.2-1) ... 63s Preparing to unpack .../libpython3-stdlib_3.14.2-1_ppc64el.deb ... 63s Unpacking libpython3-stdlib:ppc64el (3.14.2-1) over (3.13.7-1) ... 63s Setting up libpython3.14-stdlib:ppc64el (3.14.2-1) ... 63s Setting up python3.14 (3.14.2-1) ... 64s Setting up libpython3-stdlib:ppc64el (3.14.2-1) ... 64s Setting up python3-gdbm (3.14.2-1) ... 64s Setting up python3 (3.14.2-1) ... 64s running python rtupdate hooks for python3.14... 64s running python post-rtupdate hooks for python3.14... 64s Processing triggers for man-db (2.13.1-1) ... 65s Processing triggers for systemd (259-1ubuntu2) ... 65s autopkgtest [18:00:04]: upgrading testbed (apt dist-upgrade and autopurge) 65s Reading package lists... 65s Building dependency tree... 65s Reading state information... 65s Calculating upgrade... 66s The following packages were automatically installed and are no longer required: 66s python3.13 python3.13-minimal 66s Use 'sudo apt autoremove' to remove them. 66s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 66s Reading package lists... 66s Building dependency tree... 66s Reading state information... 66s Solving dependencies... 66s The following packages will be REMOVED: 66s python3.13* python3.13-minimal* 66s 0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded. 66s After this operation, 9077 kB disk space will be freed. 66s (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 ... 121596 files and directories currently installed.) 66s Removing python3.13 (3.13.11-1) ... 66s Removing python3.13-minimal (3.13.11-1) ... 69s Processing triggers for man-db (2.13.1-1) ... 69s Processing triggers for systemd (259-1ubuntu2) ... 69s (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 ... 121569 files and directories currently installed.) 69s Purging configuration files for python3.13-minimal (3.13.11-1) ... 71s autopkgtest [18:00:10]: testbed running kernel: Linux 6.18.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 12 16:45:54 UTC 2026 71s autopkgtest [18:00:10]: @@@@@@@@@@@@@@@@@@@@ apt-source vtk9 77s Get:1 http://ftpmaster.internal/ubuntu resolute/universe vtk9 9.5.2+dfsg2-4ubuntu1 (dsc) [3764 B] 77s Get:2 http://ftpmaster.internal/ubuntu resolute/universe vtk9 9.5.2+dfsg2-4ubuntu1 (tar) [25.0 MB] 77s Get:3 http://ftpmaster.internal/ubuntu resolute/universe vtk9 9.5.2+dfsg2-4ubuntu1 (diff) [22.4 kB] 78s gpgv: Signature made Sun Dec 14 11:14:16 2025 UTC 78s gpgv: using RSA key B8340990283D8D9BC1949AC74799A35146D12B35 78s gpgv: issuer "sudipm.mukherjee@gmail.com" 78s gpgv: Can't check signature: No public key 78s dpkg-source: warning: cannot verify inline signature for ./vtk9_9.5.2+dfsg2-4ubuntu1.dsc: no acceptable signature found 81s autopkgtest [18:00:20]: testing package vtk9 version 9.5.2+dfsg2-4ubuntu1 82s autopkgtest [18:00:21]: build not needed 89s autopkgtest [18:00:28]: test buildBoolean: preparing testbed 89s Reading package lists... 89s Building dependency tree... 89s Reading state information... 89s Solving dependencies... 89s Some packages could not be installed. This may mean that you have 89s requested an impossible situation or if you are using the unstable 89s distribution that some required packages have not yet been created 89s or been moved out of Incoming. 89s The following information may help to resolve the situation: 89s 89s The following packages have unmet dependencies: 89s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 89s Depends: libvtk9-qt-dev but it is not going to be installed 89s Depends: build-essential but it is not going to be installed 89s Depends: cmake but it is not going to be installed 89s E: Unable to satisfy dependencies. Reached two conflicting decisions: 89s 1. python3:ppc64el=3.13.9-3 is not selected for install 89s 2. python3:ppc64el=3.13.9-3 is selected as a downgrade because: 89s 1. satisfy:command-line:ppc64el=1 is selected for install 89s 2. satisfy:command-line:ppc64el Depends libvtk9-dev 89s 3. libvtk9-dev:ppc64el Depends python3-vtk9 (= 9.5.2+dfsg2-4ubuntu1) 89s 4. python3-vtk9:ppc64el Depends python3 (< 3.14) 89s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 89s Reading package lists... 90s Building dependency tree... 90s Reading state information... 90s Solving dependencies... 90s Some packages could not be installed. This may mean that you have 90s requested an impossible situation or if you are using the unstable 90s distribution that some required packages have not yet been created 90s or been moved out of Incoming. 90s The following information may help to resolve the situation: 90s 90s The following packages have unmet dependencies: 90s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 90s Depends: libvtk9-qt-dev but it is not going to be installed 90s Depends: build-essential but it is not going to be installed 90s Depends: cmake but it is not going to be installed 90s E: Unable to satisfy dependencies. Reached two conflicting decisions: 90s 1. python3:ppc64el=3.13.9-3 is not selected for install 90s 2. python3:ppc64el=3.13.9-3 is selected as a downgrade because: 90s 1. satisfy:command-line:ppc64el=1 is selected for install 90s 2. satisfy:command-line:ppc64el Depends libvtk9-dev 90s 3. libvtk9-dev:ppc64el Depends python3-vtk9 (= 9.5.2+dfsg2-4ubuntu1) 90s 4. python3-vtk9:ppc64el Depends python3 (< 3.14) 90s buildBoolean FAIL badpkg 90s blame: vtk9 90s 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. 90s autopkgtest [18:00:29]: test buildPoint: preparing testbed 90s Reading package lists... 90s Building dependency tree... 90s Reading state information... 90s Solving dependencies... 90s Some packages could not be installed. This may mean that you have 90s requested an impossible situation or if you are using the unstable 90s distribution that some required packages have not yet been created 90s or been moved out of Incoming. 90s The following information may help to resolve the situation: 90s 90s The following packages have unmet dependencies: 90s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 90s Depends: libvtk9-qt-dev but it is not going to be installed 90s Depends: build-essential but it is not going to be installed 90s Depends: cmake but it is not going to be installed 90s E: Unable to satisfy dependencies. Reached two conflicting decisions: 90s 1. python3:ppc64el=3.13.9-3 is not selected for install 90s 2. python3:ppc64el=3.13.9-3 is selected as a downgrade because: 90s 1. satisfy:command-line:ppc64el=1 is selected for install 90s 2. satisfy:command-line:ppc64el Depends libvtk9-dev 90s 3. libvtk9-dev:ppc64el Depends python3-vtk9 (= 9.5.2+dfsg2-4ubuntu1) 90s 4. python3-vtk9:ppc64el Depends python3 (< 3.14) 90s buildPoint FAIL badpkg 90s blame: vtk9 90s 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. 90s autopkgtest [18:00:29]: test buildVTU: preparing testbed 90s Reading package lists... 91s Building dependency tree... 91s Reading state information... 91s Solving dependencies... 91s Some packages could not be installed. This may mean that you have 91s requested an impossible situation or if you are using the unstable 91s distribution that some required packages have not yet been created 91s or been moved out of Incoming. 91s The following information may help to resolve the situation: 91s 91s The following packages have unmet dependencies: 91s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 91s Depends: libvtk9-qt-dev but it is not going to be installed 91s Depends: build-essential but it is not going to be installed 91s Depends: cmake but it is not going to be installed 91s E: Unable to satisfy dependencies. Reached two conflicting decisions: 91s 1. python3:ppc64el=3.13.9-3 is not selected for install 91s 2. python3:ppc64el=3.13.9-3 is selected as a downgrade because: 91s 1. satisfy:command-line:ppc64el=1 is selected for install 91s 2. satisfy:command-line:ppc64el Depends libvtk9-dev 91s 3. libvtk9-dev:ppc64el Depends python3-vtk9 (= 9.5.2+dfsg2-4ubuntu1) 91s 4. python3-vtk9:ppc64el Depends python3 (< 3.14) 91s autopkgtest [18:00:30]: test buildDistance: preparing testbed 91s buildVTU FAIL badpkg 91s blame: vtk9 91s 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. 91s Reading package lists... 91s Building dependency tree... 91s Reading state information... 91s Solving dependencies... 91s Some packages could not be installed. This may mean that you have 91s requested an impossible situation or if you are using the unstable 91s distribution that some required packages have not yet been created 91s or been moved out of Incoming. 91s The following information may help to resolve the situation: 91s 91s The following packages have unmet dependencies: 91s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 91s Depends: libvtk9-qt-dev but it is not going to be installed 91s Depends: build-essential but it is not going to be installed 91s Depends: cmake but it is not going to be installed 91s E: Unable to satisfy dependencies. Reached two conflicting decisions: 91s 1. python3:ppc64el=3.13.9-3 is not selected for install 91s 2. python3:ppc64el=3.13.9-3 is selected as a downgrade because: 91s 1. satisfy:command-line:ppc64el=1 is selected for install 91s 2. satisfy:command-line:ppc64el Depends libvtk9-dev 91s 3. libvtk9-dev:ppc64el Depends python3-vtk9 (= 9.5.2+dfsg2-4ubuntu1) 91s 4. python3-vtk9:ppc64el Depends python3 (< 3.14) 91s autopkgtest [18:00:30]: test buildPNG: preparing testbed 91s buildDistance FAIL badpkg 91s blame: vtk9 91s 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. 91s Reading package lists... 92s Building dependency tree... 92s Reading state information... 92s Solving dependencies... 92s Some packages could not be installed. This may mean that you have 92s requested an impossible situation or if you are using the unstable 92s distribution that some required packages have not yet been created 92s or been moved out of Incoming. 92s The following information may help to resolve the situation: 92s 92s The following packages have unmet dependencies: 92s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 92s Depends: libvtk9-qt-dev but it is not going to be installed 92s Depends: build-essential but it is not going to be installed 92s Depends: cmake but it is not going to be installed 92s E: Unable to satisfy dependencies. Reached two conflicting decisions: 92s 1. python3:ppc64el=3.13.9-3 is not selected for install 92s 2. python3:ppc64el=3.13.9-3 is selected as a downgrade because: 92s 1. satisfy:command-line:ppc64el=1 is selected for install 92s 2. satisfy:command-line:ppc64el Depends libvtk9-dev 92s 3. libvtk9-dev:ppc64el Depends python3-vtk9 (= 9.5.2+dfsg2-4ubuntu1) 92s 4. python3-vtk9:ppc64el Depends python3 (< 3.14) 92s buildPNG FAIL badpkg 92s blame: vtk9 92s 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. 92s autopkgtest [18:00:31]: test buildVTP: preparing testbed 92s Reading package lists... 92s Building dependency tree... 92s Reading state information... 92s Solving dependencies... 92s Some packages could not be installed. This may mean that you have 92s requested an impossible situation or if you are using the unstable 92s distribution that some required packages have not yet been created 92s or been moved out of Incoming. 92s The following information may help to resolve the situation: 92s 92s The following packages have unmet dependencies: 92s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 92s Depends: libvtk9-qt-dev but it is not going to be installed 92s Depends: build-essential but it is not going to be installed 92s Depends: cmake but it is not going to be installed 92s E: Unable to satisfy dependencies. Reached two conflicting decisions: 92s 1. python3:ppc64el=3.13.9-3 is not selected for install 92s 2. python3:ppc64el=3.13.9-3 is selected as a downgrade because: 92s 1. satisfy:command-line:ppc64el=1 is selected for install 92s 2. satisfy:command-line:ppc64el Depends libvtk9-dev 92s 3. libvtk9-dev:ppc64el Depends python3-vtk9 (= 9.5.2+dfsg2-4ubuntu1) 92s 4. python3-vtk9:ppc64el Depends python3 (< 3.14) 92s autopkgtest [18:00:31]: @@@@@@@@@@@@@@@@@@@@ summary 92s buildBoolean FAIL badpkg 92s blame: vtk9 92s 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. 92s buildPoint FAIL badpkg 92s blame: vtk9 92s 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. 92s buildVTU FAIL badpkg 92s blame: vtk9 92s 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. 92s buildDistance FAIL badpkg 92s blame: vtk9 92s 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. 92s buildPNG FAIL badpkg 92s blame: vtk9 92s 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. 92s buildVTP FAIL badpkg 92s blame: vtk9 92s 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. 92s buildVTP FAIL badpkg 92s blame: vtk9 92s 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.