ubuntu-phone team mailing list archive

[Alan Pope <alan.pope@xxxxxxxxxxxxx>]

On Sat, Aug 23, 2014 at 8:12 AM, Victor Thompson
<victor.thompson@xxxxxxxxx> wrote:
> As of image 205 or maybe 204, I have been unable to install click packages
> via "click-buddy" while testing with the device in developer mode. I was
> under the impression from the framework discussion this week that if you are
> stripping your security via developer mode that you should be able to
> install stuff? This is an example of what I see in my terminal while running
> click-buddy from my desktop:
>
> Fatal error: /tmp/com.ubuntu.music_1.3.596_all.click failed to install.
> Cannot install /tmp/com.ubuntu.music_1.3.596_all.click: Signature
> verification error: debsig: Origin Signature check failed. This deb might
> not be signed.
>

Confirmed. I grabbed a click and manually provisioned with adb push
and pkcon install-local under phablet-shell.

Pretty sure I installed a click last night when on #204, so this came
in #205. Looking at the changelog we got a new version of the click
tools.

http://people.canonical.com/~ogra/touch-image-stats/205.changes

Which looks to have fixed bug http://pad.lv/1330770 according to the
changelog at https://launchpadlibrarian.net/182967306/click_0.4.31.2_amd64.changes
which might be the cause of this change in behaviour.

Two options in the short term:-

1. Downgrade to #204.

ubuntu-device-flash --channel=devel-proposed --revision=204

2. Edit click-buddy to allow unsigned packages to install

Ninja edit this line in /usr/bin/click-buddy

        adb $ADBOPTS shell sudo -u $DEVICE_USER bash -ic "pkcon
install-local /tmp/$click"

to this:-

        adb $ADBOPTS shell click install --user=$DEVICE_USER
--allow-unauthenticated /tmp/$click

Which worked for me. YMMV. Probably needs a bug filing against
phablet-tools to fix click-buddy.

Cheers,
-- 
Alan Pope
Technical Project Manager

Canonical - Product Strategy
+44 (0) 7973 620 164
alan.pope@xxxxxxxxxxxxx
http://ubuntu.com/