Hi, On 7 Nov 2015 2:53 pm, Jan Niehusmann <j...@gondor.com> wrote: > On Sat, Nov 07, 2015 at 02:30:09PM +0000, 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
