ubuntu-phone team mailing list archive

[Paul Larson <paul.larson@xxxxxxxxxxxxx>]

>From a CI point of view, my main concern is that we:
1. Preserve adb shell access and a way to run things as root. If this means
we have to setup sudo post-install in our CI infrastructure, that's fine. I
already have a patch to do just that, but I am starting to think this
should either be another param to go with --developer-mode *or* a
phablet-config option. The reason for this is because we currently have
things in phablet-tools that will require root access to work properly such
as phablet-network. I suspect others outside of CI might like to use these
conveniently as well.

2. Preserve automatic screen unlocking. Some of the conversation I'm
reading here almost makes it sound like there is a plan to require a
password on screen unlock if the sudo password is also set so that adb can
be used with sudo. If that's the case, then this will effectively crowbar
test automation without a way to automatically unlock the GUI.
On Jul 8, 2014 12:07 PM, "Barry Warsaw" <barry@xxxxxxxxxx> wrote:

> On Jul 08, 2014, at 12:23 PM, Sergio Schvezov wrote:
>
> >On martes 8 de julio de 2014 10h'58:26 ART, Jamie Strandboge wrote:
> >> On 07/08/2014 03:45 AM, Oliver Grawert wrote:
> >>> Am Montag, den 07.07.2014, 22:45 +0200 schrieb Alexander Sack:
> >>  ...
> >> To be clear, we are wanting to support devices that are 'ro' but with
> adb
> >> enabled, right? Ie, I don't want to have to opt out of > system-image
> updates just
> >> cause I enabled adb and/or a sudo password. It would be great if 'rw'
> was
> >> treating separately from the other things.
> >
> >off-topic-ing; but you really don't opt out it seems:
> >https://bugs.launchpad.net/ubuntu/+source/system-image/+bug/1335568
>
> That is correct.  I've updated the bug[*], but essentially, writable image
> and
> system-image-cli are developer tools.  You're supposed to know what you're
> doing when you use them.  Image based updates will still work in writable
> mode
> (and in fact, that's a feature) but you should be very careful when you do
> that as you might get updated into an unexpected state.  You can of course
> still apt-get install/update anything you want, but the interaction between
> apt-get updates and image based updates is undefined.
>
> Cheers,
> -Barry
>
> [*] and marked it invalid at least w.r.t. system-image.
>
> --
> 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
>