Sander van Grieken wrote:
> On Wednesday 24 September 2008 23:42:13 Rod Whitby wrote:
>> Sander van Grieken wrote:
Sander van Grieken wrote:
>>> That may be, but despite that I need a daily package for kernel I can
>>> point people to.
>>> Actually blocking current stable kernel fr
On Wednesday 24 September 2008 23:42:13 Rod Whitby wrote:
> Sander van Grieken wrote:
> >> Sander van Grieken wrote:
> > That may be, but despite that I need a daily package for kernel I can
> > point people to.
> > Actually blocking current stable kernel from users by not packaging
> >
#2029: Class 0 SMS wrongly decoded (no UTF-8?)
+---
Reporter: vnevoa |Owner: openmoko-devel
Type: defect | Status: new
Priority: normal |Milestone:
Comp
#2029: Class 0 SMS wrongly decoded (no UTF-8?)
+---
Reporter: vnevoa |Owner: openmoko-devel
Type: defect | Status: new
Priority: normal |Milestone:
Comp
On Wednesday 24 September 2008 23:47:30 Rod Whitby wrote:
I have filed the following task:
https://docs.openmoko.org/trac/ticket/2034
>
> What is required is a *commitment* from Openmoko to officially publish
> and maintain the configuration documentation of the autobuilder.
It is not like we c
El jue, 25-09-2008 a las 00:22 +0800, Daniel Willmann escribió:
> [Copying this mail to openmoko-devel as well to raise awareness]
>
> Hello list,
>
> most of the FSO team is now in Taipei and yesterday we collected items
> we want to discuss/work on in the three weeks we will be here.
>
> Here'
Holger Freyther wrote:
> On Wednesday 24 September 2008 09:08:57 Rod Whitby wrote:
>> Andy Green wrote:
>>> It used to be that our kernel packages followed our stable kernel git
>>> daily.
>>>
>>> But the hash on that one tells it is stuck at Aug 23 patchlevel...
>> Yet another reason why the openm
Andy Green wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Somebody in the thread at some point said:
> |> That may be, but despite that I need a daily package for kernel I
> |> can point people to. Actually blocking current stable kernel from
> |> users by not packaging it, which se
Sander van Grieken wrote:
>> Sander van Grieken wrote:
> That may be, but despite that I need a daily package for kernel I can
> point people
> to.
> Actually blocking current stable kernel from users by not packaging it,
> which seems
> to
> be the case, is completely
On Wednesday 24 September 2008, Wolfgang Mauer wrote:
> Hi all,
> i'am new here.
> Maybe this is the wrong list, but i want to know if there some newer mono
> and gtk-sharp packages as the 1.2. for the neo?
> Are there packages for NDesk.DBus(DBUS-Sharp) avail?
> I want to do some projects with
Hi all,
i'am new here.
Maybe this is the wrong list, but i want to know if there some newer mono and
gtk-sharp packages as the 1.2. for the neo?
Are there packages for NDesk.DBus(DBUS-Sharp) avail?
I want to do some projects with C# on the neo.
Thanks for help
Wolfgang
__
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|> That may be, but despite that I need a daily package for kernel I can
|> point people to. Actually blocking current stable kernel from users by
|> not packaging it, which seems to be the case, is complete
Daniel Willmann wrote:
> [Copying this mail to openmoko-devel as well to raise awareness]
>
> Hello list,
>
> most of the FSO team is now in Taipei and yesterday we collected items
> we want to discuss/work on in the three weeks we will be here.
>
> Here's the preliminary list of problems we wan
On Wed, 24 Sep 2008 17:16:12 +0800
Daniel Willmann <[EMAIL PROTECTED]> wrote:
> Hello list,
>
> most of the FSO team is now in Taipei and yesterday we collected items
> we want to discuss/work on in the three weeks we will be here.
>
> Here's the preliminary list of problems we want to tackle. I
On Wednesday 24 September 2008, Holger Freyther wrote:
> On Wednesday 24 September 2008 11:12:15 Andy Green wrote:
> > Somebody in the thread at some point said:
> > | It's up the the person in charge of testing the linux-openmoko bitbake
> > | recipe to determine what the latest stable version in
[Copying this mail to openmoko-devel as well to raise awareness]
Hello list,
most of the FSO team is now in Taipei and yesterday we collected items
we want to discuss/work on in the three weeks we will be here.
Here's the preliminary list of problems we want to tackle. If you have
any comments o
On Wednesday 24 September 2008 09:08:57 Rod Whitby wrote:
> Andy Green wrote:
> > It used to be that our kernel packages followed our stable kernel git
> > daily.
> >
> > But the hash on that one tells it is stuck at Aug 23 patchlevel...
>
> Yet another reason why the openmoko autobuilder configura
On Wednesday 24 September 2008 11:12:15 Andy Green wrote:
> Somebody in the thread at some point said:
> | It's up the the person in charge of testing the linux-openmoko bitbake
> | recipe to determine what the latest stable version in the feeds should
> | be by updating that sane-srcrevs.inc file
On Wednesday 24 September 2008 14:24:14 Sander van Grieken wrote:
> I agree, and that's where sane-srcrevs.conf comes in, because it acts as a
> gatekeeper for distribution integration testing.
right
> But the SD card corruption patch (and most others patches) have no impact
> on interfaces or i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|> That may be, but despite that I need a daily package for kernel I
|> can point people to. Actually blocking current stable kernel from
|> users by not packaging it, which seems to be the case, is
|> comple
Hi all,
I think we are facing a limitation of the package/build environment.
It's nice to have stable/testing packages, but for day-to-day
development we need to be able to mix all those in a manner that makes
sens for developers.
If I'm working on a package or I'm having a bug that is experiment
#2029: Class 0 SMS wrongly decoded (no UTF-8?)
+---
Reporter: vnevoa |Owner: openmoko-devel
Type: defect | Status: new
Priority: normal |Milestone:
Comp
> Sander van Grieken wrote:
That may be, but despite that I need a daily package for kernel I can
point people
to.
Actually blocking current stable kernel from users by not packaging it,
which seems
to
be the case, is completely backwards.
>>> That may be the ca
Sander van Grieken wrote:
>>> That may be, but despite that I need a daily package for kernel I can point
>>> people to.
>>> Actually blocking current stable kernel from users by not packaging it,
>>> which seems to
>>> be the case, is completely backwards.
>> That may be the case, and you defint
#2029: Class 0 SMS wrongly decoded (no UTF-8?)
+---
Reporter: vnevoa |Owner: openmoko-devel
Type: defect | Status: new
Priority: normal |Milestone:
Comp
>>That may be, but despite that I need a daily package for kernel I can point
>>people to.
>> Actually blocking current stable kernel from users by not packaging it,
>> which seems to
>> be the case, is completely backwards.
>
> That may be the case, and you defintely should be able to point expe
On Wednesday 24 September 2008, Andy Green wrote:
> Somebody in the thread at some point said:
> | On Wed, Sep 24, 2008 at 08:59, Andy Green <[EMAIL PROTECTED]> wrote:
> |> Clearly that doesn't have the patch.
> |>
> |> This from today doesn't have it either.
>
> http://downloads.openmoko.org/repos
>That may be, but despite that I need a daily package for kernel I can point
>people to. Actually blocking current stable kernel from users by not
>packaging it, which seems to be the case, is completely backwards.
That may be the case, and you defintely should be able to point experienced
alp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| It's up the the person in charge of testing the linux-openmoko bitbake
| recipe to determine what the latest stable version in the feeds should
| be by updating that sane-srcrevs.inc file (after booting an
Andy Green wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Somebody in the thread at some point said:
> | Andy Green wrote:
> |> It used to be that our kernel packages followed our stable kernel git
> daily.
> |>
> |> But the hash on that one tells it is stuck at Aug 23 patchlevel...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Andy Green wrote:
|> It used to be that our kernel packages followed our stable kernel git
daily.
|>
|> But the hash on that one tells it is stuck at Aug 23 patchlevel...
|
| Yet another reason why the openm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Wed, Sep 24, 2008 at 08:59, Andy Green <[EMAIL PROTECTED]> wrote:
|> Clearly that doesn't have the patch.
|>
|> This from today doesn't have it either.
|>
|>
http://downloads.openmoko.org/repository/testi
On Wed, Sep 24, 2008 at 08:59, Andy Green <[EMAIL PROTECTED]> wrote:
> Clearly that doesn't have the patch.
>
> This from today doesn't have it either.
>
> http://downloads.openmoko.org/repository/testing/om-gta02/kernel-image-2.6.24_2.6.24+gitr105+a1e97c611253511ffc2d8c45e3e6d6894fa03fa3-r2_om-gta
Andy Green wrote:
> It used to be that our kernel packages followed our stable kernel git daily.
>
> But the hash on that one tells it is stuck at Aug 23 patchlevel...
Yet another reason why the openmoko autobuilder configuration should be
documented and published somewhere.
As an example, the p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|> There is a patch that should be in tomorrow's kernels that addresses
|> this, at least it gets my Sandisk 8GB SDHC recognized, please let me
|> know if it helped or not.
|
| Should it be included in this ke
35 matches
Mail list logo
