touch-packages team mailing list archive

[Andrew Hayzen <1513860@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

The 'latest' version of a click package is used after a reboot, even
when a click with a lower version has been manually installed.

What happened:
1) Install a click packages for an existing application with a lower version than that of the preinstalled one
2) Launch the app and notice that the newly installed is launched
3) Reboot the device
4) Launch the app and notice that the preinstalled one is used due to it having a higher version

What was expected to happen:
At step 4) for the manually installed version of the click package to still be the selected one


This affects the developer experience for example, when working on the bgplaylists of the music-app the branch has a lower version (bzr rev) than trunk/what is in the store, and after installing new versions of media-hub to test the device must be restarted. So after each restart the developer must also remember to reinstall the click package.


$ apt-cache policy click
click:
  Installed: 0.4.40+15.04.20151006-0ubuntu1.1
  Candidate: 0.4.40+15.04.20151006-0ubuntu1.1
  Version table:
 *** 0.4.40+15.04.20151006-0ubuntu1.1 0
       1001 http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/ vivid/main armhf Packages
        100 /var/lib/dpkg/status
     0.4.38.5ubuntu0.2 0
        500 http://ports.ubuntu.com/ubuntu-ports/ vivid-updates/main armhf Packages
        500 http://ports.ubuntu.com/ubuntu-ports/ vivid-security/main armhf Packages
     0.4.38.5 0
        500 http://ports.ubuntu.com/ubuntu-ports/ vivid/main armhf Packages

** Affects: canonical-developer-experience
     Importance: Undecided
         Status: New

** Affects: click (Ubuntu)
     Importance: Undecided
         Status: Confirmed

** Also affects: canonical-developer-experience
   Importance: Undecided
       Status: New

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

Title:
  'Latest' version of a click package used after reboot

Status in Client Developer Experience:
  New
Status in click package in Ubuntu:
  Confirmed

Bug description:
  The 'latest' version of a click package is used after a reboot, even
  when a click with a lower version has been manually installed.

  What happened:
  1) Install a click packages for an existing application with a lower version than that of the preinstalled one
  2) Launch the app and notice that the newly installed is launched
  3) Reboot the device
  4) Launch the app and notice that the preinstalled one is used due to it having a higher version

  What was expected to happen:
  At step 4) for the manually installed version of the click package to still be the selected one

  
  This affects the developer experience for example, when working on the bgplaylists of the music-app the branch has a lower version (bzr rev) than trunk/what is in the store, and after installing new versions of media-hub to test the device must be restarted. So after each restart the developer must also remember to reinstall the click package.

  
  $ apt-cache policy click
  click:
    Installed: 0.4.40+15.04.20151006-0ubuntu1.1
    Candidate: 0.4.40+15.04.20151006-0ubuntu1.1
    Version table:
   *** 0.4.40+15.04.20151006-0ubuntu1.1 0
         1001 http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/ vivid/main armhf Packages
          100 /var/lib/dpkg/status
       0.4.38.5ubuntu0.2 0
          500 http://ports.ubuntu.com/ubuntu-ports/ vivid-updates/main armhf Packages
          500 http://ports.ubuntu.com/ubuntu-ports/ vivid-security/main armhf Packages
       0.4.38.5 0
          500 http://ports.ubuntu.com/ubuntu-ports/ vivid/main armhf Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1513860/+subscriptions