0s autopkgtest [19:16:56]: starting date and time: 2026-01-24 19:16:56+0000 0s autopkgtest [19:16:56]: git checkout: 4b346b80 nova: make wait_reboot return success even when a no-op 0s autopkgtest [19:16:56]: host juju-7f2275-prod-proposed-migration-environment-15; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.p8d3bmsr/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:zlib --apt-upgrade lammps --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 --env=ADT_TEST_TRIGGERS=zlib/1:1.3.dfsg+really1.3.1-1ubuntu3 -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest-cpu2-ram4-disk20-ppc64el --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-15@sto01-ppc64el-1.secgroup --name adt-resolute-ppc64el-lammps-20260124-191656-juju-7f2275-prod-proposed-migration-environment-15-144f834d-7ff5-4e38-85fa-8214b25f6b6e --image adt/ubuntu-resolute-ppc64el-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-15 --net-id=net_prod-autopkgtest-workers-ppc64el -e TERM=linux --mirror=http://ftpmaster.internal/ubuntu/ 3s Creating nova instance adt-resolute-ppc64el-lammps-20260124-191656-juju-7f2275-prod-proposed-migration-environment-15-144f834d-7ff5-4e38-85fa-8214b25f6b6e from image adt/ubuntu-resolute-ppc64el-server-20260124.img (UUID a269ca64-3301-4299-8bab-2247218fc911)... 49s autopkgtest [19:17:45]: testbed dpkg architecture: ppc64el 49s autopkgtest [19:17:45]: testbed apt version: 3.1.13 49s autopkgtest [19:17:45]: @@@@@@@@@@@@@@@@@@@@ test bed setup 50s autopkgtest [19:17:46]: testbed release detected to be: None 50s autopkgtest [19:17:46]: updating testbed package index (apt update) 50s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [124 kB] 50s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 50s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 51s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 51s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [24.3 kB] 51s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [976 kB] 51s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [2820 B] 51s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [95.5 kB] 51s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el Packages [107 kB] 51s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/universe ppc64el Packages [806 kB] 51s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse ppc64el Packages [9920 B] 51s Fetched 2145 kB in 1s (2859 kB/s) 52s Reading package lists... 52s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 52s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 52s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 53s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 53s Reading package lists... 53s Reading package lists... 53s Building dependency tree... 53s Reading state information... 54s Calculating upgrade...dpkg-preconfigure: unable to re-open stdin: No such file or directory 54s 54s The following packages will be upgraded: 54s zlib1g 54s 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 54s Need to get 74.6 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 ppc64el zlib1g ppc64el 1:1.3.dfsg+really1.3.1-1ubuntu3 [74.6 kB] 54s Fetched 74.6 kB in 0s (0 B/s) 54s (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 ... 120851 files and directories currently installed.) 54s Preparing to unpack .../zlib1g_1%3a1.3.dfsg+really1.3.1-1ubuntu3_ppc64el.deb ... 54s Unpacking zlib1g:ppc64el (1:1.3.dfsg+really1.3.1-1ubuntu3) over (1:1.3.dfsg+really1.3.1-1ubuntu2) ... 54s Setting up zlib1g:ppc64el (1:1.3.dfsg+really1.3.1-1ubuntu3) ... 54s Processing triggers for libc-bin (2.42-2ubuntu4) ... 55s autopkgtest [19:17:51]: upgrading testbed (apt dist-upgrade and autopurge) 55s Reading package lists... 55s Building dependency tree... 55s Reading state information... 55s Calculating upgrade... 55s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 55s Reading package lists... 55s Building dependency tree... 55s Reading state information... 55s Solving dependencies... 55s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 58s autopkgtest [19:17:54]: testbed running kernel: Linux 6.18.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 12 16:45:54 UTC 2026 58s autopkgtest [19:17:54]: @@@@@@@@@@@@@@@@@@@@ apt-source lammps 63s Get:1 http://ftpmaster.internal/ubuntu resolute/universe lammps 20251210+dfsg-1 (dsc) [3310 B] 63s Get:2 http://ftpmaster.internal/ubuntu resolute/universe lammps 20251210+dfsg-1 (tar) [133 MB] 63s Get:3 http://ftpmaster.internal/ubuntu resolute/universe lammps 20251210+dfsg-1 (diff) [16.0 kB] 64s gpgv: Signature made Thu Jan 1 15:43:35 2026 UTC 64s gpgv: using RSA key 23C9A93E585819E9126D0A36573EF1E4BD5A01FA 64s gpgv: issuer "dparsons@debian.org" 64s gpgv: Can't check signature: No public key 64s dpkg-source: warning: cannot verify inline signature for ./lammps_20251210+dfsg-1.dsc: no acceptable signature found 70s autopkgtest [19:18:06]: testing package lammps version 20251210+dfsg-1 71s autopkgtest [19:18:07]: build not needed 87s autopkgtest [19:18:23]: test crack: preparing testbed 87s Reading package lists... 88s Building dependency tree... 88s Reading state information... 88s Solving dependencies... 88s Some packages could not be installed. This may mean that you have 88s requested an impossible situation or if you are using the unstable 88s distribution that some required packages have not yet been created 88s or been moved out of Incoming. 88s The following information may help to resolve the situation: 88s 88s The following packages have unmet dependencies: 88s satisfy:command-line : Depends: lammps but it is not going to be installed 88s E: Unable to satisfy dependencies. Reached two conflicting assignments: 88s 1. libamdhip64-6:ppc64el is selected for install because: 88s 1. satisfy:command-line:ppc64el=1 is selected for install 88s 2. satisfy:command-line:ppc64el Depends lammps 88s 3. lammps:ppc64el Depends libopenmpi40 (>= 5.0.8) 88s 4. libopenmpi40:ppc64el Depends libucx0 88s 5. libucx0:ppc64el Depends libamdhip64-6 (>= 6.1.5) 88s 2. libamdhip64-6:ppc64el Depends libamd-comgr3 88s but none of the choices are installable: 88s [no choices] 88s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 88s Reading package lists... 88s Building dependency tree... 88s Reading state information... 88s Solving dependencies... 88s Some packages could not be installed. This may mean that you have 88s requested an impossible situation or if you are using the unstable 88s distribution that some required packages have not yet been created 88s or been moved out of Incoming. 88s The following information may help to resolve the situation: 88s 88s The following packages have unmet dependencies: 88s satisfy:command-line : Depends: lammps but it is not going to be installed 88s E: Unable to satisfy dependencies. Reached two conflicting assignments: 88s 1. libamdhip64-6:ppc64el is selected for install because: 88s 1. satisfy:command-line:ppc64el=1 is selected for install 88s 2. satisfy:command-line:ppc64el Depends lammps 88s 3. lammps:ppc64el Depends libopenmpi40 (>= 5.0.8) 88s 4. libopenmpi40:ppc64el Depends libucx0 88s 5. libucx0:ppc64el Depends libamdhip64-6 (>= 6.1.5) 88s 2. libamdhip64-6:ppc64el Depends libamd-comgr3 88s but none of the choices are installable: 88s [no choices] 88s autopkgtest [19:18:24]: test dipole: preparing testbed 88s crack FAIL badpkg 88s blame: lammps 88s 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. 88s 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: lammps but it is not going to be installed 89s E: Unable to satisfy dependencies. Reached two conflicting assignments: 89s 1. libamdhip64-6:ppc64el is selected for install because: 89s 1. satisfy:command-line:ppc64el=1 is selected for install 89s 2. satisfy:command-line:ppc64el Depends lammps 89s 3. lammps:ppc64el Depends libopenmpi40 (>= 5.0.8) 89s 4. libopenmpi40:ppc64el Depends libucx0 89s 5. libucx0:ppc64el Depends libamdhip64-6 (>= 6.1.5) 89s 2. libamdhip64-6:ppc64el Depends libamd-comgr3 89s but none of the choices are installable: 89s [no choices] 89s autopkgtest [19:18:25]: test ellipse: preparing testbed 89s dipole FAIL badpkg 89s blame: lammps 89s 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. 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: lammps but it is not going to be installed 89s E: Unable to satisfy dependencies. Reached two conflicting assignments: 89s 1. libamdhip64-6:ppc64el is selected for install because: 89s 1. satisfy:command-line:ppc64el=1 is selected for install 89s 2. satisfy:command-line:ppc64el Depends lammps 89s 3. lammps:ppc64el Depends libopenmpi40 (>= 5.0.8) 89s 4. libopenmpi40:ppc64el Depends libucx0 89s 5. libucx0:ppc64el Depends libamdhip64-6 (>= 6.1.5) 89s 2. libamdhip64-6:ppc64el Depends libamd-comgr3 89s but none of the choices are installable: 89s [no choices] 89s autopkgtest [19:18:25]: test flow: preparing testbed 89s ellipse FAIL badpkg 89s blame: lammps 89s 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. 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: lammps but it is not going to be installed 90s E: Unable to satisfy dependencies. Reached two conflicting assignments: 90s 1. libamdhip64-6:ppc64el is selected for install because: 90s 1. satisfy:command-line:ppc64el=1 is selected for install 90s 2. satisfy:command-line:ppc64el Depends lammps 90s 3. lammps:ppc64el Depends libopenmpi40 (>= 5.0.8) 90s 4. libopenmpi40:ppc64el Depends libucx0 90s 5. libucx0:ppc64el Depends libamdhip64-6 (>= 6.1.5) 90s 2. libamdhip64-6:ppc64el Depends libamd-comgr3 90s but none of the choices are installable: 90s [no choices] 90s autopkgtest [19:18:26]: test friction: preparing testbed 90s flow FAIL badpkg 90s blame: lammps 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 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: lammps but it is not going to be installed 90s E: Unable to satisfy dependencies. Reached two conflicting assignments: 90s 1. libamdhip64-6:ppc64el is selected for install because: 90s 1. satisfy:command-line:ppc64el=1 is selected for install 90s 2. satisfy:command-line:ppc64el Depends lammps 90s 3. lammps:ppc64el Depends libopenmpi40 (>= 5.0.8) 90s 4. libopenmpi40:ppc64el Depends libucx0 90s 5. libucx0:ppc64el Depends libamdhip64-6 (>= 6.1.5) 90s 2. libamdhip64-6:ppc64el Depends libamd-comgr3 90s but none of the choices are installable: 90s [no choices] 90s autopkgtest [19:18:26]: test hugo: preparing testbed 90s friction FAIL badpkg 90s blame: lammps 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 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: 91s satisfy:command-line : Depends: lammps but it is not going to be installed 91s E: Unable to satisfy dependencies. Reached two conflicting assignments: 91s 1. libamdhip64-6:ppc64el is selected for install because: 91s 1. satisfy:command-line:ppc64el=1 is selected for install 91s 2. satisfy:command-line:ppc64el Depends lammps 91s 3. lammps:ppc64el Depends libopenmpi40 (>= 5.0.8) 91s 4. libopenmpi40:ppc64el Depends libucx0 91s 5. libucx0:ppc64el Depends libamdhip64-6 (>= 6.1.5) 91s 2. libamdhip64-6:ppc64el Depends libamd-comgr3 91s but none of the choices are installable: 91s [no choices] 91s hugo FAIL badpkg 91s blame: lammps 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 autopkgtest [19:18:27]: test command1: preparing testbed 109s Creating nova instance adt-resolute-ppc64el-lammps-20260124-191656-juju-7f2275-prod-proposed-migration-environment-15-144f834d-7ff5-4e38-85fa-8214b25f6b6e from image adt/ubuntu-resolute-ppc64el-server-20260124.img (UUID a269ca64-3301-4299-8bab-2247218fc911)... 161s autopkgtest [19:19:37]: testbed dpkg architecture: ppc64el 161s autopkgtest [19:19:37]: testbed apt version: 3.1.13 162s autopkgtest [19:19:38]: @@@@@@@@@@@@@@@@@@@@ test bed setup 162s autopkgtest [19:19:38]: testbed release detected to be: resolute 163s autopkgtest [19:19:39]: updating testbed package index (apt update) 163s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease [124 kB] 163s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 163s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 163s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 163s Get:5 http://ftpmaster.internal/ubuntu resolute-proposed/universe Sources [976 kB] 164s Get:6 http://ftpmaster.internal/ubuntu resolute-proposed/main Sources [95.5 kB] 164s Get:7 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse Sources [24.3 kB] 164s Get:8 http://ftpmaster.internal/ubuntu resolute-proposed/restricted Sources [2820 B] 164s Get:9 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el Packages [107 kB] 164s Get:10 http://ftpmaster.internal/ubuntu resolute-proposed/universe ppc64el Packages [806 kB] 164s Get:11 http://ftpmaster.internal/ubuntu resolute-proposed/multiverse ppc64el Packages [9920 B] 164s Fetched 2145 kB in 1s (1987 kB/s) 165s Reading package lists... 166s Hit:1 http://ftpmaster.internal/ubuntu resolute-proposed InRelease 166s Hit:2 http://ftpmaster.internal/ubuntu resolute InRelease 166s Hit:3 http://ftpmaster.internal/ubuntu resolute-updates InRelease 166s Hit:4 http://ftpmaster.internal/ubuntu resolute-security InRelease 166s Reading package lists... 166s Reading package lists... 167s Building dependency tree... 167s Reading state information... 167s Calculating upgrade... 167s The following packages will be upgraded: 167s zlib1g 167s 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 167s Need to get 74.6 kB of archives. 167s After this operation, 0 B of additional disk space will be used. 167s Get:1 http://ftpmaster.internal/ubuntu resolute-proposed/main ppc64el zlib1g ppc64el 1:1.3.dfsg+really1.3.1-1ubuntu3 [74.6 kB] 167s dpkg-preconfigure: unable to re-open stdin: No such file or directory 167s Fetched 74.6 kB in 0s (3081 kB/s) 168s (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 ... 120851 files and directories currently installed.) 168s Preparing to unpack .../zlib1g_1%3a1.3.dfsg+really1.3.1-1ubuntu3_ppc64el.deb ... 169s Unpacking zlib1g:ppc64el (1:1.3.dfsg+really1.3.1-1ubuntu3) over (1:1.3.dfsg+really1.3.1-1ubuntu2) ... 169s Setting up zlib1g:ppc64el (1:1.3.dfsg+really1.3.1-1ubuntu3) ... 169s Processing triggers for libc-bin (2.42-2ubuntu4) ... 169s autopkgtest [19:19:45]: upgrading testbed (apt dist-upgrade and autopurge) 169s Reading package lists... 169s Building dependency tree... 169s Reading state information... 170s Calculating upgrade... 170s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 170s Reading package lists... 170s Building dependency tree... 170s Reading state information... 170s Solving dependencies... 170s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 173s Reading package lists... 173s Building dependency tree... 173s Reading state information... 173s Solving dependencies... 173s Some packages could not be installed. This may mean that you have 173s requested an impossible situation or if you are using the unstable 173s distribution that some required packages have not yet been created 173s or been moved out of Incoming. 173s The following information may help to resolve the situation: 173s 173s The following packages have unmet dependencies: 173s satisfy:command-line : Depends: python3-lammps but it is not going to be installed 173s E: Unable to satisfy dependencies. Reached two conflicting assignments: 173s 1. libamdhip64-6:ppc64el is selected for install because: 173s 1. satisfy:command-line:ppc64el=1 is selected for install 173s 2. satisfy:command-line:ppc64el Depends python3-lammps 173s 3. python3-lammps:ppc64el Depends liblammps-dev 173s 4. liblammps-dev:ppc64el Depends liblammps0t64 (= 20251210+dfsg-1) 173s 5. liblammps0t64:ppc64el Depends libopenmpi40 (>= 5.0.8) 173s 6. libopenmpi40:ppc64el Depends libucx0 173s 7. libucx0:ppc64el Depends libamdhip64-6 (>= 6.1.5) 173s 2. libamdhip64-6:ppc64el Depends libamd-comgr3 173s but none of the choices are installable: 173s [no choices] 173s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from resolute-proposed 174s Reading package lists... 174s Building dependency tree... 174s Reading state information... 174s Solving dependencies... 174s Some packages could not be installed. This may mean that you have 174s requested an impossible situation or if you are using the unstable 174s distribution that some required packages have not yet been created 174s or been moved out of Incoming. 174s The following information may help to resolve the situation: 174s 174s The following packages have unmet dependencies: 174s satisfy:command-line : Depends: python3-lammps but it is not going to be installed 174s E: Unable to satisfy dependencies. Reached two conflicting assignments: 174s 1. libamdhip64-6:ppc64el is selected for install because: 174s 1. satisfy:command-line:ppc64el=1 is selected for install 174s 2. satisfy:command-line:ppc64el Depends python3-lammps 174s 3. python3-lammps:ppc64el Depends liblammps-dev 174s 4. liblammps-dev:ppc64el Depends liblammps0t64 (= 20251210+dfsg-1) 174s 5. liblammps0t64:ppc64el Depends libopenmpi40 (>= 5.0.8) 174s 6. libopenmpi40:ppc64el Depends libucx0 174s 7. libucx0:ppc64el Depends libamdhip64-6 (>= 6.1.5) 174s 2. libamdhip64-6:ppc64el Depends libamd-comgr3 174s but none of the choices are installable: 174s [no choices] 174s command1 FAIL badpkg 174s blame: lammps 174s 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. 174s autopkgtest [19:19:50]: @@@@@@@@@@@@@@@@@@@@ summary 174s crack FAIL badpkg 174s blame: lammps 174s 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. 174s dipole FAIL badpkg 174s blame: lammps 174s 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. 174s ellipse FAIL badpkg 174s blame: lammps 174s 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. 174s flow FAIL badpkg 174s blame: lammps 174s 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. 174s friction FAIL badpkg 174s blame: lammps 174s 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. 174s hugo FAIL badpkg 174s blame: lammps 174s 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. 174s command1 FAIL badpkg 174s blame: lammps 174s 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.