As far as I can tell version 1.3.6-4 is in testing (not 1.3.6-3 as per message), it got into testing 5 days ago, and this version has closed the bug.