Bug#998367: perlcritic: "Code not tidy' after perltidy

[Axel Beckert]

Control: reassign -1 perltidy
Control: found -1 20220217-1
Control: affects -1 + libperl-critic-perl

Hi,

Felix Lechner wrote:
> > The bug lies in the interaction between these 2 tools.
> 
> Yay, the problem was solved! […]
> https://github.com/Perl-Critic/Perl-Critic/issues/925#issuecomment-1048340859

Actually that "fix" still would have needed code changes in Lintian
and other consumers. These code changes additionally would have had to
check the version of perltidy and behave differently based on the version.

But according to
https://github.com/Perl-Critic/Perl-Critic/issues/925#issuecomment-1194737842
the issue should be fixed "in the most recent release of Perl::Tidy
(v20220613 or later)" due to a changed default value which seemingly
no more needs to the above mentioned code changes.

So please update perltidy to the most recent upstream release.

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe at debian.org>, https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE