[Debian-astro-maintainers] Bug#915163: closed by Ole Streicher <olebole at debian.org> (Bug#915163: fixed in montage 6.0+dfsg-2)
Helmut Grohne
helmut at subdivi.de
Sun Dec 2 19:04:13 GMT 2018
On Sun, Dec 02, 2018 at 02:40:08PM +0100, Ole Streicher wrote:
> after looking a bit closer, I forwarded this to upstream. I am afraid
> that there is not too much else I could do: locally patching all lines
> in the affected Makefiles is not really maintainable. And it looks that
> this hides some errors that may be safely ignored; so one really would
> have to go through the whole build chain to check. Let's see what I get
> together with upstream.
I agree with all of that (having patched it myself).
> Policy 4.6 seems (for me) however only to address self-written Makefiles
> ("Every time *you* put more than one shell command...") - f.e. d/rules.
> A compromise would be to provide a list of all required files and to
> compare this with the actual build, letting the build fail on failure.
I read that "you" as "one" addressing the whole software, but picking on
the wording doesn't move us forward. Forwarding the issue upstream is a
good step forward. Thank you. Checking the resulting files goes into the
right direction, but only solves part of the problem: When your build
fails, the last thing you see (with -j1) usually is the actual failure.
So your approach won't improve the build failure experience.
I'm in favour of coordinating this with upstream. That should be the
most maintainable route and should have the best cost/benefit ration (if
upstream cooperates).
Helmut
More information about the Debian-astro-maintainers
mailing list