Bug#843052: fixed in libterm-filter-perl 0.03-2

[Santiago Vila]

Two years ago, I said:

> Please note that failure rate for this one is extremely low, maybe in
> the order of 1%.

No longer the case. Now I can reproduce this on several different
types of virtual machines, and the failure rate is quite bad:

Status: failed      libterm-filter-perl_0.03-2_amd64-20181208T225252.983Z
Status: failed      libterm-filter-perl_0.03-2_amd64-20181212T234627.087Z
Status: failed      libterm-filter-perl_0.03-2_amd64-20181212T235157.458Z
Status: failed      libterm-filter-perl_0.03-2_amd64-20181212T235330.286Z
Status: failed      libterm-filter-perl_0.03-2_amd64-20181212T235831.811Z
Status: failed      libterm-filter-perl_0.03-2_amd64-20181213T000803.364Z
Status: failed      libterm-filter-perl_0.03-2_amd64-20181223T222252.071Z
Status: successful  libterm-filter-perl_0.03-2_amd64-20190104T071946.240Z
Status: failed      libterm-filter-perl_0.03-2_amd64-20190118T041049.954Z
Status: failed      libterm-filter-perl_0.03-2_amd64-20190127T211613.692Z
Status: failed      libterm-filter-perl_0.03-2_amd64-20190205T055441.205Z
Status: failed      libterm-filter-perl_0.03-2_amd64-20190218T092305.301Z
Status: failed      libterm-filter-perl_0.03-2_amd64-20190305T034945.695Z
Status: failed      libterm-filter-perl_0.03-2_amd64-20190315T182215.637Z
Status: failed      libterm-filter-perl_0.03-2_amd64-20190327T182755.610Z
Status: failed      libterm-filter-perl_0.03-2_amd64-20190410T143921.022Z

I can offer ssh access to a machine where this happens easily, please
contact me privately for details.

Thanks.