Hi, 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. 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
