0s autopkgtest [16:45:07]: starting date and time: 2024-12-04 16:45:07+0000 0s autopkgtest [16:45:07]: git checkout: 48af33f0 Fix --add-apt-source=ppa for focal 0s autopkgtest [16:45:07]: host juju-7f2275-prod-proposed-migration-environment-2; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.uk8wxz5m/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:vtk9,src:openmpi --apt-upgrade lammps --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 '--env=ADT_TEST_TRIGGERS=vtk9/9.3.0+dfsg1-1.1build2 openmpi/5.0.6-3' -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest-ppc64el --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-2@bos03-ppc64el-27.secgroup --name adt-plucky-ppc64el-lammps-20241204-161452-juju-7f2275-prod-proposed-migration-environment-2-647c58ac-19b9-41d4-a57a-165c3355bc7c --image adt/ubuntu-plucky-ppc64el-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-2 --net-id=net_prod-proposed-migration-ppc64el -e TERM=linux -e ''"'"'http_proxy=http://squid.internal:3128'"'"'' -e ''"'"'https_proxy=http://squid.internal:3128'"'"'' -e ''"'"'no_proxy=127.0.0.1,127.0.1.1,login.ubuntu.com,localhost,localdomain,novalocal,internal,archive.ubuntu.com,ports.ubuntu.com,security.ubuntu.com,ddebs.ubuntu.com,changelogs.ubuntu.com,keyserver.ubuntu.com,launchpadlibrarian.net,launchpadcontent.net,launchpad.net,10.24.0.0/24,keystone.ps5.canonical.com,objectstorage.prodstack5.canonical.com'"'"'' --mirror=http://ftpmaster.internal/ubuntu/ 70s autopkgtest [16:46:17]: testbed dpkg architecture: ppc64el 70s autopkgtest [16:46:17]: testbed apt version: 2.9.16 70s autopkgtest [16:46:17]: @@@@@@@@@@@@@@@@@@@@ test bed setup 71s autopkgtest [16:46:18]: testbed release detected to be: None 71s autopkgtest [16:46:18]: updating testbed package index (apt update) 72s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [73.9 kB] 72s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 72s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 72s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 72s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [14.2 kB] 72s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [63.2 kB] 72s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [9708 B] 72s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [764 kB] 72s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main ppc64el Packages [122 kB] 72s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted ppc64el Packages [928 B] 72s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe ppc64el Packages [623 kB] 72s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse ppc64el Packages [10.4 kB] 73s Fetched 1681 kB in 1s (1728 kB/s) 73s Reading package lists... 74s Reading package lists... 74s Building dependency tree... 74s Reading state information... 74s Calculating upgrade... 74s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 74s Reading package lists... 75s Building dependency tree... 75s Reading state information... 75s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 75s autopkgtest [16:46:22]: upgrading testbed (apt dist-upgrade and autopurge) 75s Reading package lists... 75s Building dependency tree... 75s Reading state information... 75s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 76s Starting 2 pkgProblemResolver with broken count: 0 76s Done 76s Entering ResolveByKeep 76s 76s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 76s Reading package lists... 77s Building dependency tree... 77s Reading state information... 77s Starting pkgProblemResolver with broken count: 0 77s Starting 2 pkgProblemResolver with broken count: 0 77s Done 77s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 80s autopkgtest [16:46:27]: testbed running kernel: Linux 6.11.0-8-generic #8-Ubuntu SMP Mon Sep 16 13:49:23 UTC 2024 80s autopkgtest [16:46:27]: @@@@@@@@@@@@@@@@@@@@ apt-source lammps 95s Get:1 http://ftpmaster.internal/ubuntu plucky/universe lammps 20240207+dfsg-1.1build5 (dsc) [2932 B] 95s Get:2 http://ftpmaster.internal/ubuntu plucky/universe lammps 20240207+dfsg-1.1build5 (tar) [153 MB] 95s Get:3 http://ftpmaster.internal/ubuntu plucky/universe lammps 20240207+dfsg-1.1build5 (diff) [17.2 kB] 95s gpgv: Signature made Tue Jul 30 21:05:03 2024 UTC 95s gpgv: using RSA key 883FEC247A03BE63B70FD5F920FB053CAF9559CF 95s gpgv: issuer "eeickmeyer@ubuntu.com" 95s gpgv: Can't check signature: No public key 95s dpkg-source: warning: cannot verify inline signature for ./lammps_20240207+dfsg-1.1build5.dsc: no acceptable signature found 103s autopkgtest [16:46:50]: testing package lammps version 20240207+dfsg-1.1build5 104s autopkgtest [16:46:51]: build not needed 126s autopkgtest [16:47:13]: test crack: preparing testbed 126s Reading package lists... 126s Building dependency tree... 126s Reading state information... 127s Starting pkgProblemResolver with broken count: 1 127s Starting 2 pkgProblemResolver with broken count: 1 127s Investigating (0) libopenmpi40:ppc64el < none -> 5.0.6-3 @un puN Ib > 127s Broken libopenmpi40:ppc64el Breaks on libopenmpi3:ppc64el < none @un H > (< 5.0.6-3) 127s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 127s Considering libopenmpi3t64:ppc64el 1 as a solution to libopenmpi40:ppc64el 1 127s Re-Instated libopenmpi3t64:ppc64el 127s Broken libopenmpi40:ppc64el Breaks on libopenmpi3t64:ppc64el < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 127s Considering libopenmpi3t64:ppc64el 1 as a solution to libopenmpi40:ppc64el 1 127s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 127s Done 127s Some packages could not be installed. This may mean that you have 127s requested an impossible situation or if you are using the unstable 127s distribution that some required packages have not yet been created 127s or been moved out of Incoming. 127s The following information may help to resolve the situation: 127s 127s The following packages have unmet dependencies: 127s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 127s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 127s E: Unable to correct problems, you have held broken packages. 127s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from plucky-proposed 127s Reading package lists... 127s Building dependency tree... 127s Reading state information... 128s Starting pkgProblemResolver with broken count: 1 128s Starting 2 pkgProblemResolver with broken count: 1 128s Investigating (0) libopenmpi40:ppc64el < none -> 5.0.6-3 @un puN Ib > 128s Broken libopenmpi40:ppc64el Breaks on libopenmpi3:ppc64el < none @un H > (< 5.0.6-3) 128s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 128s Considering libopenmpi3t64:ppc64el 0 as a solution to libopenmpi40:ppc64el 2 128s Broken libopenmpi40:ppc64el Breaks on libopenmpi3t64:ppc64el < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 128s Considering libopenmpi3t64:ppc64el 0 as a solution to libopenmpi40:ppc64el 2 128s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 128s Done 128s Some packages could not be installed. This may mean that you have 128s requested an impossible situation or if you are using the unstable 128s distribution that some required packages have not yet been created 128s or been moved out of Incoming. 128s The following information may help to resolve the situation: 128s 128s The following packages have unmet dependencies: 128s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 128s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 128s E: Unable to correct problems, you have held broken packages. 128s autopkgtest [16:47:15]: test dipole: preparing testbed 128s crack FAIL badpkg 128s blame: lammps 128s 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. 128s Reading package lists... 128s Building dependency tree... 128s Reading state information... 129s Starting pkgProblemResolver with broken count: 1 129s Starting 2 pkgProblemResolver with broken count: 1 129s Investigating (0) libopenmpi40:ppc64el < none -> 5.0.6-3 @un puN Ib > 129s Broken libopenmpi40:ppc64el Breaks on libopenmpi3:ppc64el < none @un H > (< 5.0.6-3) 129s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 129s Considering libopenmpi3t64:ppc64el 0 as a solution to libopenmpi40:ppc64el 2 129s Broken libopenmpi40:ppc64el Breaks on libopenmpi3t64:ppc64el < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 129s Considering libopenmpi3t64:ppc64el 0 as a solution to libopenmpi40:ppc64el 2 129s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 129s Done 129s Some packages could not be installed. This may mean that you have 129s requested an impossible situation or if you are using the unstable 129s distribution that some required packages have not yet been created 129s or been moved out of Incoming. 129s The following information may help to resolve the situation: 129s 129s The following packages have unmet dependencies: 129s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 129s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 129s E: Unable to correct problems, you have held broken packages. 129s autopkgtest [16:47:16]: test ellipse: preparing testbed 129s dipole FAIL badpkg 129s blame: lammps 129s 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. 129s Reading package lists... 129s Building dependency tree... 129s Reading state information... 130s Starting pkgProblemResolver with broken count: 1 130s Starting 2 pkgProblemResolver with broken count: 1 130s Investigating (0) libopenmpi40:ppc64el < none -> 5.0.6-3 @un puN Ib > 130s Broken libopenmpi40:ppc64el Breaks on libopenmpi3:ppc64el < none @un H > (< 5.0.6-3) 130s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 130s Considering libopenmpi3t64:ppc64el 0 as a solution to libopenmpi40:ppc64el 2 130s Broken libopenmpi40:ppc64el Breaks on libopenmpi3t64:ppc64el < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 130s Considering libopenmpi3t64:ppc64el 0 as a solution to libopenmpi40:ppc64el 2 130s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 130s Done 130s Some packages could not be installed. This may mean that you have 130s requested an impossible situation or if you are using the unstable 130s distribution that some required packages have not yet been created 130s or been moved out of Incoming. 130s The following information may help to resolve the situation: 130s 130s The following packages have unmet dependencies: 130s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 130s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 130s E: Unable to correct problems, you have held broken packages. 130s ellipse FAIL badpkg 130s blame: lammps 130s 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. 130s autopkgtest [16:47:17]: test flow: preparing testbed 130s Reading package lists... 130s Building dependency tree... 130s Reading state information... 130s Starting pkgProblemResolver with broken count: 1 130s Starting 2 pkgProblemResolver with broken count: 1 130s Investigating (0) libopenmpi40:ppc64el < none -> 5.0.6-3 @un puN Ib > 130s Broken libopenmpi40:ppc64el Breaks on libopenmpi3:ppc64el < none @un H > (< 5.0.6-3) 130s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 130s Considering libopenmpi3t64:ppc64el 0 as a solution to libopenmpi40:ppc64el 2 130s Broken libopenmpi40:ppc64el Breaks on libopenmpi3t64:ppc64el < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 130s Considering libopenmpi3t64:ppc64el 0 as a solution to libopenmpi40:ppc64el 2 130s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 130s Done 130s Some packages could not be installed. This may mean that you have 130s requested an impossible situation or if you are using the unstable 130s distribution that some required packages have not yet been created 130s or been moved out of Incoming. 130s The following information may help to resolve the situation: 130s 130s The following packages have unmet dependencies: 130s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 130s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 130s E: Unable to correct problems, you have held broken packages. 131s flow FAIL badpkg 131s blame: lammps 131s 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. 131s autopkgtest [16:47:18]: test friction: preparing testbed 131s Reading package lists... 131s Building dependency tree... 131s Reading state information... 131s Starting pkgProblemResolver with broken count: 1 131s Starting 2 pkgProblemResolver with broken count: 1 131s Investigating (0) libopenmpi40:ppc64el < none -> 5.0.6-3 @un puN Ib > 131s Broken libopenmpi40:ppc64el Breaks on libopenmpi3:ppc64el < none @un H > (< 5.0.6-3) 131s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 131s Considering libopenmpi3t64:ppc64el 0 as a solution to libopenmpi40:ppc64el 2 131s Broken libopenmpi40:ppc64el Breaks on libopenmpi3t64:ppc64el < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 131s Considering libopenmpi3t64:ppc64el 0 as a solution to libopenmpi40:ppc64el 2 131s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 131s Done 131s Some packages could not be installed. This may mean that you have 131s requested an impossible situation or if you are using the unstable 131s distribution that some required packages have not yet been created 131s or been moved out of Incoming. 131s The following information may help to resolve the situation: 131s 131s The following packages have unmet dependencies: 131s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 131s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 131s E: Unable to correct problems, you have held broken packages. 131s friction FAIL badpkg 131s blame: lammps 131s 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. 131s autopkgtest [16:47:18]: test hugo: preparing testbed 132s Reading package lists... 132s Building dependency tree... 132s Reading state information... 132s Starting pkgProblemResolver with broken count: 1 132s Starting 2 pkgProblemResolver with broken count: 1 132s Investigating (0) libopenmpi40:ppc64el < none -> 5.0.6-3 @un puN Ib > 132s Broken libopenmpi40:ppc64el Breaks on libopenmpi3:ppc64el < none @un H > (< 5.0.6-3) 132s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 132s Considering libopenmpi3t64:ppc64el 0 as a solution to libopenmpi40:ppc64el 2 132s Broken libopenmpi40:ppc64el Breaks on libopenmpi3t64:ppc64el < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 132s Considering libopenmpi3t64:ppc64el 0 as a solution to libopenmpi40:ppc64el 2 132s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 132s Done 132s Some packages could not be installed. This may mean that you have 132s requested an impossible situation or if you are using the unstable 132s distribution that some required packages have not yet been created 132s or been moved out of Incoming. 132s The following information may help to resolve the situation: 132s 132s The following packages have unmet dependencies: 132s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 132s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 132s E: Unable to correct problems, you have held broken packages. 132s hugo FAIL badpkg 132s blame: lammps 132s 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. 132s autopkgtest [16:47:19]: test command1: preparing testbed 196s autopkgtest [16:48:23]: testbed dpkg architecture: ppc64el 196s autopkgtest [16:48:23]: testbed apt version: 2.9.16 196s autopkgtest [16:48:23]: @@@@@@@@@@@@@@@@@@@@ test bed setup 196s autopkgtest [16:48:23]: testbed release detected to be: plucky 197s autopkgtest [16:48:24]: updating testbed package index (apt update) 198s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [73.9 kB] 198s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 198s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 198s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 198s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [764 kB] 198s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [63.2 kB] 198s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [14.2 kB] 198s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [9708 B] 198s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main ppc64el Packages [122 kB] 198s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted ppc64el Packages [928 B] 198s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe ppc64el Packages [623 kB] 198s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse ppc64el Packages [10.4 kB] 199s Fetched 1681 kB in 1s (1673 kB/s) 200s Reading package lists... 200s Reading package lists... 200s Building dependency tree... 200s Reading state information... 201s Calculating upgrade... 201s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 201s Reading package lists... 201s Building dependency tree... 201s Reading state information... 201s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 201s autopkgtest [16:48:28]: upgrading testbed (apt dist-upgrade and autopurge) 201s Reading package lists... 202s Building dependency tree... 202s Reading state information... 202s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 202s Starting 2 pkgProblemResolver with broken count: 0 202s Done 203s Entering ResolveByKeep 203s 203s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 203s Reading package lists... 203s Building dependency tree... 203s Reading state information... 204s Starting pkgProblemResolver with broken count: 0 204s Starting 2 pkgProblemResolver with broken count: 0 204s Done 204s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 207s Reading package lists... 207s Building dependency tree... 207s Reading state information... 207s Starting pkgProblemResolver with broken count: 1 208s Starting 2 pkgProblemResolver with broken count: 1 208s Investigating (0) libopenmpi40:ppc64el < none -> 5.0.6-3 @un puN Ib > 208s Broken libopenmpi40:ppc64el Breaks on libopenmpi3:ppc64el < none @un H > (< 5.0.6-3) 208s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 208s Considering libopenmpi3t64:ppc64el 0 as a solution to libopenmpi40:ppc64el 3 208s Broken libopenmpi40:ppc64el Breaks on libopenmpi3t64:ppc64el < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 208s Considering libopenmpi3t64:ppc64el 0 as a solution to libopenmpi40:ppc64el 3 208s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 208s Done 208s Some packages could not be installed. This may mean that you have 208s requested an impossible situation or if you are using the unstable 208s distribution that some required packages have not yet been created 208s or been moved out of Incoming. 208s The following information may help to resolve the situation: 208s 208s The following packages have unmet dependencies: 208s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 208s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 208s E: Unable to correct problems, you have held broken packages. 208s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from plucky-proposed 208s Reading package lists... 208s Building dependency tree... 208s Reading state information... 209s Starting pkgProblemResolver with broken count: 1 209s Starting 2 pkgProblemResolver with broken count: 1 209s Investigating (0) libopenmpi40:ppc64el < none -> 5.0.6-3 @un puN Ib > 209s Broken libopenmpi40:ppc64el Breaks on libopenmpi3:ppc64el < none @un H > (< 5.0.6-3) 209s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 209s Considering libopenmpi3t64:ppc64el -1 as a solution to libopenmpi40:ppc64el 4 209s Broken libopenmpi40:ppc64el Breaks on libopenmpi3t64:ppc64el < none -> 5.0.5-6 @un puN > (< 5.0.6-3) 209s Considering libopenmpi3t64:ppc64el -1 as a solution to libopenmpi40:ppc64el 4 209s Conflicts//Breaks against version 4.1.6-13.3ubuntu2 for libopenmpi3t64 but that is not InstVer, ignoring 209s Done 209s Some packages could not be installed. This may mean that you have 209s requested an impossible situation or if you are using the unstable 209s distribution that some required packages have not yet been created 209s or been moved out of Incoming. 209s The following information may help to resolve the situation: 209s 209s The following packages have unmet dependencies: 209s libopenmpi40 : Breaks: libopenmpi3 (< 5.0.6-3) 209s Breaks: libopenmpi3t64 (< 5.0.6-3) but 5.0.5-6 is to be installed 209s E: Unable to correct problems, you have held broken packages. 209s autopkgtest [16:48:36]: @@@@@@@@@@@@@@@@@@@@ summary 209s crack FAIL badpkg 209s blame: lammps 209s 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. 209s dipole FAIL badpkg 209s blame: lammps 209s 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. 209s ellipse FAIL badpkg 209s blame: lammps 209s 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. 209s flow FAIL badpkg 209s blame: lammps 209s 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. 209s friction FAIL badpkg 209s blame: lammps 209s 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. 209s hugo FAIL badpkg 209s blame: lammps 209s 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. 209s command1 FAIL badpkg 209s blame: lammps 209s 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. 209s command1 FAIL badpkg 209s blame: lammps 209s 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. 220s nova [W] Using flock in prodstack6-ppc64el 220s Creating nova instance adt-plucky-ppc64el-lammps-20241204-161452-juju-7f2275-prod-proposed-migration-environment-2-647c58ac-19b9-41d4-a57a-165c3355bc7c from image adt/ubuntu-plucky-ppc64el-server-20241204.img (UUID e9236e35-df68-4c3b-8528-5ccc09308d42)... 220s nova [W] Using flock in prodstack6-ppc64el 220s Creating nova instance adt-plucky-ppc64el-lammps-20241204-161452-juju-7f2275-prod-proposed-migration-environment-2-647c58ac-19b9-41d4-a57a-165c3355bc7c from image adt/ubuntu-plucky-ppc64el-server-20241204.img (UUID e9236e35-df68-4c3b-8528-5ccc09308d42)...