adt fails to install unsigned clicks

[Nicholas Skaggs]

Adt run will fail when passing a click package in via --click if it's unsigned. This is often the case for developer generated click packages. These can be installed via passing --allow-untrusted swithc to the pkcon when installing on the device; can this be support via adt-run?

Cannot install /tmp/adt-run.AQ5C0m/com.ubuntu.filemanager.devel_0.3.latest_armhf.click: Signature verification error: debsig: Origin Signature check failed. This deb might not be signed.

adt-run [16:37:49]: ERROR: unexpected error: click install failed with status 1

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Martin Pitt (pitti)]

So supposedly we should call click install with --allow-unauthenticated.

[Launchpad Janitor (janitor)]

This bug was fixed in the package autopkgtest - 3.5.3

---------------
autopkgtest (3.5.3) unstable; urgency=medium

  * ssh-setup/adb: Use the new "phablet-config network" to save/restore wifi
    connections, which also works with non-root adb.
  * Give adt-run's tee processes some time to catch up between printing
    results and stderr, to avoid scrambled logs. (LP: #1373441)
  * Fix NullRunner.test_timeout_no_output for older Python versions.
  * tests/pyflakes: Skip test if pyflakes3 is not available (for backports).
  * Bump Standards version to 3.9.6 (no changes necessary).
  * NullRunner.test_timeout_no_output: Slightly relax time bound to make
    failures less likely on loaded/slow machines.
  * Install clicks with --allow-unauthenticated to support local developer
    generated packages. (LP: #1372640)

 -- Martin Pitt <email address hidden> Sun, 28 Sep 2014 12:16:16 +0200