Hey,
It took a bit longer than expected, but we finally manage to push,
review and land all the current AOSP 4.4.2 based changes at
https://code-review.phablet.ubuntu.com/.
We decided to use this opportunity to also exercise our gerrit
instance to do proper review for all the patches we had, so t
On Mon, Feb 10, 2014 at 1:35 PM, Sergio Schvezov
wrote:
>
> On 10/02/14 12:20, Jamie Strandboge wrote:
>>
>> On 02/10/2014 08:56 AM, Chris Wayne wrote:
>>>
>>> Jamie,
>>> Thanks for reviving this, it definitely needs more action.
>>>
>>>
>>> I don't think the plan should be to move it into a diffe
On Mon, Feb 10, 2014 at 10:25 AM, Łukasz 'sil2100' Zemczak
wrote:
> For tomorrow's image we plan a new autopilot landing, along with a new
> unity-mir and unity8. Let's hope all goes well and we'll still be in a
> promotable state with our images tomorrow.
So far I hit the publish button on diale
Barry,
I'll check into this when I get home tonight.
Thanks for all your help (everyone).
Alan O'Dannel
Sent from my iPhone
> On Feb 10, 2014, at 1:17 PM, Barry Warsaw wrote:
>
>> On Feb 10, 2014, at 12:47 PM, Alan O'Dannel wrote:
>>
>> All, I just tried the update again, this time I receive
On Feb 10, 2014, at 12:47 PM, Alan O'Dannel wrote:
>All, I just tried the update again, this time I received the error (system
>image.gpg.SignatureError).
Okay, so here's the thing to do:
Take a look at your /etc/system-image/client.ini file to find the locations of
the image_master, image_signi
All, I just tried the update again, this time I received the error (system
image.gpg.SignatureError).
Regards,
Alan O'Dannel
Sent from my iPhone
> On Feb 10, 2014, at 12:15 PM, Timo Leppiniemi
> wrote:
>
> Hi,
>
> I experienced the same problem and did the the update via adb shell. First it
Barry, I am using a network that requires authentication. I successfully
updated using this network in the past. I'll try updating later today on my
home network. If that doesn't work, I'll check the logs and file checksums.
Thank you,
Alan O'Dannel
Sent from my iPhone
> On Feb 10, 2014, at 12
On Feb 10, 2014, at 02:56 PM, Stéphane Graber wrote:
>I did a quick wget test on my laptop here and they all download fine and
>all .asc signatures match with the .tar.xz so they don't appear to be
>corrupted.
The next thing to try, for folks who are seeing this problem, is to compare
the checksu
Hi,
I experienced the same problem and did the the update via adb shell. First it
did not work and I thought ot was caused by problems on the update server. On
second try update was successful. I did copy paste the output to pastebin...
Don't remember the link atm.
> On 10.2.2014, at 21.56, St
On Mon, Feb 10, 2014 at 02:45:09PM -0500, Barry Warsaw wrote:
> On Feb 10, 2014, at 11:16 AM, Alan O'Dannel wrote:
>
> >At the end of the update I receive a message indicating that a file was not
> >found. (FileNotFoundError:/var/lib/system-image/blacklist). The name appears
> >to truncated.
> >
>
On Feb 10, 2014, at 11:16 AM, Alan O'Dannel wrote:
>At the end of the update I receive a message indicating that a file was not
>found. (FileNotFoundError:/var/lib/system-image/blacklist). The name appears
>to truncated.
>
>Is this unique to my device (mako), or is there a problem with the OTA ima
Thank you. Looks like it is something unique to my device.
Regards,
Alan O'Dannel
Sent from my iPhone
> On Feb 10, 2014, at 11:22 AM, wrote:
>
> I have just done, no issue ( mako )
>
> Ciao
> Gio
>
>
>
> Da: Alan O'Dannel
> Data invio: lunedì 10 febbraio 2014 20:16
> A: lukasz.z
I have just done, no issue ( mako )
Ciao
Gio
Da: Alan O'Dannel
Data invio: lunedì 10 febbraio 2014 20:16
A: lukasz.zemc...@canonical.com
Cc: Alexander Sack, ubuntu-phone@lists.launchpad.net, Didier Roche
Lukasz,
At the end of the update I receive a message indicating t
Lukasz,
At the end of the update I receive a message indicating that a file was not
found. (FileNotFoundError:/var/lib/system-image/blacklist). The name appears to
truncated.
Is this unique to my device (mako), or is there a problem with the OTA image?
Thank you,
Alan O'Dannel
Sent from my iP
Hello everyone,
Good news: we have promoted image #173! \o/
Rationale: even though we weren't completely green in terms of autopilot
on mako during smoketesting, after looking closely into the failures we
confirmed all problems being only test-related and no-risk so there was
no need to block on p
If you have a compatible license (and I have no idea what that means in
terms of QML components, but GPLv3 is obviously OK), you can just
include those new components in your project. You'd probably need to
adjust the imports a bit and rename the data attribute back to
children, but that's not
Does nobody have any idea? There's nothing more we can develop on our
app until this is merged.
On mer, 2014-02-05 at 15:56 +, Sam Bull wrote:
> Are expandable items going to be available soon?
>
> It looks like it's been ready to merge for weeks:
> https://code.launchpad.net/~mzanetti/ubuntu
On 10/02/14 12:20, Jamie Strandboge wrote:
On 02/10/2014 08:56 AM, Chris Wayne wrote:
Jamie,
Thanks for reviving this, it definitely needs more action.
I don't think the plan should be to move it into a different deb package shipped
in the rootfs. I thought the plan was to ship everything de
On 01/17/2014 07:32 PM, Steve Langasek wrote:
> On Fri, Jan 17, 2014 at 05:51:27PM +, John McAleely wrote:
>> On 17/01/14 17:04, Oliver Grawert wrote:> hi,
>>> Am Freitag, den 17.01.2014, 16:47 + schrieb John McAleely:
I think that is a genie we would rather not let out of the bottle.
It shouldn't live in /custom, the custom tarball is only for
carrier-specific customizations. TBH it doesn't matter to me in which
dir/partition this stuff lives, as long as it's not shipped in the rootfs
image.
On Mon, Feb 10, 2014 at 10:20 AM, Jamie Strandboge wrote:
> On 02/10/2014 08:56 AM,
On 02/10/2014 08:56 AM, Chris Wayne wrote:
> Jamie,
> Thanks for reviving this, it definitely needs more action.
>
>
> I don't think the plan should be to move it into a different deb package
> shipped
> in the rootfs. I thought the plan was to ship everything device-specific in
> the
> device
Jamie,
Thanks for reviving this, it definitely needs more action.
I don't think the plan should be to move it into a different deb package
shipped in the rootfs. I thought the plan was to ship everything
device-specific in the device tarball? (That is after all, the whole
purpose of this thread
Hi Ricardo,
It happened to me twice on mako, once on bulid # 172 on Saturday and once
on build # 173 on Sunday, but since about 24 hours the phone is working
properly.
Kind regards
/sebastian
2014-02-10 Ricardo Salveti de Araujo :
> On Sun, Feb 9, 2014 at 10:34 AM, Sebastian Gomułka
> wrote
23 matches
Mail list logo
