[Expired for click (Ubuntu) because there has been no activity for 60
days.]
** Changed in: click (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1513860
T
** Changed in: canonical-developer-experience
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1513860
Title:
'Latest' version of a click package used after reboot
In QA we use 1 (uninstall the store version) and this workaround works
fine so far.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1513860
Title:
'Latest' version of a click package used after reboot
@Pat
1) I haven't tried what happens in this case
2) This is not possible for the music-app currently as we have exceptions in
the platform (eg app lifecycle)
3) Is usually what I end up doing (once I've realised I've been flipped to the
'latest' version)
4) If I can't restart/update this is inc
@zoltan can you read this over and think about how to address it
** Changed in: canonical-developer-experience
Status: New => Confirmed
** Changed in: canonical-developer-experience
Assignee: (unassigned) => Zoltan Balogh (bzoltan)
--
You received this bug notification because you a
@Andrew at the risk of stating the obvious are none of the following practical?
1) uninstall the store version
2) name your test app something else
3) version the test app to be newer
4) don't get updates while actively developing
** No longer affects: canonical-devices-system-image
--
You recei
Possible real fix as described in bug #1479001
This change has the side effect (a regression) of making it impossible
to sideload an older version of a click, since the system hooks are run
on boot: the older versions will be unregistered upon the next boot. We
believe this is fixable by comparing
So I have a few scenarios this has happened, in the music app and other
core apps the bzr revision number is used as the sub version, for
example {major}.{minor}.{bzrrevno}.
The first example is from the music-app, the store currently is of the
version 2.2.910 but I'm working on the music-app back
@andrew why would you expect a lower version to ever run?
Is it not easy enough to bump the test version to something later?
This is exactly due to the change cited in the earlier comment.
** Changed in: canonical-devices-system-image
Status: New => Incomplete
** Changed in: click (Ubuntu)
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1513860
Title:
'Latest' version of a click package used afte
This is almost certainly fallout from bug 1479001.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1513860
Title:
'Latest' version of a click package used after reboot
To manage notifications about t
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: click (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1513860
Title:
'Lat
12 matches
Mail list logo
