On Tue, Jul 03, 2018 at 12:29:00PM +0200, Alberto Gonzalez Iniesta wrote:
> Have you tested your assertion? Because if ./configure fails, MCONFIG is
> not created and the build (make) fails:
That was a general statement. I think it doesn't really matter whether
it practically does cause misbuilds:
On Fri, Sep 15, 2017 at 05:17:44PM +0200, Helmut Grohne wrote:
> Source: netkit-tftp
> Version: 0.17-18.1
> Severity: serious
> Justification: policy 4.6
>
> netkit-tftp's debian/rules does not trap errors from ./configure. In
> case ./configure fails, the build continues. This can produces
> appa
Hello, Raphael.
Dead upstream requires few updates to a package. Anyway, I was just
looking into that now.
Regards,
Alberto
On Tue, Jul 03, 2018 at 09:44:46AM +0200, Raphael Hertzog wrote:
> Hello Alberto,
>
> it's been 8 years that you haven't touched netkit-tftp and the package
> has been re
Hello Alberto,
it's been 8 years that you haven't touched netkit-tftp and the package
has been removed from Debian testing due to the bug I'm replying to.
Can you take care of fixing the bug and/or properly orphaning the package
if you are no longer interested in it?
Regards,
On Fri, 15 Sep 201
Source: netkit-tftp
Version: 0.17-18.1
Severity: serious
Justification: policy 4.6
netkit-tftp's debian/rules does not trap errors from ./configure. In
case ./configure fails, the build continues. This can produces
apparently successful misbuilds and is prohibited by the Debian policy
in section 4
5 matches
Mail list logo
