0s autopkgtest [11:45:27]: starting date and time: 2025-11-17 11:45:27+0000 0s autopkgtest [11:45:27]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [11:45:27]: host juju-7f2275-prod-proposed-migration-environment-2; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.qat2x1rb/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:fenics-basix,src:python3-defaults --apt-upgrade scifem --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 '--env=ADT_TEST_TRIGGERS=fenics-basix/0.9.0-4 python3-defaults/3.13.7-2' -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest-cpu2-ram4-disk20-amd64 --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-2@sto01-10.secgroup --name adt-resolute-amd64-scifem-20251117-114527-juju-7f2275-prod-proposed-migration-environment-2-d4294770-e98b-47da-9006-39e07b9b9e30 --image adt/ubuntu-resolute-amd64-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-2 --net-id=net_prod-autopkgtest-workers-amd64 -e TERM=linux --mirror=http://ftpmaster.internal/ubuntu/ 4s Creating nova instance adt-resolute-amd64-scifem-20251117-114527-juju-7f2275-prod-proposed-migration-environment-2-d4294770-e98b-47da-9006-39e07b9b9e30 from image adt/ubuntu-resolute-amd64-server-20251117.img (UUID 9762b0cc-7c5b-4854-acd5-cc74ad0de8c6)... 47s autopkgtest [11:46:14]: testbed dpkg architecture: amd64 48s autopkgtest [11:46:15]: testbed apt version: 3.1.11 48s autopkgtest [11:46:15]: @@@@@@@@@@@@@@@@@@@@ test bed setup 48s autopkgtest [11:46:15]: testbed release detected to be: None 49s autopkgtest [11:46:16]: updating testbed package index (apt update) 50s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [87.8 kB] 50s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 50s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 50s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 50s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [9848 B] 50s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [868 kB] 50s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [81.1 kB] 50s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [22.9 kB] 50s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 Packages [159 kB] 50s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/main i386 Packages [118 kB] 50s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 c-n-f Metadata [3096 B] 50s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/restricted i386 Packages [3744 B] 50s Get:13 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 Packages [64.6 kB] 50s Get:14 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 c-n-f Metadata [336 B] 50s Get:15 http://ftpmaster.internal/ubuntu resolute-proposed/universe i386 Packages [279 kB] 50s Get:16 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 Packages [607 kB] 50s Get:17 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 c-n-f Metadata [21.2 kB] 50s Get:18 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse i386 Packages [6516 B] 50s Get:19 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 Packages [13.4 kB] 51s Get:20 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 c-n-f Metadata [680 B] 52s Fetched 2346 kB in 1s (2275 kB/s) 53s Reading package lists... 53s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 53s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 53s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 53s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 54s Reading package lists... 54s Reading package lists... 54s Building dependency tree... 54s Reading state information... 54s Calculating upgrade... 54s The following packages will be upgraded: 54s libpython3-stdlib python3 python3-minimal usbutils 54s 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 54s Need to get 146 kB of archives. 54s After this operation, 0 B of additional disk space will be used. 54s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 python3-minimal amd64 3.13.7-2 [27.8 kB] 54s Get:2 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 python3 amd64 3.13.7-2 [23.9 kB] 54s Get:3 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 libpython3-stdlib amd64 3.13.7-2 [10.6 kB] 54s Get:4 http://ftpmaster.internal/ubuntu resolute/main amd64 usbutils amd64 1:019-1 [83.9 kB] 54s dpkg-preconfigure: unable to re-open stdin: No such file or directory 54s Fetched 146 kB in 0s (13.1 MB/s) 55s (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.) 55s Preparing to unpack .../python3-minimal_3.13.7-2_amd64.deb ... 55s Unpacking python3-minimal (3.13.7-2) over (3.13.7-1) ... 55s Setting up python3-minimal (3.13.7-2) ... 55s (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.) 55s Preparing to unpack .../python3_3.13.7-2_amd64.deb ... 55s running python pre-rtupdate hooks for python3.13... 55s Unpacking python3 (3.13.7-2) over (3.13.7-1) ... 55s Preparing to unpack .../libpython3-stdlib_3.13.7-2_amd64.deb ... 55s Unpacking libpython3-stdlib:amd64 (3.13.7-2) over (3.13.7-1) ... 55s Preparing to unpack .../usbutils_1%3a019-1_amd64.deb ... 55s Unpacking usbutils (1:019-1) over (1:018-2) ... 55s Setting up usbutils (1:019-1) ... 55s Setting up libpython3-stdlib:amd64 (3.13.7-2) ... 55s Setting up python3 (3.13.7-2) ... 55s running python rtupdate hooks for python3.13... 55s running python post-rtupdate hooks for python3.13... 55s Processing triggers for man-db (2.13.1-1) ... 56s autopkgtest [11:46:23]: upgrading testbed (apt dist-upgrade and autopurge) 56s Reading package lists... 56s Building dependency tree... 56s Reading state information... 56s Calculating upgrade... 56s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 56s Reading package lists... 57s Building dependency tree... 57s Reading state information... 57s Solving dependencies... 57s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 59s autopkgtest [11:46:26]: testbed running kernel: Linux 6.17.0-5-generic #5-Ubuntu SMP PREEMPT_DYNAMIC Mon Sep 22 10:00:33 UTC 2025 59s autopkgtest [11:46:26]: @@@@@@@@@@@@@@@@@@@@ apt-source scifem 61s Get:1 http://ftpmaster.internal/ubuntu resolute/universe scifem 0.6.0-2 (dsc) [2418 B] 61s Get:2 http://ftpmaster.internal/ubuntu resolute/universe scifem 0.6.0-2 (tar) [1931 kB] 61s Get:3 http://ftpmaster.internal/ubuntu resolute/universe scifem 0.6.0-2 (diff) [4496 B] 61s gpgv: Signature made Fri May 30 11:06:51 2025 UTC 61s gpgv: using RSA key 23C9A93E585819E9126D0A36573EF1E4BD5A01FA 61s gpgv: Can't check signature: No public key 61s dpkg-source: warning: cannot verify inline signature for ./scifem_0.6.0-2.dsc: no acceptable signature found 61s autopkgtest [11:46:28]: testing package scifem version 0.6.0-2 61s autopkgtest [11:46:28]: build not needed 62s autopkgtest [11:46:29]: test command1: preparing testbed 62s Reading package lists... 62s Building dependency tree... 62s Reading state information... 62s Solving dependencies... 62s Some packages could not be installed. This may mean that you have 62s requested an impossible situation or if you are using the unstable 62s distribution that some required packages have not yet been created 62s or been moved out of Incoming. 62s The following information may help to resolve the situation: 62s 62s The following packages have unmet dependencies: 62s satisfy:command-line : Depends: python3-scifem but it is not going to be installed 62s Depends: python3-nibabel but it is not going to be installed 62s Depends: python3-pytest but it is not going to be installed 62s Depends: python3-all-dev but it is not going to be installed 62s E: Unable to satisfy dependencies. Reached two conflicting decisions: 62s 1. python3-basix:amd64 is selected for install because: 62s 1. satisfy:command-line:amd64=1 is selected for install 62s 2. satisfy:command-line:amd64 Depends python3-scifem 62s 3. python3-scifem:amd64 Depends python3-basix 62s 2. python3-basix:amd64 is available in versions 0.9.0-4, 0.9.0-2build2 62s but none of the choices are installable: 62s - python3-basix:amd64=0.9.0-4 is not selected for install because: 62s 1. satisfy:command-line:amd64=1 is selected for install as above 62s 1-2. python3-scifem:amd64 is selected for install as above 62s 3. python3-scifem:amd64 is available in version 0.6.0-2 62s 4. python3-basix:amd64=0.9.0-4 Breaks python3-scifem (< 0.10.0-1~) 62s - python3-basix:amd64=0.9.0-2build2 is not selected for install 62s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 63s Reading package lists... 63s Building dependency tree... 63s Reading state information... 63s Solving dependencies... 63s Some packages could not be installed. This may mean that you have 63s requested an impossible situation or if you are using the unstable 63s distribution that some required packages have not yet been created 63s or been moved out of Incoming. 63s The following information may help to resolve the situation: 63s 63s The following packages have unmet dependencies: 63s satisfy:command-line : Depends: python3-scifem but it is not going to be installed 63s Depends: python3-nibabel but it is not going to be installed 63s Depends: python3-pytest but it is not going to be installed 63s Depends: python3-all-dev but it is not going to be installed 63s E: Unable to satisfy dependencies. Reached two conflicting decisions: 63s 1. python3-basix:amd64 is selected for install because: 63s 1. satisfy:command-line:amd64=1 is selected for install 63s 2. satisfy:command-line:amd64 Depends python3-scifem 63s 3. python3-scifem:amd64 Depends python3-basix 63s 2. python3-basix:amd64 is available in versions 0.9.0-4, 0.9.0-2build2 63s but none of the choices are installable: 63s - python3-basix:amd64=0.9.0-4 is not selected for install because: 63s 1. satisfy:command-line:amd64=1 is selected for install as above 63s 1-2. python3-scifem:amd64 is selected for install as above 63s 3. python3-scifem:amd64 is available in version 0.6.0-2 63s 4. python3-basix:amd64=0.9.0-4 Breaks python3-scifem (< 0.10.0-1~) 63s - python3-basix:amd64=0.9.0-2build2 is not selected for install 63s command1 FAIL badpkg 63s blame: scifem 63s 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. 63s autopkgtest [11:46:30]: test command2: preparing testbed 83s Creating nova instance adt-resolute-amd64-scifem-20251117-114527-juju-7f2275-prod-proposed-migration-environment-2-d4294770-e98b-47da-9006-39e07b9b9e30 from image adt/ubuntu-resolute-amd64-server-20251117.img (UUID 9762b0cc-7c5b-4854-acd5-cc74ad0de8c6)... 125s autopkgtest [11:47:32]: testbed dpkg architecture: amd64 125s autopkgtest [11:47:32]: testbed apt version: 3.1.11 126s autopkgtest [11:47:33]: @@@@@@@@@@@@@@@@@@@@ test bed setup 126s autopkgtest [11:47:33]: testbed release detected to be: resolute 126s autopkgtest [11:47:33]: updating testbed package index (apt update) 127s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [87.8 kB] 127s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 127s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 127s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 127s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [868 kB] 127s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [9848 B] 127s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [81.1 kB] 127s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [22.9 kB] 127s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 Packages [159 kB] 127s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/main i386 Packages [118 kB] 127s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 c-n-f Metadata [3096 B] 127s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/restricted i386 Packages [3744 B] 127s Get:13 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 Packages [64.6 kB] 127s Get:14 http://ftpmaster.internal/ubuntu resolute-proposed/restricted amd64 c-n-f Metadata [336 B] 127s Get:15 http://ftpmaster.internal/ubuntu resolute-proposed/universe i386 Packages [279 kB] 127s Get:16 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 Packages [607 kB] 127s Get:17 http://ftpmaster.internal/ubuntu resolute-proposed/universe amd64 c-n-f Metadata [21.2 kB] 127s Get:18 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse i386 Packages [6516 B] 128s Get:19 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 Packages [13.4 kB] 128s Get:20 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse amd64 c-n-f Metadata [680 B] 129s Fetched 2346 kB in 1s (2293 kB/s) 130s Reading package lists... 130s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 130s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 130s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 130s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 131s Reading package lists... 131s Reading package lists... 131s Building dependency tree... 131s Reading state information... 131s Calculating upgrade... 131s The following packages will be upgraded: 131s libpython3-stdlib python3 python3-minimal usbutils 131s 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 131s Need to get 146 kB of archives. 131s After this operation, 0 B of additional disk space will be used. 131s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 python3-minimal amd64 3.13.7-2 [27.8 kB] 131s Get:2 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 python3 amd64 3.13.7-2 [23.9 kB] 131s Get:3 http://ftpmaster.internal/ubuntu resolute-proposed/main amd64 libpython3-stdlib amd64 3.13.7-2 [10.6 kB] 131s Get:4 http://ftpmaster.internal/ubuntu resolute/main amd64 usbutils amd64 1:019-1 [83.9 kB] 131s dpkg-preconfigure: unable to re-open stdin: No such file or directory 131s Fetched 146 kB in 0s (0 B/s) 131s (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.) 131s Preparing to unpack .../python3-minimal_3.13.7-2_amd64.deb ... 131s Unpacking python3-minimal (3.13.7-2) over (3.13.7-1) ... 131s Setting up python3-minimal (3.13.7-2) ... 132s (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.) 132s Preparing to unpack .../python3_3.13.7-2_amd64.deb ... 132s running python pre-rtupdate hooks for python3.13... 132s Unpacking python3 (3.13.7-2) over (3.13.7-1) ... 132s Preparing to unpack .../libpython3-stdlib_3.13.7-2_amd64.deb ... 132s Unpacking libpython3-stdlib:amd64 (3.13.7-2) over (3.13.7-1) ... 132s Preparing to unpack .../usbutils_1%3a019-1_amd64.deb ... 132s Unpacking usbutils (1:019-1) over (1:018-2) ... 132s Setting up usbutils (1:019-1) ... 132s Setting up libpython3-stdlib:amd64 (3.13.7-2) ... 132s Setting up python3 (3.13.7-2) ... 132s running python rtupdate hooks for python3.13... 132s running python post-rtupdate hooks for python3.13... 132s Processing triggers for man-db (2.13.1-1) ... 132s autopkgtest [11:47:39]: upgrading testbed (apt dist-upgrade and autopurge) 133s Reading package lists... 133s Building dependency tree... 133s Reading state information... 133s Calculating upgrade... 133s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 133s Reading package lists... 133s Building dependency tree... 133s Reading state information... 133s Solving dependencies... 133s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 135s Reading package lists... 136s Building dependency tree... 136s Reading state information... 136s Solving dependencies... 136s Some packages could not be installed. This may mean that you have 136s requested an impossible situation or if you are using the unstable 136s distribution that some required packages have not yet been created 136s or been moved out of Incoming. 136s The following information may help to resolve the situation: 136s 136s The following packages have unmet dependencies: 136s satisfy:command-line : Depends: python3-scifem but it is not going to be installed 136s Depends: python3-pytest but it is not going to be installed 136s Depends: python3-all-dev but it is not going to be installed 136s E: Unable to satisfy dependencies. Reached two conflicting decisions: 136s 1. python3-basix:amd64 is selected for install because: 136s 1. satisfy:command-line:amd64=1 is selected for install 136s 2. satisfy:command-line:amd64 Depends python3-scifem 136s 3. python3-scifem:amd64 Depends python3-basix 136s 2. python3-basix:amd64 is available in versions 0.9.0-4, 0.9.0-2build2 136s but none of the choices are installable: 136s - python3-basix:amd64=0.9.0-4 is not selected for install because: 136s 1. satisfy:command-line:amd64=1 is selected for install as above 136s 1-2. python3-scifem:amd64 is selected for install as above 136s 3. python3-scifem:amd64 is available in version 0.6.0-2 136s 4. python3-basix:amd64=0.9.0-4 Breaks python3-scifem (< 0.10.0-1~) 136s - python3-basix:amd64=0.9.0-2build2 is not selected for install 136s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 136s Reading package lists... 136s Building dependency tree... 136s Reading state information... 136s Solving dependencies... 136s Some packages could not be installed. This may mean that you have 136s requested an impossible situation or if you are using the unstable 136s distribution that some required packages have not yet been created 136s or been moved out of Incoming. 136s The following information may help to resolve the situation: 136s 136s The following packages have unmet dependencies: 136s satisfy:command-line : Depends: python3-scifem but it is not going to be installed 136s Depends: python3-pytest but it is not going to be installed 136s Depends: python3-all-dev but it is not going to be installed 136s E: Unable to satisfy dependencies. Reached two conflicting decisions: 136s 1. python3-basix:amd64 is selected for install because: 136s 1. satisfy:command-line:amd64=1 is selected for install 136s 2. satisfy:command-line:amd64 Depends python3-scifem 136s 3. python3-scifem:amd64 Depends python3-basix 136s 2. python3-basix:amd64 is available in versions 0.9.0-4, 0.9.0-2build2 136s but none of the choices are installable: 136s - python3-basix:amd64=0.9.0-4 is not selected for install because: 136s 1. satisfy:command-line:amd64=1 is selected for install as above 136s 1-2. python3-scifem:amd64 is selected for install as above 136s 3. python3-scifem:amd64 is available in version 0.6.0-2 136s 4. python3-basix:amd64=0.9.0-4 Breaks python3-scifem (< 0.10.0-1~) 136s - python3-basix:amd64=0.9.0-2build2 is not selected for install 136s command2 FAIL badpkg 136s blame: scifem 136s 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. 136s autopkgtest [11:47:43]: test test-MPI: preparing testbed 137s Reading package lists... 137s Building dependency tree... 137s Reading state information... 137s Solving dependencies... 137s Some packages could not be installed. This may mean that you have 137s requested an impossible situation or if you are using the unstable 137s distribution that some required packages have not yet been created 137s or been moved out of Incoming. 137s The following information may help to resolve the situation: 137s 137s The following packages have unmet dependencies: 137s satisfy:command-line : Depends: python3-scifem but it is not going to be installed 137s Depends: python3-nibabel but it is not going to be installed 137s Depends: python3-pytest but it is not going to be installed 137s Depends: python3-all-dev but it is not going to be installed 137s Depends: python3-h5py-mpi but it is not going to be installed 137s Depends: mpi-default-dev but it is not going to be installed 137s E: Unable to satisfy dependencies. Reached two conflicting decisions: 137s 1. python3-basix:amd64 is selected for install because: 137s 1. satisfy:command-line:amd64=1 is selected for install 137s 2. satisfy:command-line:amd64 Depends python3-scifem 137s 3. python3-scifem:amd64 Depends python3-basix 137s 2. python3-basix:amd64 is available in versions 0.9.0-4, 0.9.0-2build2 137s but none of the choices are installable: 137s - python3-basix:amd64=0.9.0-4 is not selected for install because: 137s 1. satisfy:command-line:amd64=1 is selected for install as above 137s 1-2. python3-scifem:amd64 is selected for install as above 137s 3. python3-scifem:amd64 is available in version 0.6.0-2 137s 4. python3-basix:amd64=0.9.0-4 Breaks python3-scifem (< 0.10.0-1~) 137s - python3-basix:amd64=0.9.0-2build2 is not selected for install 137s test-MPI FAIL badpkg 137s blame: scifem 137s 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. 137s autopkgtest [11:47:44]: @@@@@@@@@@@@@@@@@@@@ summary 137s command1 FAIL badpkg 137s blame: scifem 137s 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. 137s command2 FAIL badpkg 137s blame: scifem 137s 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. 137s test-MPI FAIL badpkg 137s blame: scifem 137s 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.