The debbuild of fuerte oneiric 386 has fallen behind and is in process rebuilding.  It's currently 6 hours into the build and chugging as expected. [1]  Unfortunately debbuilding is a slow process with it taking ~ 8 hours per arch.  If there's an error it sometimes can fall a full cycle behind, and depending on how many machines are turned on, sometimes we can't build all arches in parallel, making a cycle take up to 16 hours. 

Tully

[1] http://build.willowgarage.com/job/debbuild-build-debs-fuerte-oneiric-i386/820/


On Tue, May 15, 2012 at 1:09 AM, Stéphane Magnenat <stephane.magnenat@mavt.ethz.ch> wrote:
Hi Tully,

Thank you for these explanations, I now understand better the motivations behind the current system.

As gps_umd provides the definition of the "extended" gps messages and does not compile, it is a problem for dependencies. If the maintainer is on this list, maybe one should move the message definitions to their own stack to prevent dependency problems?

Our stack ethzasl_aseba compiles fine on fuerte excepted for oneiric_i386 [1], as it seems that some basic stacks are missing (like common). I guess it is a known problem, do you know when it will be fixed?


Thank you, kind regards,

Stéphane

[1] http://build.willowgarage.com/job/prerelease_fuerte_ethzasl_aseba_oneiric_i386/2/console


--
Dr Stéphane Magnenat
http://stephane.magnenat.net



--
Tully Foote
Systems Engineer
Willow Garage, Inc.
tfoote@willowgarage.com
(650) 475-2827