Hi guys,
when we using this ks(http://wiki.meego.com/images/Tiny-wl.ks) to create
Wayland testing image with command sudo mic-image-creator -c tiny-wl.ks
-t tmp --cache=cache -f livecd --logfile=log.
we got this error msg, does anyone know how to fix it?
"Please specify the main repo name using
On Thu, Jun 30, 2011 at 5:09 AM, Ramez Hanna wrote:
> On Tue, 2011-06-14 at 10:52 +0200, ext Dominig ar Foll wrote:
>> Hello,
>>
>> those who have discussed with me during the MeeGo Conference in San
>> Francisco, know that I have started a small project to create a Light
>> version of OBS.
>>
>>
On Thu, 2011-06-30 at 11:00 -0700, Arjan van de Ven wrote:
> exactly; this is what the change is solving; each source package (which
> is the ultimate unit that has an owner,
> and tends to map basically 1:1 to upstream git repos/etc) has now its
> own component and owner.
Theoretically correct
On 6/30/2011 10:11 AM, Dave Neary wrote:
Developers seeing bugs that they are able to fix helps the bugs get
fixed. If a module developer is searching for open bugs in "his" module
and doesn't find any, then that's a problem.
exactly; this is what the change is solving; each source package (whi
On Thu, 2011-06-30 at 19:11 +0200, Dave Neary wrote:
> Ways to solve the problem would be for the developer to search for
> something else (bugs owned by meta_ow...@meego.bugs or whatever)
That would also make it easier to follow components that one is
interested in contributing to while NOT being
Hi,
Arjan van de Ven wrote:
> anything that leads to the bug getting fixed is value. that's not just
> what developers do...
Developers seeing bugs that they are able to fix helps the bugs get
fixed. If a module developer is searching for open bugs in "his" module
and doesn't find any, then that'
As long as the bugs are assigned to the original reporter, would they
not be filed with them?
Having descriptive bug reports does matter to the developer, if the
problem is not described, how can we fix it? I come from a Bugzilla
background so would this also not apply here?
On 30/06/2011 15
On 06/30/2011 06:22 PM, Luis Araujo wrote:
Forwarding to our mailing list.
Original Message
Subject:LMT removal announcement?
Date: Thu, 30 Jun 2011 11:50:38 -0430
From: Luis Araujo
To: meego-packag...@meego.com
CC: meego-dev@meego.com
Hello everyone,
Hello everyone,
I just noticed libmeegotouch was removed from the repositories[0], along
with all the meegotouch* packages.
Did we get an announcement somewhere about this happening today?, I
mean, we all know LMT would be removed soon, but it'd be nice to know
this in advance.
Cheers,
[0
On Thu, Jun 30, 2011 at 5:54 PM, Thiago Macieira wrote:
> Em Thursday, 30 de June de 2011, às 17:22:48, Ville M. Vainio escreveu:
>> If you don't get worse performance with Qt Compositor, is there a good
>> reason not to use it (as a starting point again, since it's not a
>> "product" in itself)?
On Wed, Jun 29, 2011 at 11:17 AM, Wichmann, Mats D
wrote:
>
> For the purposes of compliance is only GLESv2 required, or is v1 also
> required?
> If the latter, we have an issue to figure out in that there seems to be some
> variance in library names (the Mesa version is /usr/lib/libGLESv1_CM.so.1
Em Thursday, 30 de June de 2011, às 17:22:48, Ville M. Vainio escreveu:
> One advantage of using Qt Compositor as starting point would be making
> the compositor easy to modify, e.g. for OEM's looking for
> differentiated experience at compositor level.
>
> If you don't get worse performance with Q
On Thu, Jun 30, 2011 at 10:22 AM, Ville M. Vainio wrote:
> On Thu, Jun 30, 2011 at 2:41 PM, Thiago Macieira wrote:
>
>> It doesn't. I was going to ask steven what reasons he had for using the qt
>> compositor. It's just a sample compositor, showing what is possible to do if
>> you integrate the w
On Thu, Jun 30, 2011 at 2:41 PM, Thiago Macieira wrote:
> It doesn't. I was going to ask steven what reasons he had for using the qt
> compositor. It's just a sample compositor, showing what is possible to do if
> you integrate the wayland libraries into a QML-based application. I've seen
> other
On 6/30/2011 7:10 AM, Marius Vollmer wrote:
ext Arjan van de Ven writes:
On 6/29/2011 11:57 PM, eric.le-r...@nokia.com wrote:
I hear you but isn't moving a bug to another component an important enough
event it's worth recording it in an inline comment on the bug?
I would say not. the compone
ext Arjan van de Ven writes:
> On 6/29/2011 11:57 PM, eric.le-r...@nokia.com wrote:
>>
>> I hear you but isn't moving a bug to another component an important enough
>> event it's worth recording it in an inline comment on the bug?
>
> I would say not. the component is metadata and does not add va
On 6/30/2011 7:02 AM, eric.le-r...@nokia.com wrote:
I have a very simple idea on bugs; the value of a bug lies in its
ability to fix something in the OS
that makes the OS better. Anything else around the bug is either neutral
or overhead.
Now that you put it this way, I'm more than convinced th
Hi Arjan,
On 6/30/11 4:41 PM, "ext Arjan van de Ven" wrote:
>On 6/29/2011 11:57 PM, eric.le-r...@nokia.com wrote:
>>
>> I hear you but isn't moving a bug to another component an important
>>enough
>> event it's worth recording it in an inline comment on the bug?
>
>I would say not. the component
On 6/29/2011 11:57 PM, eric.le-r...@nokia.com wrote:
I hear you but isn't moving a bug to another component an important enough
event it's worth recording it in an inline comment on the bug?
I would say not. the component is metadata and does not add value to the
bug itself
it doesn't he
Hi,
On 30/06/11 13:09, Ramez Hanna wrote:
I also got similar (if not exactly) requirements from some of our
internal developers, I have drafted a wiki page describing the reasons
we think we need a different tool than just osc/obs and some details of
the proposed implementation
Do you have a l
On Tue, 2011-06-14 at 10:52 +0200, ext Dominig ar Foll wrote:
> Hello,
>
> those who have discussed with me during the MeeGo Conference in San
> Francisco, know that I have started a small project to create a Light
> version of OBS.
>
> The goal of the project is to ease the access to OBS for emb
Em Thursday, 30 de June de 2011, às 14:08:37, Tiago Vignatti escreveu:
> On 06/30/2011 12:43 PM, steven wrote:
> > how about qt-compositor?
>
> Because we don't need that much.
>
> In principle, we are happy with a single compositor that contains only a
> very thin layer for MeeGo. Besides, pushing
On 06/30/2011 12:43 PM, steven wrote:
how about qt-compositor?
Because we don't need that much.
In principle, we are happy with a single compositor that contains only a
very thin layer for MeeGo. Besides, pushing the effort of building a
compositor Qt-independent would ease the adoption for
Hi Rolla,
Selbak, Rolla N wrote:
> Just fyi, the 1.3 release schedule is posted up on the wiki:
>
> http://wiki.meego.com/Release_Engineering/Plans/1.3
>
> Main dates are:
>
> MM2: Jul 26 - Intrusive (high risk and priority) changes phase complete
Is there a milestone (perhaps past) on decisio
On Thu, 2011-06-30 at 10:42 +0200, nic...@nicoladefilippo.it wrote:
> Hi,
> what's a difference betwen
> http://repository.maemo.org/meego/n900-de/daily/1.2.0.90.5.20110624.3.DE.2011-06-28.1/images/mg-handset-armv7nhl-n900-ce-stable/
> and
> http://repository.maemo.org/meego/n900-de/archive/1.2.0.
Hi,
how about qt-compositor?
On Thu, 2011-06-30 at 10:56 +0300, Tiago Vignatti wrote:
> On 06/30/2011 09:50 AM, Zhao, Juan J wrote:
> > Hi there,
> >
> > Which wayland-compositer will meego use when moving to wayland?
>
> There is some sort of wrapper in wayland-compositor (meego shell) with a
Hi,
what's a difference betwen
http://repository.maemo.org/meego/n900-de/daily/1.2.0.90.5.20110624.3.DE.2011-06-28.1/images/mg-handset-armv7nhl-n900-ce-stable/
andhttp://repository.maemo.org/meego/n900-de/archive/1.2.0.90.5.20110621.5.DE.2011-06-23.1/images/mg-handset-armv7nhl-n900-ce-stable/
On 06/30/2011 09:50 AM, Zhao, Juan J wrote:
Hi there,
Which wayland-compositer will meego use when moving to wayland?
There is some sort of wrapper in wayland-compositor (meego shell) with a
specific protocol interface that we have to shape to accommodate the
style of windows that MeeGo UX h
"Zhao, Juan J" writes:
> Hi there,
> Which wayland-compositer will meego use when moving to
> wayland?
I guess the details you need are in here¹?
¹ http://wiki.meego.com/Wayland_in_MeeGo
--
Roger WANG Intel Open Source Technology Center
_
29 matches
Mail list logo
