ubuntu-phone team mailing list archive

[Christian Dywan <christian.dywan@xxxxxxxxxxxxx>]

As a rule of thumb, apt-get doesn't agree well with OTA. There is a 
fair chance of the following reboot to get stuck in a loop.
apt-get uses dpkg which is oblivious of symlinks used to make certain 
files writable on a normally readonly image - when you're making it 
writable you're cheating, services and apps on the system can't do 
that. So if dpkg happens to touch one of these special links it will 
break writability of that file.

PPAs are using apt-get, so they are affected just the same. apt-get 
update is more likely to cause a problem because you will pull in lots 
of arbitrary updates.


If, like me, you do this anyway because you find you need to install 
things using apt, be sure to save this link:

http://sturmflut.github.io/ubuntu/bq/2015/05/04/hacking-the-bq-part-1-bootloader-fastboot-recovery/

ciao,
   Christian

Am Mi, 29. Jul, 2015 um 3:25 schrieb lgd 
<linuxgehtned@xxxxxxxxxxxxxxxx>:
> Am 27.07.2015 um 10:53 schrieb M Moldaviax:
> >  Will following the steps suggested prevent future OTA updates?
> >  cheers
>
> I think not really? But when I make the system writable I only use
> apt-get to update. I think a mix of both is not good beside some 
> special
> cases with little system changes. Maybe a Canonical developer can
> explain it more clear if you would need it.
>
> >  On Fri, Jul 24, 2015 at 7:33 PM, lgd <linuxgehtned@xxxxxxxxxxxxxxxx
> >  <mailto:linuxgehtned@xxxxxxxxxxxxxxxx>> wrote:
> >
> >      Am 24.07.2015 um 15:48 schrieb Gijs Hillenius:
> >      > 5) reboot
> >
> >      Closing of system settings and reopening worked for me, too. So 
> > tests
> >      are much faster.
>
>
>
> --
> Mailing list: https://launchpad.net/~ubuntu-phone
> Post to     : ubuntu-phone@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~ubuntu-phone
> More help   : https://help.launchpad.net/ListHelp