Le 16/01/2014 17:53, Didier Roche a écrit :
We are waiting on AP tests results in the infrastructure (so, another
5-6 hours) and we need to dogfood the image on both maguro and mako.
We'll probably be able to promote an image only tomorrow morning
european time surely.
Image test results
On Thu, Jan 16, 2014 at 08:22:43AM -0600, Jamie Strandboge wrote:
> On 01/16/2014 08:08 AM, Chris Wayne wrote:
> > My point is that lxc-android-config should even only have *generic*
> > container
> > bits. Anything and everything that is device-specific should not be in the
> > rootfs
> For th
On Tue, Jan 14, 2014 at 02:46:38PM -0800, Alex Chiang wrote:
> >> While this works for now with our limited set of supported devices, it can
> >> quickly become untenable once we start building images for OEMs in the
> >> future,
> >> or if we get an influx of community builds.
> > I figured that
Hi all,
Many thanks to Chris for raising this important topic.
As Alex mentioned, he and I had chatted earlier this week about the
importance of keeping a single Ubuntu root image that's common to all
devices. This is something that we need to hold the line on; allowing
individual OEMs to have c
Hello,
To learn some more Go and also about Click package internals I wrote a tool
that modulo bugs and a few corner cases replicates what the official click
build and click buildsource commands do
I only tested it very briefly and on a single package so far.
If you have Go installed and GOPATH s
On Wed, Jan 15, 2014 at 5:12 AM, Oliver Grawert wrote:
>
> > /etc/init/bluetooth-touch-maguro.conf
> this is a question for cyphermox ... i guess it should rather be named
> after the BT chipset than after the device (and ship multiple configs)
> but currently we only have one device using this c
On Thu, Jan 16, 2014 at 02:34:11PM -0500, Chris Wayne wrote:
> After some digging around the system, the following types of
> device-specific files are currently living in our rootfs:
>
>- upstart jobs in /etc/init
>- udev rules (in /etc/udev/rules.d and /lib/udev/rules.d)
>- ubuntu-to
After some digging around the system, the following types of
device-specific files are currently living in our rootfs:
- upstart jobs in /etc/init
- udev rules (in /etc/udev/rules.d and /lib/udev/rules.d)
- ubuntu-touch-session configs (basically just telling the system the
number of p
On 01/12/2014 02:24 PM, Tomas wrote:
> Hi,
>
> any news about when Swedish keyboard will be merged?
The code to split out keyboard language specific plugins (which includes
layouts, spell checking and predictive text) into seperate packages has
been merged in trunk, and we're working in parallel o
On 01/16/2014 12:41 PM, Bill Filler wrote:
> On 01/16/2014 01:27 PM, Jamie Strandboge wrote:
>> On 01/16/2014 12:08 PM, Bill Filler wrote:
>>
>> ...
>>> *Dialer App: *
>>> ...
>>> * Work beginning to support call hold and call switch UI
>> I'm not up on all the terminology, so forgive me. Does this
On 01/16/2014 01:27 PM, Jamie Strandboge wrote:
> On 01/16/2014 12:08 PM, Bill Filler wrote:
>
> ...
>> *Dialer App: *
>> ...
>> * Work beginning to support call hold and call switch UI
> I'm not up on all the terminology, so forgive me. Does this include ignoring a
> call? Ie LP: #1260988
>
>
Just
On 01/16/2014 12:08 PM, Bill Filler wrote:
...
> *Dialer App: *
> ...
> * Work beginning to support call hold and call switch UI
I'm not up on all the terminology, so forgive me. Does this include ignoring a
call? Ie LP: #1260988
--
Jamie Strandboge http://www.ubuntu.com/
si
?Hi Guys,
I will be sending out weekly status updates of the progress the System
Apps team is making. Here is the report for last week.
*Telephony Services: *
* landed support in history-service, ofono-qt and telepathy-ofono to
support the newly added multi-party calling and delivery reporting
fea
mokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/ubuntu-clock-app-autopilot/642628/
Today's run contains an actual test failure possibility, looking into
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/131:20140116:20140115.1/6095/ubuntu-clock-app-autopilot/673039/
*calendar-app* (
Le 16/01/2014 11:58, Didier Roche a écrit :
Will continue giving you informations.
Cheers,
Similar information than the one giving on the ubuntu-phone mailing list
under the title "Landing team 16.01.14".
Ricardo fixed the issue promptly, we reran all AP tests manually to
certify that this
Hey,
short message today.
As you can see on the other thread "stop the line", we had to continue
stopping the line due to another bug that was detected. The unity-mir
fix is in thanks to the excellent work from Ricardo. The image is
building now and we wait for the test results to unblock the
What was the cause of the issue after all?
Jim
On Thu, Jan 16, 2014 at 7:50 AM, Oliver Grawert wrote:
> hi,
> Am Donnerstag, den 16.01.2014, 13:43 +0100 schrieb Sebastian Gomułka:
> > It looks like, that the bug with stopping music playback when the
> > screen goes blank returned - mako, build
On 01/16/2014 08:08 AM, Chris Wayne wrote:
> My point is that lxc-android-config should even only have *generic* container
> bits. Anything and everything that is device-specific should not be in the
> rootfs
>
For the reference hardware (including the emulator), how does one update the
device-s
hi,
Am Donnerstag, den 16.01.2014, 09:08 -0500 schrieb Chris Wayne:
> My point is that lxc-android-config should even only have *generic*
> container bits. Anything and everything that is device-specific
> should not be in the rootfs
>
which is currently technically impossible ... i.e. we need th
My point is that lxc-android-config should even only have *generic*
container bits. Anything and everything that is device-specific should not
be in the rootfs
On Thu, Jan 16, 2014 at 9:04 AM, Oliver Grawert wrote:
> hi,
> Am Donnerstag, den 16.01.2014, 08:58 -0500 schrieb Chris Wayne:
> > We
hi,
Am Donnerstag, den 16.01.2014, 08:58 -0500 schrieb Chris Wayne:
> We should still have as little as possible device-specific in
> lxc-android-config though, shouldn't we? I'm all for putting
> *everything* device specific into the device tarball, otherwise it's
> simply not maintainable.
>
we
We should still have as little as possible device-specific in
lxc-android-config though, shouldn't we? I'm all for putting *everything*
device specific into the device tarball, otherwise it's simply not
maintainable.
On Thu, Jan 16, 2014 at 8:46 AM, Jamie Strandboge wrote:
> On 01/15/2014 04:34
Hello everyone; just to let you know that if you are on trusty you can
install ubuntu-device-flash and ubuntu-emulator
ubuntu-device-flash is going to be replacing phablet-flash and removes
all the old cruft and hacks set in place following all the architecture
changes and backwards compatibil
On 01/15/2014 04:34 PM, Jamie Strandboge wrote:
> On 01/15/2014 03:43 PM, Sergio Schvezov wrote:
>>
>> On 15/01/14 15:56, Jamie Strandboge wrote:
>>> On 01/15/2014 12:49 PM, Alex Chiang wrote:
On Wed, Jan 15, 2014 at 4:28 AM, Sergio Schvezov
wrote:
> On 14/01/14 19:46, Alex Chiang wr
That's great. By the way, music in FLAC format sound much better on Ubuntu
than on Android.
Best regards
/sebastian
2014/1/16 Łukasz 'sil2100' Zemczak
> Hello!
>
> On 16.01.2014 13:43, Sebastian Gomułka wrote:
> > It looks like, that the bug with stopping music playback when the screen
> > go
Hello!
On 16.01.2014 13:43, Sebastian Gomułka wrote:
> It looks like, that the bug with stopping music playback when the screen
> goes blank returned - mako, build 131.
>
>
>
Yes, we know of this regression - our team stumbled upon it today as
well. Thanks to everyone involved a fix for this i
hi,
Am Donnerstag, den 16.01.2014, 13:43 +0100 schrieb Sebastian Gomułka:
> It looks like, that the bug with stopping music playback when the
> screen goes blank returned - mako, build 131.
>
yup, was just fixed next image will have it (and will hopefully be
promoteable)
ciao
oli
It looks like, that the bug with stopping music playback when the screen
goes blank returned - mako, build 131.
--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help : https://help.launchpad
You have one great 10-inch tablet, it does not require an emulator. Why you
want to make all harder?)
--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help : https://help.launchpad.net/Lis
Le 16/01/2014 11:14, Didier Roche a écrit :
We didn't cross fingers enough apparently. Another regression was spot
just in time by Alan
(https://bugs.launchpad.net/music-app/+bug/1269744) while doing
dogfooding.
For now, we only know it was working on image #121 and the bug is in
latest image
Le 15/01/2014 17:42, Didier Roche a écrit :
Some more updates.
The rss reader issue was found (a change in a public rss feed used in
the tests).
Nicholas' fix is under review to use a mock rss feed in the test so
that we are not impacted by those anymore.
We will be back in a normal situatio
On Wed, Jan 15, 2014 at 8:18 PM, Jamie Strandboge wrote:
> On 01/13/2014 08:40 AM, Alexander Sack wrote:
>> 1. Ubuntu Engineering (UE) will make a strong push on the _emulator_
>> during the month' ahead. Goal is to support the emulator for arm and
>> x86 as a _primary engineering platform_ for UE
On Tue, Jan 14, 2014 at 6:16 AM, Shuduo Sang wrote:
> On Mon, Jan 13, 2014 at 11:19 PM, Зонов Роман wrote:
>> Sorry. but your decision about manta is minimum...strange. IMHO, manta is
>> very important for development. Not because I have one, because manta is a
>> tablet with 10-inch display. M
33 matches
Mail list logo
