[Pkg-octave-devel] Processing of octave2.9_2.9.7-2_i386.changes

Christian T. Steigies cts at debian.org
Fri Aug 18 12:02:29 UTC 2006


On Fri, Aug 18, 2006 at 11:46:37AM +0200, Rafael Laboissiere wrote:
> * Christian T. Steigies <cts at debian.org> [2006-08-18 00:39]:
> 
> > Build needed 62:15:44, 163920k disk space
> 
> Thanks for bringing this to our attention.  I am looking at the issue now
> and if I find a reasonable way to avoid the docs being generated at build
> time, I will upload a new version of the package.

No hurry, the latest build is still running, we don't want to wast two days
of building, do we? If you find a fix, it is sufficient if it is included in
the next upload. Maybe doc building does not take that much time after all,
the buildd is still crunching on c++ code. As for the metafont runs, they
might actually have to be created for every build, since a "good" buildd is
cleaning up the chroot after the build, and since TeX is not build
essential, the compiled fonts might be removed as well. A "very good" buildd
actually starts every build from fresh chroot which has never seen a TeX
installation, but we don't do that on m68k, since creating the chroots takes
more time than simply removing all build-depends after the build.

Christian



More information about the Pkg-octave-devel mailing list