Re: m68k packages lagging -- manual uploads?
On Thu, Sep 08, 2005 at 04:34:47PM +0200, Ingo Juergensmann wrote:
> On Thu, Sep 08, 2005 at 04:28:44PM +0200, Loïc Minier wrote:
>
> > It seems quite a lot of m68k builds are missing for packages for the
> > GNOME 2.10 transition. Looking at:
> > <http://buildd.debian.org/stats/graph-week-big.png>
> > ... it seems m68k has a big backlog.
>
> Yes, indeed...
>
> http://unstable.buildd.net/buildd/m68k_stats says, m68k has roughly about
> 300 packages backlog, slightly growing when looking at
> http://unstable.buildd.net/buildd/m68k_stats.png
>
> > Can some additional buildds be brought online? Or maybe should some
> > manual builds take place?
Manual builds (on the machines that already run a buildd) would slow things
down only even more. It would help though, if people would not upload
packages like crazy. Or, when they upload, take care that they actually
build instead of wasting hours and then failing with know gcc-4.0 bugs (ie
using -O3 is currently not recommended for m68k, -O2 usually works), or,
even worse, fail at the last minute, as just happened on my mac after 6
hours building:
dh_fixperms -pdigikamimageplugins
chown: cannot access `debian/digikamimadebian/digikamimageplugins/usr/share/locale/fr/LC_MESSAGES/digikamimageplugin_superimpose.mo':
No such file or directory
chown: cannot access `TERM=unknown': No such file or directory
dh_fixperms: command returned error code
make: *** [binary-fixup/digikamimageplugins] Error 1
I think we will just have to wait, once everybody has uploaded packages for
the C++ transition, the gnome transition, and every other transition, plus
two new uploads for packaging bugs introduced by the previous uploads,
things will settle down again.
> It would be nice, when the existing buildds would be brought back online,
> such as akire and zot (although zot is not the speediest). Christian
> Steigies added a new 66 MHz 060 (garkin) buildd lately, but that suffers
> from some problems (having only a serial link f.e.).
garkin has no problems (unless building postgresql), thank you very much. It
just happened to get linux-2.6 to build and I decided to let it have it
instead of cross-compiling it again. It seems it will crunch away another
day or two, which is a good stress test for the machine, as well as a good
test to see if this package actually builds natively. So far I have always
cross-compiled linux-2.6. I guess the other buildds just have some packages
that take a while to build, my mac seems to be crunching on one C file since
18 hours... now if the slower buildds, and a couple of the fast ones, would
get smaller packages to build preferentially, things might not look that
bad.
But then, wasn't m68k reduced to second class recently?
Christian
Reply to: