touch-packages team mailing list archive

[Simon Fels <simon.busch@xxxxxxxxxxxxx>]

On 16.09.2015 10:32, Matthias Apitz wrote:
> I have pulled the tar files for the device and channel and the file
> channel.ini is fine in the archive version-25.tar.xz;
>
> more:
> the file has in all three locations:
> - my BQ r25
> - the version-25.tar.xz
> - the damaged file in my wife's BQ
> the same last modification time 2 sep 11:33
>
> it's absolutely unclear while it was of zero bytes in my wife's BQ; how
> the file is moved from the tar file in place during installation? it can
> not be a simple un-tar because the file in the tar archive is
> 'system/etc/system-image/channel.ini'
>

It is a simple un-tar. Have a look at [1]. The system partition/image is 
mounted at /recovery/system and the un-tar is run with the current 
directory set /recovery which then completely matches the directory 
layout in the update tarball. However it's a two-step process where 
first all removed files are removed and then the new/changed files are 
added/updated.

regards,
Simon

[1]: 
https://code-review.phablet.ubuntu.com/gitweb?p=CyanogenMod/android_bootable_recovery.git;a=blob;f=system-image-upgrader;h=c645b0abebb2a2d1295fd20071a4f10b9ce78cf0;hb=refs/heads/phablet-4.4.2_r1#l515

-- 
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:
  New

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