** Description changed: OTA 10 links created by puritine-conf upstart are not updated to ContainersConfig.json and the rootfs when puritine click is installed not through custom tarball. Since the links are not updated, libertine does not try to use the new puritine container (it still points to the old one). So after updated puritine click install: - phablet@ubuntu-phablet:~/.local/share/libertine$ ls -l ContainersConfig.json-origwq + phablet@ubuntu-phablet:~/.local/share/libertine$ ls -l ContainersConfig.json lrwxrwxrwx 1 phablet phablet 100 Apr 28 12:37 ContainersConfig.json-> /custom/click/.click/users/@all/com.ubuntu.puritine/libertine-config/libertine/ContainersConfig.json But that should be: lrwxrwxrwx 1 phablet phablet 111 Apr 28 16:07 ContainersConfig.json -> /opt/click.ubuntu.com/.click/users/phablet/com.ubuntu.puritine/libertine-config/libertine/ContainersConfig.json And: phablet@ubuntu-phablet:~/.cache/libertine-container/puritine$ ls -l rootfs-orig lrwxrwxrwx 1 phablet phablet 102 Apr 28 12:37 rootfs-orig -> /custom/click/.click/users/@all/com.ubuntu.puritine/libertine-data/libertine-container/puritine/rootfs But that should be: lrwxrwxrwx 1 phablet phablet 113 Apr 28 15:46 rootfs -> /opt/click.ubuntu.com/.click/users/phablet/com.ubuntu.puritine/libertine-data/libertine-container/puritine/rootfs VERSION INFO - phablet@ubuntu-phablet:~$ dpkg -S /usr/share/upstart/sessions/puritine-click.conf + phablet@ubuntu-phablet:~$ dpkg -S /usr/share/upstart/sessions/puritine-click.conf libertine-demo: /usr/share/upstart/sessions/puritine-click.conf phablet@ubuntu-phablet:~$ apt-cache policy libertine-demo libertine-demo: - Installed: 0.99.12+15.04.20160321-0ubuntu1 + Installed: 0.99.12+15.04.20160321-0ubuntu1
** Description changed: OTA 10 links created by puritine-conf upstart are not updated to ContainersConfig.json and the rootfs when puritine click is installed not through custom tarball. Since the links are not updated, libertine does not try to use the new puritine container (it still points to the old one). So after updated puritine click install: phablet@ubuntu-phablet:~/.local/share/libertine$ ls -l ContainersConfig.json lrwxrwxrwx 1 phablet phablet 100 Apr 28 12:37 ContainersConfig.json-> /custom/click/.click/users/@all/com.ubuntu.puritine/libertine-config/libertine/ContainersConfig.json But that should be: lrwxrwxrwx 1 phablet phablet 111 Apr 28 16:07 ContainersConfig.json -> /opt/click.ubuntu.com/.click/users/phablet/com.ubuntu.puritine/libertine-config/libertine/ContainersConfig.json And: - phablet@ubuntu-phablet:~/.cache/libertine-container/puritine$ ls -l rootfs-orig + phablet@ubuntu-phablet:~/.cache/libertine-container/puritine$ ls -l rootfs lrwxrwxrwx 1 phablet phablet 102 Apr 28 12:37 rootfs-orig -> /custom/click/.click/users/@all/com.ubuntu.puritine/libertine-data/libertine-container/puritine/rootfs But that should be: lrwxrwxrwx 1 phablet phablet 113 Apr 28 15:46 rootfs -> /opt/click.ubuntu.com/.click/users/phablet/com.ubuntu.puritine/libertine-data/libertine-container/puritine/rootfs VERSION INFO phablet@ubuntu-phablet:~$ dpkg -S /usr/share/upstart/sessions/puritine-click.conf libertine-demo: /usr/share/upstart/sessions/puritine-click.conf phablet@ubuntu-phablet:~$ apt-cache policy libertine-demo libertine-demo: Installed: 0.99.12+15.04.20160321-0ubuntu1 ** Description changed: OTA 10 links created by puritine-conf upstart are not updated to ContainersConfig.json and the rootfs when puritine click is installed not through custom tarball. Since the links are not updated, libertine does not try to use the new puritine container (it still points to the old one). So after updated puritine click install: phablet@ubuntu-phablet:~/.local/share/libertine$ ls -l ContainersConfig.json lrwxrwxrwx 1 phablet phablet 100 Apr 28 12:37 ContainersConfig.json-> /custom/click/.click/users/@all/com.ubuntu.puritine/libertine-config/libertine/ContainersConfig.json But that should be: lrwxrwxrwx 1 phablet phablet 111 Apr 28 16:07 ContainersConfig.json -> /opt/click.ubuntu.com/.click/users/phablet/com.ubuntu.puritine/libertine-config/libertine/ContainersConfig.json And: phablet@ubuntu-phablet:~/.cache/libertine-container/puritine$ ls -l rootfs - lrwxrwxrwx 1 phablet phablet 102 Apr 28 12:37 rootfs-orig -> /custom/click/.click/users/@all/com.ubuntu.puritine/libertine-data/libertine-container/puritine/rootfs + lrwxrwxrwx 1 phablet phablet 102 Apr 28 12:37 rootfs -> /custom/click/.click/users/@all/com.ubuntu.puritine/libertine-data/libertine-container/puritine/rootfs But that should be: lrwxrwxrwx 1 phablet phablet 113 Apr 28 15:46 rootfs -> /opt/click.ubuntu.com/.click/users/phablet/com.ubuntu.puritine/libertine-data/libertine-container/puritine/rootfs VERSION INFO phablet@ubuntu-phablet:~$ dpkg -S /usr/share/upstart/sessions/puritine-click.conf libertine-demo: /usr/share/upstart/sessions/puritine-click.conf phablet@ubuntu-phablet:~$ apt-cache policy libertine-demo libertine-demo: Installed: 0.99.12+15.04.20160321-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576406 Title: puritine click not installed by custom tarball does not work To manage notifications about this bug go to: https://bugs.launchpad.net/libertine/+bug/1576406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
