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

Rafael Laboissiere rafael at debian.org
Fri Aug 18 09:46:37 UTC 2006

* Christian T. Steigies <cts at debian.org> [2006-08-18 00:39]:

> This source package landed on my m68k build a couple of days ago. When I
> checked the log of the previous build to find out how long the build might
> take, I noticed that a significant portion of the log consists of TeX
> messages:
> http://buildd.debian.org/fetch.php?&pkg=octave2.9&ver=2.9.7-1&arch=m68k&stamp=1155639465&file=log&as=raw
> I assume the files created there all end up in the various doc and info
> packages, but they are not part of the m68k build! I hope there is nothing
> arch specific in the docs, so they should not be part of it. But if these
> docs never get uploaded, why does my poor machine have to build those files?
> If the doc building could be moved to the binary-indep target, we would all
> benefit, unless you own stocks of my local utilities company. I don't know
> how much time is spent for the doc target, but it it just 10% of the build
> time (looks more like 50% of the space of the log), this could save us 6
> hours on certain machines:
> [...]
> 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.


More information about the Pkg-octave-devel mailing list