Bug#804331: mongrel2: FTBFS in jessie - FAILED: failed to verify m2-cert.pem

[James Cowgill]

Hi,

On 7 Nov 2015 2:12 pm, Jan Niehusmann  wrote:
> Version: 1.9.2-1 
>
> Hi James, 
>
> On Sat, Nov 07, 2015 at 01:06:31PM +, James Cowgill wrote: 
> > This happens because the certificate m2-cert.pem expired earlier this year. 
> > Upstream worked around it as part of this commit: 
>
> That fix is already present in debian since version 1.9.2-1. 

I know. I was wondering if it could be fixed in stable?

James

Bug#804331: mongrel2: FTBFS in jessie - FAILED: failed to verify m2-cert.pem

[James Cowgill]

Source: mongrel2
Version: 1.9.1-6
Severity: serious
Tags: jessie fixed-upstream

Hi,

The version of mongrel2 in jessie FTBFS due to this error in the testsuite:

> ERROR in test tests/cert_tests
> 
> RUNNING: ./tests/cert_tests
> FAILED: failed to verify m2-cert.pem

This happens because the certificate m2-cert.pem expired earlier this year.
Upstream worked around it as part of this commit:

https://github.com/mongrel2/mongrel2/commit/854bc486e0d06f7585edf79e398933d6818e521b

Thanks,
James

Bug#804331: mongrel2: FTBFS in jessie - FAILED: failed to verify m2-cert.pem

[Andreas Beckmann]

On Sat, 7 Nov 2015 15:53:12 +0100 Jan Niehusmann  wrote:
> problem". Is this really 'critical'?

Yes, being unable to build a package from stable in stable is RC.

> BTW, I placed the patched version of the package in the branch 'stable'
> of the git repository on alioth:

Looks minimal and a good candidate for jessie-pu.


Andreas

Bug#804331: mongrel2: FTBFS in jessie - FAILED: failed to verify m2-cert.pem

[Jan Niehusmann]

Hi,

On Sat, Nov 07, 2015 at 02:30:09PM +, James Cowgill wrote:
> I know. I was wondering if it could be fixed in stable?

Well, for stable I'd just disable the failing test, instead of backporting
the upstream fix. Commenting out the mu_assert line containing the error
message would be enough.

But why? If there's a need to do a rebuild, it's easy enough to do the
fix, then.

https://www.debian.org/doc/manuals/developers-reference/pkgs.html#upload-stable
lists three situations where an upload to stable would be reasonable.
The only one which may apply here is "a truly critical functionality
problem". Is this really 'critical'?

BTW, I placed the patched version of the package in the branch 'stable'
of the git repository on alioth:
http://anonscm.debian.org/cgit/users/jan/mongrel2.git/log/?h=stable

Jan

Bug#804331: mongrel2: FTBFS in jessie - FAILED: failed to verify m2-cert.pem

[James Cowgill]

Hi,

On 7 Nov 2015 2:53 pm, Jan Niehusmann  wrote:
> On Sat, Nov 07, 2015 at 02:30:09PM +, James Cowgill wrote: 
> > I know. I was wondering if it could be fixed in stable? 
>
> Well, for stable I'd just disable the failing test, instead of backporting 
> the upstream fix. Commenting out the mu_assert line containing the error 
> message would be enough. 
>
> But why? If there's a need to do a rebuild, it's easy enough to do the 
> fix, then. 

I'm trying to fix polarssl bug #801493 in jessie and the security team asked me 
to ensure all the rdeps still build in jessie. This was the only package that 
failed.

> https://www.debian.org/doc/manuals/developers-reference/pkgs.html#upload-stable
>  
> lists three situations where an upload to stable would be reasonable. 
> The only one which may apply here is "a truly critical functionality 
> problem". Is this really 'critical'? 

I don't know what the release team's opinion is, but a package which can't be 
built (and therefore can't be modified without hacking it) seems like a 
critical issue to me.

Thanks,
James