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

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

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

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

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

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

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

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

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

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.