BTW another undesirable symptom is that a user can uninstall an app only
to see it remain in their app scope
--
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:
I am more concerned with changing intended functionality, perhaps for
multiuser systems although its not clear that will ever be a real
requirement for click.
It seems fixing the logic that is unnecessarily updating the timestamps
should be done
Should this behavior only be enabled on single
We think we have a way forward for fixing this, but want to get some
consensus before continuing.
First of all, as Colin mentioned, in order to make sure clicks in /opt
are updated when OTA updates install newer versions in /custom, `click
hook run-system` needs to be updated to compare those
While this is a slightly annoying bug, it is not new, nor a regression;
and requires a somewhat intimate knowledge of the system, to even
realize it is being hit. There also appear to be a couple of workarounds
for this issue. As such, I'd suggest possibly reducing the priority of
this from
I agree that this should not be Critical: after an OTA the user will
just see more updates available for the installed apps and scopes, they
will not look out of place and the workaround is to just install those.
** Changed in: click (Ubuntu)
Importance: Critical = Medium
** Changed in: click
** Changed in: canonical-devices-system-image
Milestone: ww34-2015 = ww40-2015
--
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
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
** Tags added: lt-category-visible
--
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
I'd rather strongly recommend against changing the fundamental database
design; I think that if you take that road then you will find yourself
playing whack-a-mole with conflicting requirements. Instead, my
suggestion would be to arrange for click hook run-system-hooks to
garbage-collect user
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
I reproduced it by installing a dummy 1.24 version which goes into /opt/click
After an update to ota5 /custom/click contained the latest 1.26 version but the
system still reported 1.24 as the active version
click pkgdir com.canonical.scopes.fbphotos
So, when I flash ota4 then use system settings to update to ota5,
fbphotos is 1.26 (correct from the custom tarball).
However, this user had fbphotos 1.24 after OTA update..
So yeah, I guess they installed 1.24 from store (which perhaps should
not be allowed since it is a lower version than 1.26
12 matches
Mail list logo
