Hi Russell, I have committed changes upstream that should resolve both of the problems that you reported. The changes are a much more extensive than I expected. Mainly due to a mixture of necessary and arguably non-essential clean-ups. Thus a backport to 1.18 seems tricky. And 1.17 worse. So I'd rather just wait until 1.19 is released to close this bug. Let me know if this will be a problem for you.
The relevant changes can be found at: http://hg.vergenet.net/perdition/perdition/rev/12f2b53f08c4 http://hg.vergenet.net/perdition/perdition/rev/bd513c35636b http://hg.vergenet.net/perdition/perdition/rev/2ed2e5395779 http://hg.vergenet.net/perdition/perdition/rev/f21dd04b668f http://hg.vergenet.net/perdition/perdition/rev/8753e200e5ec http://hg.vergenet.net/perdition/perdition/rev/0469d32b52e7 http://hg.vergenet.net/perdition/perdition/rev/e1b850fa5cd4 http://hg.vergenet.net/perdition/perdition/rev/1a687661ae08 http://hg.vergenet.net/perdition/perdition/rev/3b96a69dbce1 http://hg.vergenet.net/perdition/perdition/rev/4920a57fa03f http://hg.vergenet.net/perdition/perdition/rev/7d8a43fe967c http://hg.vergenet.net/perdition/perdition/rev/7eb28143e8c8 http://hg.vergenet.net/perdition/perdition/rev/103e4c5af59f http://hg.vergenet.net/perdition/perdition/rev/5470fbf15b6b http://hg.vergenet.net/perdition/perdition/rev/4ddbaf5c3aa3 http://hg.vergenet.net/perdition/perdition/rev/b2baf2bcd467 http://hg.vergenet.net/perdition/perdition/rev/f48bc95a78aa http://hg.vergenet.net/perdition/perdition/rev/f8711d197450 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
