Hi Sébastien, On 02.01.2018 14:37, Sébastien Villemot wrote: > On Sun, Dec 31, 2017 at 07:46:54PM +0100, Oliver Heimlich wrote: >> I have one particular question regarding octave-interval. The build produces >> two binary packages: octave-interval and octave-interval-doc. The latter is >> architecture "all" and multi-arch "foreign". However, it is build by all >> architectures. >> >> Since version 3.1.0 building the documentation takes a lot of time and >> timeouts on some build environments, e. g., armel. Of course this should be >> optimized upstream. >> >> Would it make sense to build octave-interval-doc only on few architectures >> where the build environment has more resources? ... > In your case, you want octave-interval to be built by the > build-arch/binary-arch targets, and octave-interval-doc by the > build-indep/binary-indep targets. Splitting the build seems unnecessarily complicated. I have pushed a patch, which should reduce the build time and hopefully makes the package build on armel and mips64el again. Currently these builds are “killed ... after 150 minutes of inactivity”. I assume that the build failures block testing migrations for the package right now, thus I'd suggest to make a new upload of octave-interval. Oliver
Attachment:
signature.asc
Description: OpenPGP digital signature