On 2017-09-12 17:23, Holger Levsen wrote: > On Tue, Sep 12, 2017 at 04:52:22PM +0200, Boud Roukema wrote:
>> It seems to me that the problem is a missing "esac\n;;" (earlier than >> line 62). I've attached a patch that works for me on a dummy file. > > thanks a lot for this nice bug report, I've now deployed the fix and > rescheduled > 19126 affected packages in 49 suites, which translates to 1007 in stretch, > 171 in buster, 1201 in sid and me being to lazy to do stats for those 46 other > suites. Holger, you missed the second half of Boud's fix, so add another ;; 23722fb34 really fix 42acc54048 4743d4aef p-r: make verbose messages more consistent Andreas PS: I don't know if we need such a verbose changelog for a feature just introduced in the previous patch series ... since the bug has never been in a release PPS: I don't know why this got mismerged and lost some lines when extracting that patch from my private devel tree - it's correct in my production HEAD
