Hello Sebastian Andrzej Siewior. On Thu, Nov 03, 2016 at 08:48:04PM +0100, Sebastian Andrzej Siewior wrote: > control: retitle: -1 fetchmail: FTBFS if building in parallel > > On 2016-11-03 07:45:16 [+0100], Andreas Henriksson wrote: > > Hello Kurt Roeckx. > Hi, > > > The failure in this build log didn't look like it was really openssl > > related. > > I've tried rebuilding the package which succeded for me. > > > > Could you please double-check here and possibly close this bug report > > if there's no issue? > > fetchmail builds against openssl 1.1.0. So we are good here. > fetchmail fails to build with -j4. > What do we do now? I retitled the bug. Can you reproduce this on your > end?
Disclaimer: I'm not the maintainer. (And your retitle seems to have failed? One too many : after retitle?) (And as already mentioned to Kurt, you might want to unblock the openssl transition as well as this bug is not related to openssl.) It seems build-arch depends on configure-stamp and build-stamp. The latter two gets executed in parallel which results in build-stamp getting executer before configure-stamp and thus the failure. Since the fetchmail packaging currently uses a deprecated debhelper compat level 7, preferrably it would get updated to a current level (and switched to use the debhelper sequencer while at it). While doing that upgrading/cleanup work on the packaging this bug will likely go away. Another (quick and dirty) option would be to completely disable parallel execution of debian/rules, eg. by adding ".NOTPARALLEL:". Another option that could also work is to make the build-stamp target depend on configure-stamp.... hopefully fixes the parallelism bug and probably a theoretically correct change no matter what. Regards, Andreas Henriksson PS. Not volunteering for any of the above myself.
