Thank you for the detailed explanation!
So that means that if I manually install a package, it gets reverted to
the one included in the system image when updating, before applying the
diff and no matter if I switched back to read-only mode before or not,
right?
If I understand it correctly, I always have to reinstall the package
but I do not have to do any cleanup work like reverting to read-only
mode. Please correct me if I'm wrong. ;)
Am Do, 28. Mai, 2015 um 2:32 schrieb Oliver Grawert <[email protected]>:
Am Donnerstag, den 28.05.2015, 13:36 +0200 schrieb Niklas Wenzel:
Hi all,
I am wondering how the image based update mechanism handles manually
installed Debian packages.
very simple, it doesn't
the system image update is a diff between two rootfs builds ... during
update the rootfs is made readwrite and the diff is applied on top of
the usually readonly rootfs ... thats it ...
if you have modified any files that existed before, they get reverted
(this includes the package db ! ) ... if you added single files that
didn't exist before on the image these will not be touched.
if you installed a .deb package manually with a newer version the info
from the package db will be gone/reverted (see above) and changed
files
will be reverted.
if you don't keep your system constantly writeable but only make it
shortly writeable to install a deb for testing and then switch back to
readonly system-image updates you might get through with that, but i
wouldn't count on it ...
ciao
oli
--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : [email protected]
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help : https://help.launchpad.net/ListHelp
--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : [email protected]
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help : https://help.launchpad.net/ListHelp
