i just rolled a package based on cherry-picking that patch from upstream. this is not enough to fix the problem.
there is something else between 2.2.1 and that revision that fixes something else...
one thing to note, though: before that patch, nothing works at all.
i just rolled a package based on cherry-picking that patch from upstream. this is not enough to fix the problem.
there is something else between 2.2.1 and that revision that fixes something else...
one thing to note, though: before that patch, nothing works at all.