0s autopkgtest [17:55:16]: starting date and time: 2026-01-24 17:55:16+0000 0s autopkgtest [17:55:16]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [17:55:16]: host juju-7f2275-prod-proposed-migration-environment-15; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.yshtw5wt/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-amd64 --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-15@sto01-8.secgroup --name adt-resolute-amd64-vtk9-20260124-175516-juju-7f2275-prod-proposed-migration-environment-15-47967d9e-b571-4560-9cbc-3b8db30d397f --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/ 3s Creating nova instance adt-resolute-amd64-vtk9-20260124-175516-juju-7f2275-prod-proposed-migration-environment-15-47967d9e-b571-4560-9cbc-3b8db30d397f from image adt/ubuntu-resolute-amd64-server-20260124.img (UUID 46811f22-3700-43f4-953b-ee3c613d71bb)... 75s autopkgtest [17:56:31]: testbed dpkg architecture: amd64 75s autopkgtest [17:56:31]: testbed apt version: 3.1.13 75s autopkgtest [17:56:31]: @@@@@@@@@@@@@@@@@@@@ test bed setup 76s autopkgtest [17:56:32]: testbed release detected to be: None 76s autopkgtest [17:56:32]: updating testbed package index (apt update) 76s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [124 kB] 76s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 76s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 76s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 76s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [985 kB] 77s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [93.1 kB] 77s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [24.3 kB] 77s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [2820 B] 77s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 Packages [113 kB] 77s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/main i386 Packages [96.9 kB] 77s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 c-n-f Metadata [3712 B] 77s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 Packages [12.3 kB] 77s Get:13 http://ftpmaster.internal/ubuntu resolute-proposed/restricted i386 Packages [3696 B] 77s Get:14 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 c-n-f Metadata [336 B] 77s Get:15 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 Packages [892 kB] 77s Get:16 http://ftpmaster.internal/ubuntu resolute-proposed/universe i386 Packages [375 kB] 77s Get:17 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 c-n-f Metadata [24.8 kB] 77s Get:18 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 Packages [12.4 kB] 77s Get:19 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse i386 Packages [4704 B] 77s Get:20 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 c-n-f Metadata [824 B] 78s Fetched 2768 kB in 1s (3497 kB/s) 78s Reading package lists... 79s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 79s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 79s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 79s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 79s Reading package lists... 79s Reading package lists... 79s Building dependency tree... 79s Reading state information... 80s Calculating upgrade... 80s The following packages were automatically installed and are no longer required: 80s python3.13 python3.13-minimal 80s Use 'sudo apt autoremove' to remove them. 80s The following NEW packages will be installed: 80s libpython3.14-minimal libpython3.14-stdlib python3.14 python3.14-minimal 80s The following packages will be upgraded: 80s libpython3-stdlib python3 python3-gdbm python3-minimal rust-coreutils 80s 5 upgraded, 4 newly installed, 0 to remove and 0 not upgraded. 80s Need to get 10.4 MB of archives. 80s After this operation, 25.2 MB of additional disk space will be used. 80s Get:1 http://ftpmaster.internal/ubuntu resolute/main amd64 libpython3.14-minimal amd64 3.14.2-1 [920 kB] 80s Get:2 http://ftpmaster.internal/ubuntu resolute/main amd64 python3.14-minimal amd64 3.14.2-1 [2563 kB] 80s Get:3 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 python3-minimal amd64 3.14.2-1 [28.2 kB] 80s Get:4 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 python3 amd64 3.14.2-1 [22.9 kB] 80s Get:5 http://ftpmaster.internal/ubuntu resolute/main amd64 libpython3.14-stdlib amd64 3.14.2-1 [2398 kB] 80s Get:6 http://ftpmaster.internal/ubuntu resolute/main amd64 python3.14 amd64 3.14.2-1 [816 kB] 80s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 libpython3-stdlib amd64 3.14.2-1 [10.9 kB] 80s Get:8 http://ftpmaster.internal/ubuntu resolute/main amd64 rust-coreutils amd64 0.5.0-0ubuntu1 [3628 kB] 80s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 python3-gdbm amd64 3.14.2-1 [11.1 kB] 80s dpkg-preconfigure: unable to re-open stdin: No such file or directory 80s Fetched 10.4 MB in 1s (19.9 MB/s) 80s Selecting previously unselected package libpython3.14-minimal:amd64. 81s (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 ... 124177 files and directories currently installed.) 81s Preparing to unpack .../libpython3.14-minimal_3.14.2-1_amd64.deb ... 81s Unpacking libpython3.14-minimal:amd64 (3.14.2-1) ... 81s Selecting previously unselected package python3.14-minimal. 81s Preparing to unpack .../python3.14-minimal_3.14.2-1_amd64.deb ... 81s Unpacking python3.14-minimal (3.14.2-1) ... 81s Setting up libpython3.14-minimal:amd64 (3.14.2-1) ... 81s Setting up python3.14-minimal (3.14.2-1) ... 81s (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 ... 124519 files and directories currently installed.) 81s Preparing to unpack .../python3-minimal_3.14.2-1_amd64.deb ... 81s Unpacking python3-minimal (3.14.2-1) over (3.13.9-3) ... 81s Setting up python3-minimal (3.14.2-1) ... 82s (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 ... 124519 files and directories currently installed.) 82s Preparing to unpack .../python3_3.14.2-1_amd64.deb ... 82s running python pre-rtupdate hooks for python3.14... 82s Unpacking python3 (3.14.2-1) over (3.13.9-3) ... 82s Selecting previously unselected package libpython3.14-stdlib:amd64. 82s Preparing to unpack .../libpython3.14-stdlib_3.14.2-1_amd64.deb ... 82s Unpacking libpython3.14-stdlib:amd64 (3.14.2-1) ... 82s Selecting previously unselected package python3.14. 82s Preparing to unpack .../python3.14_3.14.2-1_amd64.deb ... 82s Unpacking python3.14 (3.14.2-1) ... 82s Preparing to unpack .../libpython3-stdlib_3.14.2-1_amd64.deb ... 82s Unpacking libpython3-stdlib:amd64 (3.14.2-1) over (3.13.9-3) ... 82s Preparing to unpack .../rust-coreutils_0.5.0-0ubuntu1_amd64.deb ... 82s Unpacking rust-coreutils (0.5.0-0ubuntu1) over (0.2.2-0ubuntu2) ... 82s Setting up rust-coreutils (0.5.0-0ubuntu1) ... 82s (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 ... 124980 files and directories currently installed.) 82s Preparing to unpack .../python3-gdbm_3.14.2-1_amd64.deb ... 82s Unpacking python3-gdbm (3.14.2-1) over (3.13.9-3) ... 82s Setting up libpython3.14-stdlib:amd64 (3.14.2-1) ... 82s Setting up python3.14 (3.14.2-1) ... 83s Setting up libpython3-stdlib:amd64 (3.14.2-1) ... 83s Setting up python3-gdbm (3.14.2-1) ... 83s Setting up python3 (3.14.2-1) ... 83s running python rtupdate hooks for python3.14... 83s running python post-rtupdate hooks for python3.14... 83s Processing triggers for man-db (2.13.1-1) ... 83s Processing triggers for systemd (259-1ubuntu2) ... 83s autopkgtest [17:56:39]: upgrading testbed (apt dist-upgrade and autopurge) 83s Reading package lists... 84s Building dependency tree... 84s Reading state information... 84s Calculating upgrade... 84s The following packages were automatically installed and are no longer required: 84s python3.13 python3.13-minimal 84s Use 'sudo apt autoremove' to remove them. 84s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 84s Reading package lists... 84s Building dependency tree... 84s Reading state information... 84s Solving dependencies... 84s The following packages will be REMOVED: 84s python3.13* python3.13-minimal* 84s 0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded. 84s After this operation, 7860 kB disk space will be freed. 84s (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 ... 124978 files and directories currently installed.) 84s Removing python3.13 (3.13.11-1) ... 85s Removing python3.13-minimal (3.13.11-1) ... 85s Processing triggers for man-db (2.13.1-1) ... 85s Processing triggers for systemd (259-1ubuntu2) ... 85s (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 ... 124951 files and directories currently installed.) 85s Purging configuration files for python3.13-minimal (3.13.11-1) ... 87s autopkgtest [17:56:43]: testbed running kernel: Linux 6.18.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 12 16:49:02 UTC 2026 88s autopkgtest [17:56:44]: @@@@@@@@@@@@@@@@@@@@ apt-source vtk9 92s Get:1 http://ftpmaster.internal/ubuntu resolute/universe vtk9 9.5.2+dfsg2-4ubuntu1 (dsc) [3764 B] 92s Get:2 http://ftpmaster.internal/ubuntu resolute/universe vtk9 9.5.2+dfsg2-4ubuntu1 (tar) [25.0 MB] 92s Get:3 http://ftpmaster.internal/ubuntu resolute/universe vtk9 9.5.2+dfsg2-4ubuntu1 (diff) [22.4 kB] 92s gpgv: Signature made Sun Dec 14 11:14:16 2025 UTC 92s gpgv: using RSA key B8340990283D8D9BC1949AC74799A35146D12B35 92s gpgv: issuer "sudipm.mukherjee@gmail.com" 92s gpgv: Can't check signature: No public key 92s dpkg-source: warning: cannot verify inline signature for ./vtk9_9.5.2+dfsg2-4ubuntu1.dsc: no acceptable signature found 93s autopkgtest [17:56:49]: testing package vtk9 version 9.5.2+dfsg2-4ubuntu1 94s autopkgtest [17:56:50]: build not needed 100s autopkgtest [17:56:56]: test buildBoolean: preparing testbed 100s Reading package lists... 100s Building dependency tree... 100s Reading state information... 100s Solving dependencies... 100s Some packages could not be installed. This may mean that you have 100s requested an impossible situation or if you are using the unstable 100s distribution that some required packages have not yet been created 100s or been moved out of Incoming. 100s The following information may help to resolve the situation: 100s 100s The following packages have unmet dependencies: 101s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 101s Depends: libvtk9-qt-dev but it is not going to be installed 101s Depends: build-essential but it is not going to be installed 101s Depends: cmake 101s E: Unable to satisfy dependencies. Reached two conflicting assignments: 101s 1. python3:amd64=3.13.9-3 is not selected for install 101s 2. python3:amd64=3.13.9-3 is selected as a downgrade because: 101s 1. satisfy:command-line:amd64=1 is selected for install 101s 2. satisfy:command-line:amd64 Depends libvtk9-dev 101s 3. libvtk9-dev:amd64 Depends python3-vtk9 (= 9.5.2+dfsg2-4ubuntu1) 101s 4. python3-vtk9:amd64 Depends python3 (< 3.14) 101s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 101s Reading package lists... 101s Building dependency tree... 101s Reading state information... 101s Solving dependencies... 101s Some packages could not be installed. This may mean that you have 101s requested an impossible situation or if you are using the unstable 101s distribution that some required packages have not yet been created 101s or been moved out of Incoming. 101s The following information may help to resolve the situation: 101s 101s The following packages have unmet dependencies: 101s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 101s Depends: libvtk9-qt-dev but it is not going to be installed 101s Depends: build-essential but it is not going to be installed 101s Depends: cmake 101s E: Unable to satisfy dependencies. Reached two conflicting assignments: 101s 1. python3:amd64=3.13.9-3 is not selected for install 101s 2. python3:amd64=3.13.9-3 is selected as a downgrade because: 101s 1. satisfy:command-line:amd64=1 is selected for install 101s 2. satisfy:command-line:amd64 Depends libvtk9-dev 101s 3. libvtk9-dev:amd64 Depends python3-vtk9 (= 9.5.2+dfsg2-4ubuntu1) 101s 4. python3-vtk9:amd64 Depends python3 (< 3.14) 101s autopkgtest [17:56:57]: test buildPoint: preparing testbed 101s buildBoolean FAIL badpkg 101s blame: vtk9 101s 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. 101s Reading package lists... 102s Building dependency tree... 102s Reading state information... 102s Solving dependencies... 102s Some packages could not be installed. This may mean that you have 102s requested an impossible situation or if you are using the unstable 102s distribution that some required packages have not yet been created 102s or been moved out of Incoming. 102s The following information may help to resolve the situation: 102s 102s The following packages have unmet dependencies: 102s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 102s Depends: libvtk9-qt-dev but it is not going to be installed 102s Depends: build-essential but it is not going to be installed 102s Depends: cmake 102s E: Unable to satisfy dependencies. Reached two conflicting assignments: 102s 1. python3:amd64=3.13.9-3 is not selected for install 102s 2. python3:amd64=3.13.9-3 is selected as a downgrade because: 102s 1. satisfy:command-line:amd64=1 is selected for install 102s 2. satisfy:command-line:amd64 Depends libvtk9-dev 102s 3. libvtk9-dev:amd64 Depends python3-vtk9 (= 9.5.2+dfsg2-4ubuntu1) 102s 4. python3-vtk9:amd64 Depends python3 (< 3.14) 102s buildPoint FAIL badpkg 102s blame: vtk9 102s 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. 102s autopkgtest [17:56:58]: test buildVTU: preparing testbed 102s Reading package lists... 102s Building dependency tree... 102s Reading state information... 102s Solving dependencies... 102s Some packages could not be installed. This may mean that you have 102s requested an impossible situation or if you are using the unstable 102s distribution that some required packages have not yet been created 102s or been moved out of Incoming. 102s The following information may help to resolve the situation: 102s 102s The following packages have unmet dependencies: 102s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 102s Depends: libvtk9-qt-dev but it is not going to be installed 102s Depends: build-essential but it is not going to be installed 102s Depends: cmake 102s E: Unable to satisfy dependencies. Reached two conflicting assignments: 102s 1. python3:amd64=3.13.9-3 is not selected for install 102s 2. python3:amd64=3.13.9-3 is selected as a downgrade because: 102s 1. satisfy:command-line:amd64=1 is selected for install 102s 2. satisfy:command-line:amd64 Depends libvtk9-dev 102s 3. libvtk9-dev:amd64 Depends python3-vtk9 (= 9.5.2+dfsg2-4ubuntu1) 102s 4. python3-vtk9:amd64 Depends python3 (< 3.14) 102s buildVTU FAIL badpkg 102s blame: vtk9 102s 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. 102s autopkgtest [17:56:58]: test buildDistance: preparing testbed 102s Reading package lists... 102s Building dependency tree... 102s Reading state information... 103s Solving dependencies... 103s Some packages could not be installed. This may mean that you have 103s requested an impossible situation or if you are using the unstable 103s distribution that some required packages have not yet been created 103s or been moved out of Incoming. 103s The following information may help to resolve the situation: 103s 103s The following packages have unmet dependencies: 103s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 103s Depends: libvtk9-qt-dev but it is not going to be installed 103s Depends: build-essential but it is not going to be installed 103s Depends: cmake 103s E: Unable to satisfy dependencies. Reached two conflicting assignments: 103s 1. python3:amd64=3.13.9-3 is not selected for install 103s 2. python3:amd64=3.13.9-3 is selected as a downgrade because: 103s 1. satisfy:command-line:amd64=1 is selected for install 103s 2. satisfy:command-line:amd64 Depends libvtk9-dev 103s 3. libvtk9-dev:amd64 Depends python3-vtk9 (= 9.5.2+dfsg2-4ubuntu1) 103s 4. python3-vtk9:amd64 Depends python3 (< 3.14) 103s buildDistance FAIL badpkg 103s blame: vtk9 103s 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. 103s autopkgtest [17:56:59]: test buildPNG: preparing testbed 103s Reading package lists... 103s Building dependency tree... 103s Reading state information... 103s Solving dependencies... 103s Some packages could not be installed. This may mean that you have 103s requested an impossible situation or if you are using the unstable 103s distribution that some required packages have not yet been created 103s or been moved out of Incoming. 103s The following information may help to resolve the situation: 103s 103s The following packages have unmet dependencies: 103s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 103s Depends: libvtk9-qt-dev but it is not going to be installed 103s Depends: build-essential but it is not going to be installed 103s Depends: cmake 103s E: Unable to satisfy dependencies. Reached two conflicting assignments: 103s 1. python3:amd64=3.13.9-3 is not selected for install 103s 2. python3:amd64=3.13.9-3 is selected as a downgrade because: 103s 1. satisfy:command-line:amd64=1 is selected for install 103s 2. satisfy:command-line:amd64 Depends libvtk9-dev 103s 3. libvtk9-dev:amd64 Depends python3-vtk9 (= 9.5.2+dfsg2-4ubuntu1) 103s 4. python3-vtk9:amd64 Depends python3 (< 3.14) 103s buildPNG FAIL badpkg 103s blame: vtk9 103s 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. 103s autopkgtest [17:56:59]: test buildVTP: preparing testbed 103s Reading package lists... 103s Building dependency tree... 103s Reading state information... 104s Solving dependencies... 104s Some packages could not be installed. This may mean that you have 104s requested an impossible situation or if you are using the unstable 104s distribution that some required packages have not yet been created 104s or been moved out of Incoming. 104s The following information may help to resolve the situation: 104s 104s The following packages have unmet dependencies: 104s satisfy:command-line : Depends: libvtk9-dev but it is not going to be installed 104s Depends: libvtk9-qt-dev but it is not going to be installed 104s Depends: build-essential but it is not going to be installed 104s Depends: cmake 104s E: Unable to satisfy dependencies. Reached two conflicting assignments: 104s 1. python3:amd64=3.13.9-3 is not selected for install 104s 2. python3:amd64=3.13.9-3 is selected as a downgrade because: 104s 1. satisfy:command-line:amd64=1 is selected for install 104s 2. satisfy:command-line:amd64 Depends libvtk9-dev 104s 3. libvtk9-dev:amd64 Depends python3-vtk9 (= 9.5.2+dfsg2-4ubuntu1) 104s 4. python3-vtk9:amd64 Depends python3 (< 3.14) 104s buildVTP FAIL badpkg 104s blame: vtk9 104s 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. 104s autopkgtest [17:57:00]: @@@@@@@@@@@@@@@@@@@@ summary 104s buildBoolean FAIL badpkg 104s blame: vtk9 104s 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. 104s buildPoint FAIL badpkg 104s blame: vtk9 104s 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. 104s buildVTU FAIL badpkg 104s blame: vtk9 104s 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. 104s buildDistance FAIL badpkg 104s blame: vtk9 104s 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. 104s buildPNG FAIL badpkg 104s blame: vtk9 104s 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. 104s buildVTP FAIL badpkg 104s blame: vtk9 104s 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.