On Sep 22, 2015, at 05:38 AM, Matthias Apitz wrote: >I do not know what "si 2.5" or "si 3.0" is; I only can see what I have >posted in the original report: version: Ubuntu 15.04-armhf >(20150825-170536), can you please explain here (or off-list) what those >"si values" are?
Yep, sorry, but glad you figured it out. :) You can always find the version of the system-image client with: $ system-image-cli --version >as I said, on the update to r25 on September 13, mine was working fine >and my wife's failed; in my BQ a lot of things are installed below >~phablet, even a chroot complete system to compile things; the one of my >wife is nearly unchanged (if I do not count contacts etc.); the only >"unusual" with my wife's phone is that it was for "repair" in June here >in Germany in the company Mundo Reader GmbH and I don't know what they >did exactly as "repair"; it returned with a new MAC addr, that's why I >think, they just returned another device which I then updated to r24; do >you want me to contact Mundo Reader? I'd find it *very* surprising if they reflashed the device with a wily-based image. I wonder, is the chroot you mention wily or vivid-overlay? Is it at all possible that when you set up the chroot, an update to system-image 3.0 leaked into the root partition? Again, that would be very surprising, especially if your wife's phone was still read-only root. >What do you mean with "dangling symlink"? I could not see any error in >the fetched delta files nor in https://system-image.ubuntu.com/ubuntu- >touch/stable/bq-aquaris.en/krillin/version-25.tar.xz .... Dangling symlink means that there's a symbolic link that points to a file that doesn't exist. Specifically, you *should* see something like this: root@ubuntu-phablet:~# ls -l /etc/system-image/config.d/ total 0 lrwxrwxrwx 1 root root 13 Sep 21 18:59 00_default.ini -> ../client.ini lrwxrwxrwx 1 root root 14 Sep 21 18:59 01_channel.ini -> ../channel.ini root@ubuntu-phablet:~# ls -l /etc/system-image/ total 28 -rw-r--r-- 1 root root 1468 Oct 29 2014 archive-master.tar.xz -rw-r--r-- 1 root root 836 Oct 29 2014 archive-master.tar.xz.asc -rw-r--r-- 1 root root 252 Sep 20 23:25 channel.ini -rw-r--r-- 1 root root 877 Oct 27 2014 client.ini drwxrwxr-x 2 root root 4096 Sep 21 18:59 config.d -rw-r--r-- 1 root root 4755 Sep 10 07:19 writable-paths That's taken from my currently updated BQ phone: root@ubuntu-phablet:~# system-image-cli -i current build number: 129 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-09-21 19:00:00 version version: 129 version ubuntu: 20150921 version device: 20150821-736d127 version custom: 20150821-887-33-32-vivid root@ubuntu-phablet:~# system-image-cli --version system-image-cli 2.5.1 All channels should have an /etc/system-image/config.d directory containing two symlinks, with those symlinks pointing back into existing, non-zero files in /etc/system-image. However, system-image 2.5.1 will ignore /etc/system-image/config.d -- that directory is *only* relevant for system-image >= 3.0, so even if those symlinks were dangling, si 2.5.1 would never even notice. I'm still not positive this is exactly the problem you saw, but it was definitely a problem in si 3.0. I think the best we can do at this point with your bug report is chalk it up to gremlins and re-open it if it ever occurs again. It's only going to be with some live debugging that we can narrow it down. FTR, if it ever does happen again, several bits of information will be helpful: $ system-image-cli --version $ system-image-cli -i and the contents of /var/log/system-image/client.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1495207 Title: BQ E4.5 (r24): after fine update to r25 system is reported as r-1 and as "never" updated Status in Canonical System Image: New Status in system-image package in Ubuntu: Confirmed Bug description: After the vacation I have updated today (September 13, 2015) my BQ 4.5 and the one of my wife to r25. Both updates went without any problem and mine does not show any issue. The one of my wife shows in About the device window: OS number: -1 (and not r25) last updated: never version: Ubuntu 15.04-armhf (20150825-170536) What went wrong and what can I do? I'm afraid that the next update will fail completely now because it can not see the current version. Apart of this the device is working. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1495207/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
