Heimdal Patches Re: [PATCH] Some coverity fixes

[Volker Lendecke]

On Sat, May 09, 2015 at 08:07:38AM +0100, Andrew Bartlett wrote:
> Actually, they really do hurt.  I am working on updating Heimdal (it is
> a long, thankless task, but still clearly required), I've had to drop
> almost all of the 'fix the build' patches so far, because they simply
> don't apply.  

Does this mean we will have to go through a load of build failures
again? We seem to have much stricter warning levels than heimdal has,
and I do see many failures over and over again with the O3 developer
build. This also is painful.

I request to instrument waf such that in the heimdal tree we allow every
warning under the sun and not fail at all. Please see a new heimdal
import NACKed by me already if this is not met.

Also, I will modify our Coverity build such that we completely ignore
errors there.

> To ensure we don't just loose them when we rebase (and the rebase is
> going to be so large you would never notice), I really do need patches
> to Heimdal to be first submitted as github pull requests into Heimdal
> master.  We have tools to try and pick up the local patches, but they
> are no longer very helpful because we have a mix of patches that do
> apply, don't apply upstream divergence or are already upstream.

Okay, will heimdal maintain a release stream based on our version for us,
with a latency measured in months not years? Much like Michael maintains
ctdb-1.0.114 forever?

Volker

-- 
SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
phone: +49-551-370000-0, fax: +49-551-370000-9
AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen
http://www.sernet.de, mailto:kontakt at sernet.de