0s autopkgtest [12:50:37]: starting date and time: 2025-11-17 12:50:37+0000 0s autopkgtest [12:50:37]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [12:50:37]: host juju-7f2275-prod-proposed-migration-environment-2; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.xvhqyg6b/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-ppc64el --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-2@bos03-ppc64el-40.secgroup --name adt-resolute-ppc64el-scifem-20251117-125037-juju-7f2275-prod-proposed-migration-environment-2-a47d39fa-40dc-4a88-a505-505338f24123 --image adt/ubuntu-resolute-ppc64el-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-2 --net-id=net_prod-proposed-migration-ppc64el -e TERM=linux --mirror=http://ftpmaster.internal/ubuntu/ 4s Creating nova instance adt-resolute-ppc64el-scifem-20251117-125037-juju-7f2275-prod-proposed-migration-environment-2-a47d39fa-40dc-4a88-a505-505338f24123 from image adt/ubuntu-resolute-ppc64el-server-20251117.img (UUID c6f5b741-c77a-45db-84cb-f00b40e77676)... 59s autopkgtest [12:51:36]: testbed dpkg architecture: ppc64el 59s autopkgtest [12:51:36]: testbed apt version: 3.1.11 59s autopkgtest [12:51:36]: @@@@@@@@@@@@@@@@@@@@ test bed setup 59s autopkgtest [12:51:36]: testbed release detected to be: None 60s autopkgtest [12:51:37]: updating testbed package index (apt update) 61s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [87.8 kB] 61s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 61s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 61s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 61s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [868 kB] 62s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [22.9 kB] 62s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [9848 B] 62s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [81.1 kB] 62s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el Packages [140 kB] 62s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/restricted ppc64el Packages [940 B] 62s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/universe ppc64el Packages [562 kB] 63s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse ppc64el Packages [11.0 kB] 63s Fetched 1784 kB in 2s (726 kB/s) 64s Reading package lists... 64s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 64s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 65s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 65s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 66s Reading package lists... 66s Reading package lists... 66s Building dependency tree... 66s Reading state information... 66s Calculating upgrade... 66s The following packages will be upgraded: 66s libpython3-stdlib python3 python3-minimal usbutils 66s 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 66s Need to get 154 kB of archives. 66s After this operation, 0 B of additional disk space will be used. 66s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el python3-minimal ppc64el 3.13.7-2 [27.8 kB] 66s Get:2 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el python3 ppc64el 3.13.7-2 [23.9 kB] 66s Get:3 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el libpython3-stdlib ppc64el 3.13.7-2 [10.6 kB] 66s Get:4 http://ftpmaster.internal/ubuntu resolute/main ppc64el usbutils ppc64el 1:019-1 [91.5 kB] 67s dpkg-preconfigure: unable to re-open stdin: No such file or directory 67s Fetched 154 kB in 0s (354 kB/s) 67s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 81022 files and directories currently installed.) 67s Preparing to unpack .../python3-minimal_3.13.7-2_ppc64el.deb ... 67s Unpacking python3-minimal (3.13.7-2) over (3.13.7-1) ... 67s Setting up python3-minimal (3.13.7-2) ... 67s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 81022 files and directories currently installed.) 67s Preparing to unpack .../python3_3.13.7-2_ppc64el.deb ... 68s running python pre-rtupdate hooks for python3.13... 68s Unpacking python3 (3.13.7-2) over (3.13.7-1) ... 68s Preparing to unpack .../libpython3-stdlib_3.13.7-2_ppc64el.deb ... 68s Unpacking libpython3-stdlib:ppc64el (3.13.7-2) over (3.13.7-1) ... 68s Preparing to unpack .../usbutils_1%3a019-1_ppc64el.deb ... 68s Unpacking usbutils (1:019-1) over (1:018-2) ... 68s Setting up usbutils (1:019-1) ... 68s Setting up libpython3-stdlib:ppc64el (3.13.7-2) ... 68s Setting up python3 (3.13.7-2) ... 68s running python rtupdate hooks for python3.13... 68s running python post-rtupdate hooks for python3.13... 68s Processing triggers for man-db (2.13.1-1) ... 70s autopkgtest [12:51:47]: upgrading testbed (apt dist-upgrade and autopurge) 70s Reading package lists... 70s Building dependency tree... 70s Reading state information... 70s Calculating upgrade... 70s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 71s Reading package lists... 71s Building dependency tree... 71s Reading state information... 71s Solving dependencies... 71s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 74s autopkgtest [12:51:51]: testbed running kernel: Linux 6.17.0-5-generic #5-Ubuntu SMP PREEMPT_DYNAMIC Mon Sep 22 10:02:41 UTC 2025 74s autopkgtest [12:51:51]: @@@@@@@@@@@@@@@@@@@@ apt-source scifem 77s Get:1 http://ftpmaster.internal/ubuntu resolute/universe scifem 0.6.0-2 (dsc) [2418 B] 77s Get:2 http://ftpmaster.internal/ubuntu resolute/universe scifem 0.6.0-2 (tar) [1931 kB] 77s Get:3 http://ftpmaster.internal/ubuntu resolute/universe scifem 0.6.0-2 (diff) [4496 B] 77s gpgv: Signature made Fri May 30 11:06:51 2025 UTC 77s gpgv: using RSA key 23C9A93E585819E9126D0A36573EF1E4BD5A01FA 77s gpgv: Can't check signature: No public key 77s dpkg-source: warning: cannot verify inline signature for ./scifem_0.6.0-2.dsc: no acceptable signature found 77s autopkgtest [12:51:54]: testing package scifem version 0.6.0-2 78s autopkgtest [12:51:55]: build not needed 78s autopkgtest [12:51:55]: test command1: preparing testbed 79s Reading package lists... 79s Building dependency tree... 79s Reading state information... 79s Solving dependencies... 79s Some packages could not be installed. This may mean that you have 79s requested an impossible situation or if you are using the unstable 79s distribution that some required packages have not yet been created 79s or been moved out of Incoming. 79s The following information may help to resolve the situation: 79s 79s The following packages have unmet dependencies: 79s satisfy:command-line : Depends: python3-scifem but it is not going to be installed 79s Depends: python3-nibabel but it is not going to be installed 79s Depends: python3-pytest but it is not going to be installed 79s Depends: python3-all-dev but it is not going to be installed 79s E: Unable to satisfy dependencies. Reached two conflicting decisions: 79s 1. python3-basix:ppc64el is selected for install because: 79s 1. satisfy:command-line:ppc64el=1 is selected for install 79s 2. satisfy:command-line:ppc64el Depends python3-scifem 79s 3. python3-scifem:ppc64el Depends python3-basix 79s 2. python3-basix:ppc64el is available in versions 0.9.0-4, 0.9.0-2build2 79s but none of the choices are installable: 79s - python3-basix:ppc64el=0.9.0-4 is not selected for install because: 79s 1. satisfy:command-line:ppc64el=1 is selected for install as above 79s 1-2. python3-scifem:ppc64el is selected for install as above 79s 3. python3-scifem:ppc64el is available in version 0.6.0-2 79s 4. python3-basix:ppc64el=0.9.0-4 Breaks python3-scifem (< 0.10.0-1~) 79s - python3-basix:ppc64el=0.9.0-2build2 is not selected for install 79s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 79s Reading package lists... 79s Building dependency tree... 79s Reading state information... 80s Solving dependencies... 80s Some packages could not be installed. This may mean that you have 80s requested an impossible situation or if you are using the unstable 80s distribution that some required packages have not yet been created 80s or been moved out of Incoming. 80s The following information may help to resolve the situation: 80s 80s The following packages have unmet dependencies: 80s satisfy:command-line : Depends: python3-scifem but it is not going to be installed 80s Depends: python3-nibabel but it is not going to be installed 80s Depends: python3-pytest but it is not going to be installed 80s Depends: python3-all-dev but it is not going to be installed 80s E: Unable to satisfy dependencies. Reached two conflicting decisions: 80s 1. python3-basix:ppc64el is selected for install because: 80s 1. satisfy:command-line:ppc64el=1 is selected for install 80s 2. satisfy:command-line:ppc64el Depends python3-scifem 80s 3. python3-scifem:ppc64el Depends python3-basix 80s 2. python3-basix:ppc64el is available in versions 0.9.0-4, 0.9.0-2build2 80s but none of the choices are installable: 80s - python3-basix:ppc64el=0.9.0-4 is not selected for install because: 80s 1. satisfy:command-line:ppc64el=1 is selected for install as above 80s 1-2. python3-scifem:ppc64el is selected for install as above 80s 3. python3-scifem:ppc64el is available in version 0.6.0-2 80s 4. python3-basix:ppc64el=0.9.0-4 Breaks python3-scifem (< 0.10.0-1~) 80s - python3-basix:ppc64el=0.9.0-2build2 is not selected for install 80s command1 FAIL badpkg 80s blame: scifem 80s 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. 80s autopkgtest [12:51:57]: test command2: preparing testbed 101s Creating nova instance adt-resolute-ppc64el-scifem-20251117-125037-juju-7f2275-prod-proposed-migration-environment-2-a47d39fa-40dc-4a88-a505-505338f24123 from image adt/ubuntu-resolute-ppc64el-server-20251117.img (UUID c6f5b741-c77a-45db-84cb-f00b40e77676)... 157s autopkgtest [12:53:14]: testbed dpkg architecture: ppc64el 157s autopkgtest [12:53:14]: testbed apt version: 3.1.11 158s autopkgtest [12:53:15]: @@@@@@@@@@@@@@@@@@@@ test bed setup 158s autopkgtest [12:53:15]: testbed release detected to be: resolute 159s autopkgtest [12:53:16]: updating testbed package index (apt update) 159s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [87.8 kB] 159s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 159s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 159s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 160s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [81.1 kB] 160s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [22.9 kB] 160s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [868 kB] 160s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [9848 B] 160s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el Packages [140 kB] 160s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/restricted ppc64el Packages [940 B] 160s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/universe ppc64el Packages [562 kB] 160s Get:12 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse ppc64el Packages [11.0 kB] 160s Fetched 1784 kB in 1s (1235 kB/s) 161s Reading package lists... 162s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 162s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 162s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 162s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 163s Reading package lists... 163s Reading package lists... 163s Building dependency tree... 163s Reading state information... 163s Calculating upgrade... 163s The following packages will be upgraded: 163s libpython3-stdlib python3 python3-minimal usbutils 163s 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 163s Need to get 154 kB of archives. 163s After this operation, 0 B of additional disk space will be used. 163s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el python3-minimal ppc64el 3.13.7-2 [27.8 kB] 164s Get:2 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el python3 ppc64el 3.13.7-2 [23.9 kB] 164s Get:3 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el libpython3-stdlib ppc64el 3.13.7-2 [10.6 kB] 164s Get:4 http://ftpmaster.internal/ubuntu resolute/main ppc64el usbutils ppc64el 1:019-1 [91.5 kB] 164s dpkg-preconfigure: unable to re-open stdin: No such file or directory 164s Fetched 154 kB in 0s (345 kB/s) 164s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 81022 files and directories currently installed.) 164s Preparing to unpack .../python3-minimal_3.13.7-2_ppc64el.deb ... 164s Unpacking python3-minimal (3.13.7-2) over (3.13.7-1) ... 164s Setting up python3-minimal (3.13.7-2) ... 165s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 81022 files and directories currently installed.) 165s Preparing to unpack .../python3_3.13.7-2_ppc64el.deb ... 165s running python pre-rtupdate hooks for python3.13... 165s Unpacking python3 (3.13.7-2) over (3.13.7-1) ... 165s Preparing to unpack .../libpython3-stdlib_3.13.7-2_ppc64el.deb ... 165s Unpacking libpython3-stdlib:ppc64el (3.13.7-2) over (3.13.7-1) ... 165s Preparing to unpack .../usbutils_1%3a019-1_ppc64el.deb ... 165s Unpacking usbutils (1:019-1) over (1:018-2) ... 165s Setting up usbutils (1:019-1) ... 165s Setting up libpython3-stdlib:ppc64el (3.13.7-2) ... 165s Setting up python3 (3.13.7-2) ... 165s running python rtupdate hooks for python3.13... 165s running python post-rtupdate hooks for python3.13... 165s Processing triggers for man-db (2.13.1-1) ... 167s autopkgtest [12:53:24]: upgrading testbed (apt dist-upgrade and autopurge) 167s Reading package lists... 167s Building dependency tree... 167s Reading state information... 167s Calculating upgrade... 167s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 167s Reading package lists... 168s Building dependency tree... 168s Reading state information... 168s Solving dependencies... 168s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 171s Reading package lists... 171s Building dependency tree... 171s Reading state information... 171s Solving dependencies... 171s Some packages could not be installed. This may mean that you have 171s requested an impossible situation or if you are using the unstable 171s distribution that some required packages have not yet been created 171s or been moved out of Incoming. 171s The following information may help to resolve the situation: 171s 171s The following packages have unmet dependencies: 171s satisfy:command-line : Depends: python3-scifem but it is not going to be installed 171s Depends: python3-pytest but it is not going to be installed 171s Depends: python3-all-dev but it is not going to be installed 171s E: Unable to satisfy dependencies. Reached two conflicting decisions: 171s 1. python3-basix:ppc64el is selected for install because: 171s 1. satisfy:command-line:ppc64el=1 is selected for install 171s 2. satisfy:command-line:ppc64el Depends python3-scifem 171s 3. python3-scifem:ppc64el Depends python3-basix 171s 2. python3-basix:ppc64el is available in versions 0.9.0-4, 0.9.0-2build2 171s but none of the choices are installable: 171s - python3-basix:ppc64el=0.9.0-4 is not selected for install because: 171s 1. satisfy:command-line:ppc64el=1 is selected for install as above 171s 1-2. python3-scifem:ppc64el is selected for install as above 171s 3. python3-scifem:ppc64el is available in version 0.6.0-2 171s 4. python3-basix:ppc64el=0.9.0-4 Breaks python3-scifem (< 0.10.0-1~) 171s - python3-basix:ppc64el=0.9.0-2build2 is not selected for install 171s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 171s Reading package lists... 171s Building dependency tree... 171s Reading state information... 171s Solving dependencies... 171s Some packages could not be installed. This may mean that you have 171s requested an impossible situation or if you are using the unstable 171s distribution that some required packages have not yet been created 171s or been moved out of Incoming. 171s The following information may help to resolve the situation: 171s 171s The following packages have unmet dependencies: 172s satisfy:command-line : Depends: python3-scifem but it is not going to be installed 172s Depends: python3-pytest but it is not going to be installed 172s Depends: python3-all-dev but it is not going to be installed 172s E: Unable to satisfy dependencies. Reached two conflicting decisions: 172s 1. python3-basix:ppc64el is selected for install because: 172s 1. satisfy:command-line:ppc64el=1 is selected for install 172s 2. satisfy:command-line:ppc64el Depends python3-scifem 172s 3. python3-scifem:ppc64el Depends python3-basix 172s 2. python3-basix:ppc64el is available in versions 0.9.0-4, 0.9.0-2build2 172s but none of the choices are installable: 172s - python3-basix:ppc64el=0.9.0-4 is not selected for install because: 172s 1. satisfy:command-line:ppc64el=1 is selected for install as above 172s 1-2. python3-scifem:ppc64el is selected for install as above 172s 3. python3-scifem:ppc64el is available in version 0.6.0-2 172s 4. python3-basix:ppc64el=0.9.0-4 Breaks python3-scifem (< 0.10.0-1~) 172s - python3-basix:ppc64el=0.9.0-2build2 is not selected for install 172s command2 FAIL badpkg 172s blame: scifem 172s 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. 172s autopkgtest [12:53:29]: test test-MPI: preparing testbed 172s Reading package lists... 172s Building dependency tree... 172s Reading state information... 172s Solving dependencies... 172s Some packages could not be installed. This may mean that you have 172s requested an impossible situation or if you are using the unstable 172s distribution that some required packages have not yet been created 172s or been moved out of Incoming. 172s The following information may help to resolve the situation: 172s 172s The following packages have unmet dependencies: 172s satisfy:command-line : Depends: python3-scifem but it is not going to be installed 172s Depends: python3-nibabel but it is not going to be installed 172s Depends: python3-pytest but it is not going to be installed 172s Depends: python3-all-dev but it is not going to be installed 172s Depends: python3-h5py-mpi but it is not going to be installed 172s Depends: mpi-default-dev but it is not going to be installed 172s E: Unable to satisfy dependencies. Reached two conflicting decisions: 172s 1. python3-basix:ppc64el is selected for install because: 172s 1. satisfy:command-line:ppc64el=1 is selected for install 172s 2. satisfy:command-line:ppc64el Depends python3-scifem 172s 3. python3-scifem:ppc64el Depends python3-basix 172s 2. python3-basix:ppc64el is available in versions 0.9.0-4, 0.9.0-2build2 172s but none of the choices are installable: 172s - python3-basix:ppc64el=0.9.0-4 is not selected for install because: 172s 1. satisfy:command-line:ppc64el=1 is selected for install as above 172s 1-2. python3-scifem:ppc64el is selected for install as above 172s 3. python3-scifem:ppc64el is available in version 0.6.0-2 172s 4. python3-basix:ppc64el=0.9.0-4 Breaks python3-scifem (< 0.10.0-1~) 172s - python3-basix:ppc64el=0.9.0-2build2 is not selected for install 172s autopkgtest [12:53:29]: @@@@@@@@@@@@@@@@@@@@ summary 172s command1 FAIL badpkg 172s blame: scifem 172s 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. 172s command2 FAIL badpkg 172s blame: scifem 172s 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. 172s test-MPI FAIL badpkg 172s blame: scifem 172s 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. 172s test-MPI FAIL badpkg 172s blame: scifem 172s 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.