Hi, we encountered this error during installations of the SecureDrop application, which uses Ubuntu 14.0.4.5 for its server-side OS. We put out an advisory which you can find here: https://securedrop.org/news/advisory-server-installation-failure-uefi-boot-mode/ -but basically we're seeing the same error as described above.
I just tried an install using the new shim-signed package as follows:
1) installed Ubuntu 14.04.5 to servers
2) updated /etc/apt/sources.list to include the trusty-proposed repository
3) ran sudo apt-get update
Then I proceeded with the SecureDrop install, which failed at the same task and with the same error as before:
---
fatal: [app]: FAILED! => {"cache_update_time": 1540315459, "cache_updated": false, "changed": false, "msg": "'/usr/bin/apt-get -y -o \"Dpkg::Options::=--force-confdef\" -o \"Dpkg::Options::=--force-confold\" install 'securedrop-keyring'' failed: E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).\n", "rc": 100, "stderr": "E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).\n", "stderr_lines": ["E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution)."], "stdout": "Reading package lists...\nBuilding dependency tree...\nReading state information...\nYou might want to run 'apt-get -f install' to correct these:\nThe following packages have unmet dependencies:\n shim-signed : Depends: shim (= 13-0ubuntu2) but it is not going to be installed\n", "stdout_lines": ["Reading package lists...", "Building dependency tree...", "Reading state information...", "You might want to run 'apt-get -f install' to correct these:", "The following packages have unmet dependencies:", " shim-signed : Depends: shim (= 13-0ubuntu2) but it is not going to be installed"]}
---
This is Ansible output - the actual apt-get command that failed is:
Hi, we encountered this error during installations of the SecureDrop application, which uses Ubuntu 14.0.4.5 for its server-side OS. We put out an advisory which you can find here: https:/ /securedrop. org/news/ advisory- server- installation- failure- uefi-boot- mode/ -but basically we're seeing the same error as described above.
I just tried an install using the new shim-signed package as follows: sources. list to include the trusty-proposed repository
1) installed Ubuntu 14.04.5 to servers
2) updated /etc/apt/
3) ran sudo apt-get update
Then I proceeded with the SecureDrop install, which failed at the same task and with the same error as before:
--- update_ time": 1540315459, "cache_updated": false, "changed": false, "msg": "'/usr/bin/apt-get -y -o \"Dpkg: :Options: :=--force- confdef\ " -o \"Dpkg: :Options: :=--force- confold\ " install 'securedrop- keyring' ' failed: E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).\n", "rc": 100, "stderr": "E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).\n", "stderr_lines": ["E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution)."], "stdout": "Reading package lists...\nBuilding dependency tree...\nReading state information...\nYou might want to run 'apt-get -f install' to correct these:\nThe following packages have unmet dependencies:\n shim-signed : Depends: shim (= 13-0ubuntu2) but it is not going to be installed\n", "stdout_lines": ["Reading package lists...", "Building dependency tree...", "Reading state information...", "You might want to run 'apt-get -f install' to correct these:", "The following packages have unmet dependencies:", " shim-signed : Depends: shim (= 13-0ubuntu2) but it is not going to be installed"]}
fatal: [app]: FAILED! => {"cache_
---
This is Ansible output - the actual apt-get command that failed is:
apt-get -y -o "Dpkg:: Options: :=--force- confdef" -o "Dpkg:: Options: :=--force- confold" install 'securedrop- keyring'
I also tried installing shim-signed directly on the server with the command: trusty- proposed
sudo apt-get install shinm-signed/
This failed with a similar error about the shim package being an unmet dependency.
Unless I'm setting up the -proposed repo incorrectly, I don't believe adding dpkg as a predependency fixes this bug.