touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #95606
[Bug 1479001] Re: OTA update: lower user click not updated by custom tarball higher click
Correct me if I'm wrong, but this seems to be by design. Notice if you
go check for available updates, Ubuntu is listed as a separate update to
Facebook Photos. It seems reasonable to expect that if I update Ubuntu,
Facebook Photos will not be updated, since I didn't select it. Indeed,
after the OTA update, if you go back to view available updates, Facebook
Photos is still listed there, and if you update there, the user will now
be on 1.26.
Colin, are you suggesting adding another system hook, then? Aren't those
run on each boot? I can't think of a way to write a system hook that
will only force-ably update user-installed apps upon OTA and not on each
boot. Thoughts?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to click in Ubuntu.
https://bugs.launchpad.net/bugs/1479001
Title:
OTA update: lower user click not updated by custom tarball higher
click
Status in Canonical System Image:
Confirmed
Status in click package in Ubuntu:
Confirmed
Bug description:
A user in the field has OTA5 installed. But one click in OTA 5
(com.canonical.scopes.fbphotos_fbphotos 1.26) did not get updated and
is at the pre OTA5 version: 1.24.
Expectations: if OTA custom tarball has a higher version click package
than the user's, that higher click package is installed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479001/+subscriptions