Re: FSO fails and fails

2009-02-13 Thread Rod Whitby
Daniel Spies wrote: > I knew about downloads.freesmartphone.org, but as you can see there is no > build after 18th Jan. and one build for M5. > downloads.openmoko.org has got the images indeed, thanks! Thanks for reporting it - I've been concentrating on FSO milestone5 feeds and updated images (h

Re: FSO fails and fails

2009-02-11 Thread Daniel Spies
On Thu, 12 Feb 2009 14:33:46 +1030, Rod Whitby wrote: > Daniel Spies wrote: >> I wonder if anyone would be interested in daily automated builds as I >> build >> on my root server anyway? >> I could also do some other builds if s/o needs it... > > There are already FSO automated builds on downloa

Re: FSO fails and fails

2009-02-11 Thread Rod Whitby
Daniel Spies wrote: > I wonder if anyone would be interested in daily automated builds as I build > on my root server anyway? > I could also do some other builds if s/o needs it... There are already FSO automated builds on downloads.freesmartphone.org (maintained by me) and downloads.openmoko.org

Re: Re: FSO fails and fails

2009-02-11 Thread Daniel Spies
On Tue, 10 Feb 2009 23:39:42 +0100, Daniel Spies wrote: > Oleg Sadov wrote on Tuesday 10 February 2009: >> >> You may try define the list of locales in GLIBC_GENERATE_LOCALES >> variable in your fso-milestone5/conf/local.conf without es_NI locale, >> for example: >> >> GLIBC_GENERATE_LOCALES = "e

Re: Re: FSO fails and fails

2009-02-10 Thread Daniel Spies
Oleg Sadov wrote on Tuesday 10 February 2009: > > You may try define the list of locales in GLIBC_GENERATE_LOCALES > variable in your fso-milestone5/conf/local.conf without es_NI locale, > for example: > > GLIBC_GENERATE_LOCALES = "en_US.UTF-8 ru_RU.UTF-8" > For now the build of unstable with ENA

Re: FSO fails and fails

2009-02-10 Thread Oleg Sadov
В Втр, 10/02/2009 в 15:17 +, Arigead пишет: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Al Johnson wrote: > > Response below... > > > > On Tuesday 10 February 2009, Daniel Spies wrote: > >> On Tue, 10 Feb 2009 09:53:46 +0100, Daniel Spies > >> > >> > >> wrote: > >>> On Mon, 9 Feb

Re: FSO fails and fails

2009-02-10 Thread Arigead
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Al Johnson wrote: > Response below... > > On Tuesday 10 February 2009, Daniel Spies wrote: >> On Tue, 10 Feb 2009 09:53:46 +0100, Daniel Spies >> >> >> wrote: >>> On Mon, 9 Feb 2009 15:18:35 +, Al Johnson >>> >>> wrote: I was having a simil

Re: FSO fails and fails

2009-02-10 Thread Al Johnson
Response below... On Tuesday 10 February 2009, Daniel Spies wrote: > On Tue, 10 Feb 2009 09:53:46 +0100, Daniel Spies > > > wrote: > > On Mon, 9 Feb 2009 15:18:35 +, Al Johnson > > > > wrote: > >> I was having a similar experience, so I made a new directory and started > >> from > >> scratch

Re: FSO fails and fails

2009-02-10 Thread Daniel Spies
On Tue, 10 Feb 2009 09:53:46 +0100, Daniel Spies wrote: > On Mon, 9 Feb 2009 15:18:35 +, Al Johnson > wrote: >> >> I was having a similar experience, so I made a new directory and started >> from >> scratch. make fso-gta02-unstable-image has just completed building again, >> and >> milesto

Re: FSO fails and fails

2009-02-10 Thread Daniel Spies
On Mon, 9 Feb 2009 15:18:35 +, Al Johnson wrote: > > I was having a similar experience, so I made a new directory and started > from > scratch. make fso-gta02-unstable-image has just completed building again, > and > milestone5 built fine a couple of days ago. This is the second or third >

Re: FSO fails and fails

2009-02-09 Thread Al Johnson
On Monday 09 February 2009, Daniel Spies wrote: > Hi, > > I am a little bit confused about the FSO distibution. I am trying to > compile testing branch since January without success. First I got the weird > localization issue and now other build errors. As far as I could see it > from bugzilla the

FSO fails and fails

2009-02-09 Thread Daniel Spies
Hi, I am a little bit confused about the FSO distibution. I am trying to compile testing branch since January without success. First I got the weird localization issue and now other build errors. As far as I could see it from bugzilla the issues are known and also the build logs on [1] are failin