Quoting Christian PERRIER (firstname.lastname@example.org): > Interesting question. I was indeed convinced that the patch made its > way to 3.6 but it apparently didn't. Upstream bug tracker doesn't say > a word about 3.6 or about the patch not being relevant for 3.6. > > I'm checking this with upstream....but it probably just got forgotten, > so, yes, 3.6 could be affected by this bug. I uploaded a fixed package in s-p-u. On the other hand, I re-prodded upstream so that the fix is included in the soon-to-come 3.6.2 release.
Description: Digital signature