> Unfortunately, this does not say what the problem was. (Please let me > refer you to devref 6.3, that reads: "When referring to bugs, don't > assume anything. Say what the problem was, how it was fixed, and > append the closes: #nnnnn string.".) > But well, this was uploaded already, so whatever..
thanks, I need to improve the quality of my changelog entries. I tried to be as synthetic as possible but sometimes it is too much :) > Other than that, I'm not good enough at Python/Qt to pretend having > reviewed the code changes in full details, but they do seem pretty > minimal, and limited to fixing the bug, so it should be good enough > for Wheezy. I tried my best with the upstream to provide a patch less invasive as possible to remain understandable by the release team in the smaller amount of time. Cheers, Fred -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/a2a20ec3b8560d408356cac2fc148e5358e1a...@sun-dag1.synchrotron-soleil.fr
