On Mon, Mar 17, 2014 at 11:37 PM, Jamie Strandboge wrote:
>
>> My understanding is that the store will only return results to clients
>> that match frameworks they have.
>
> I think at the time I wrote this, the store didn't yet support this, but
> perhaps
> I was mistaken. If it hasn't landed by
On Tue, Mar 18, 2014 at 2:06 AM, Ricardo Salveti de Araujo
wrote:
> It seems this happened because it tried to upgrade the apps but failed
> as the framework was invalid (previous images didn't have the 14.04
> framework).
>
> I wonder if this is also happening with the latest stable image (from
>
Hi David,
thanks, that's a lot better. I don't know where the difference comes
from, but now I don't get the error about a missing spec file anymore.
I wonder about the extracting of the binary files.
The "building" wiki pages mentions that they should be taken from a CM
image. I tried to ru
On Tue, Mar 18, 2014 at 9:24 AM, Martin Albisetti wrote:
> On Tue, Mar 18, 2014 at 2:06 AM, Ricardo Salveti de Araujo
> wrote:
>> It seems this happened because it tried to upgrade the apps but failed
>> as the framework was invalid (previous images didn't have the 14.04
>> framework).
>>
>> I wo
SDK team status - 18.03.2014
QtC/ Tools
* The plugin trunks are migrated to QtC 3.0
* Pass user arguments to cmake running in the chroot [4]
* Forced clean up before cmake
* Include the shlibs info that qtcreator should and make dh_shlibdeps
search plugin directories for deps
* Remove hard-
"I don't know where the difference comes from, but now I don't get the
error about a missing spec file anymore."
Figure it out is definitely the best knowledge, skills, teaching, you could
have.
In my opinion it's even more important than reaching the building goal.
About the binaries blobs I don
Hello.
My name is Luis Cuervo and I am an Android/FFOS engineer.
Right now i'm working with a Geeksphone Revolution (
http://www.geeksphone.com/) and I get FFOS working on it. It's a X86
device. I have all sources needed to build any image but i signed a NDA and
cant share them :( .
I was thinki
Hey everyone,
It has been a while since the settings team didn't send a status update,
here is a summary of what kept us busy during that time
* Testing
In saucy we had a rather low number of tests, we spent quite some this
cycle to fix that. We have now over 50 integration tests and mocks f
On Tue, Mar 18, 2014 at 11:53 AM, Corvus wrote:
> Hello.
>
> My name is Luis Cuervo and I am an Android/FFOS engineer.
>
> Right now i'm working with a Geeksphone Revolution
> (http://www.geeksphone.com/) and I get FFOS working on it. It's a X86
> device. I have all sources needed to build any ima
I added this to the default cmdline using Boardconfig.mk:
datapart=/dev/block/mmcblk0p9 boot=touch debug rw console=tty0,115200n8
no_console_suspend=1
I modify too the init scrip so now it does ln -s /dev/userdata
/dev/block/mmcblk0p9
Neither of this work. And it's supposed that if a data partit
hi,
Am Dienstag, den 18.03.2014, 17:19 +0100 schrieb Corvus:
> I added this to the default cmdline using Boardconfig.mk:
>
>
> datapart=/dev/block/mmcblk0p9
you want this to be datapart=/dev/mmcblk0p9 since this is not android,
it uses proper linux device names ;)
ciao
oli
signature
Thank you. I will test it. And rechecking the cmdline in boot.img seems
that it modified in recovery.img but not in boot.img so datapart and the
rest of variables are not in boot.img.
Thanks for your help, will test this and add the correct boot.img cmdline
and come back to show you the results :D
hi,
Am Dienstag, den 18.03.2014, 17:19 +0100 schrieb Corvus:
> I added this to the default cmdline using Boardconfig.mk:
>
> boot=touch
oh, and I only noticed this after sending the last mail, why do you add
boot=touch ? there is no such boot script, we just use the Ubuntu
defaults, you should no
res on music-app (Alan/Bill):
https://bugs.launchpad.net/music-app/+bug/1293488
* reliable test failure on calendar-app (Alan/Bill):
https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1293489
-> Note that there is one more in #243:
http://ci.ubuntu.com/smokeng/trusty/touch/mako/243:20140318:
On Tue, Mar 18, 2014 at 1:19 PM, Corvus wrote:
> I added this to the default cmdline using Boardconfig.mk:
>
> datapart=/dev/block/mmcblk0p9 boot=touch debug rw console=tty0,115200n8
> no_console_suspend=1
>
> I modify too the init scrip so now it does ln -s /dev/userdata
> /dev/block/mmcblk0p9
>
>
> You can also edit your boot.img by hand as well (using abootimg), so
> you can then just replace your custom initrd and use it to boot your
> device.
>
My boot.img is not working with abootimg because is not standard. I cannot
even extract it :-(
> Cheers,
>
> --
> Ricardo Salveti de Araujo
hi,
Am Dienstag, den 18.03.2014, 19:52 +0100 schrieb Corvus:
>
> >
> > You can also edit your boot.img by hand as well (using abootimg), so
> > you can then just replace your custom initrd and use it to boot your
> > device.
> >
>
> My boot.img is not working with abootimg because is not standard
Hello everyone. After last Ubuntu SDK update I can't run QML application on desktop. What I must to do to fix bug?
--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help : https://help.laun
On Tue, Mar 18, 2014 at 2:47 PM, Didier Roche wrote:
> Blocking issues for image promotion:
>
> * Volume buttons no longer function correctly since #238 mako/flo/manta
> (Ricardo)
> https://bugs.launchpad.net/ubuntu/+source/android/+bug/1293478
I updated the bug and also moved it to Unity8 (the l
On 03/18/2014 01:57 PM, Зонов Роман wrote:
> Hello everyone.
>
> After last Ubuntu SDK update I can't run QML application on desktop. What I
> must
> to do to fix bug?
>
How are you running it?
If you are using qmlscene directly or via QtCreator, I suggest filing a bug
using:
$ ubuntu-bug qt
On 18.03.2014 21:56, Ricardo Salveti de Araujo wrote:
Would be nice if someone from the Unity8 team could take a look a this issue.
See bugs:
- https://launchpad.net/bugs/1283191
- https://launchpad.net/bugs/1293478
Fix for one is in silo 13 already, although Ricardo found another issue
at th
On Tue, Mar 18, 2014 at 2:47 PM, Didier Roche wrote:
> * messaging app flaky test (Bill):
> https://bugs.launchpad.net/messaging-app/+bug/1293610
>
I have just submitted a branch that should make that test more reliable:
https://code.launchpad.net/~boiko/messaging-app/fix_autopilot/+merge/211651
calendar-app (Alan/Bill):
https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1293489
-> Note that there is one more in #243:
http://ci.ubuntu.com/smokeng/trusty/touch/mako/243:20140318:20140304/7236/calendar_app/
Calendar has some wonkiness to it; discovered this last Friday and it
hasn't gone
So for my shift today, I got a number of small fixes in and kicked
image 245, which contains:
address-book-app, ubuntu-download-manager, ofono, and unity-webapps-qml.
Then I published mir along with a tiny qtubuntu bugfix, which will
soon become image 256 when cron kicks the next image.
--
Mail
* Nicholas Skaggs wrote:
> On a sidenote, as both my devices are running #244 they are
> useless for testing :-( Fortunately Alan had a device on stable
> we could vet changes with. Lesson learned, don't update both
> devices at the same time.
Me too; r244 and r245 both exhibit rather frequent
On Wed, Mar 19, 2014 at 2:55 AM, Ricardo Salveti de Araujo
wrote:
> On Tue, Mar 18, 2014 at 10:24 PM, Robert Park
> wrote:
>> So for my shift today, I got a number of small fixes in and kicked
>> image 245, which contains:
>>
>> address-book-app, ubuntu-download-manager, ofono, and unity-webapps
On Tue, Mar 18, 2014 at 10:24 PM, Robert Park wrote:
> So for my shift today, I got a number of small fixes in and kicked
> image 245, which contains:
>
> address-book-app, ubuntu-download-manager, ofono, and unity-webapps-qml.
>
> Then I published mir along with a tiny qtubuntu bugfix, which will
27 matches
Mail list logo
