touch-packages team mailing list archive

[Pat McGowan <pat.mcgowan@xxxxxxxxxxxxx>]

Based on the doc

When click is asked to list the set of packages for a given user, it
walks its way down the list of databases from top (default) to bottom
(core). For each database, it checks registrations for that user,
followed by registrations for @all. It takes the first registration for
any given package name that it finds.

This does not mention selecting the most recent version which could be
seen as a feature if the user wants to use an earlier version. However
since installing older packages is not supported from the UI I would
argue we should always default to the latest version and not the first
match found.

This seems a fundamental incompatibility between image updates and click
installs.

FWIW uninstalling the user version (via the UI) is all that is needed to
enable the updated version. After the uninstall the store UI incorrectly
shows the option to install, but returning to the list refreshes with
the correct installed state.

-- 
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