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! […]
>
Hi,
On Sun, Nov 7, 2021 at 11:37 PM intrigeri wrote:
>
> The bug lies in the interaction between these 2 tools.
Yay, the problem was solved! [1] Will you please deploy the fix with a
little bit of urgency? Lintian's pipeline has been malfunctioning for
a little while. Thanks!
Kind regards,
Hi,
On Sun, Nov 7, 2021 at 11:37 PM intrigeri wrote:
>
> In combination with which version of perltidy?
I work on Lintian on stable but always depend on current versions of
perltidy and perlcritic. Without backports, I cherry-pick both when
Lintian's Salsa CI breaks for style. I currently have
Control: severity -1 important
Hi,
Felix Lechner (2021-11-03):
>> https://github.com/Perl-Critic/Perl-Critic/issues/925
>
> That has not seen any activity in over two years.
FWIW, there has been renewed activity a few days ago on the
corresponding PR:
Control: affects -1 lintian
Hi,
On Wed, Nov 3, 2021 at 12:49 AM intrigeri wrote:
>
>
> I can reproduce
Thanks for the research!
> https://github.com/Perl-Critic/Perl-Critic/issues/925
That has not seen any activity in over two years. Would you consider
marking the version in unstable as
Control: tag -1 + upstream
Control: forwarded -1 https://github.com/Perl-Critic/Perl-Critic/issues/925
Hi,
I can reproduce this even if I delete all lines from
lib/Lintian/Index/Item.pm (current master branch) except the first
5 ones:
# -*- perl -*-
# Lintian::Index::Item -- Representation of
Package: libperl-critic-perl
Severity: normal
Hi,
Perlcritic does not appear to use the latest version of perltidy, or
perhaps invokes it with different settings. In unstable, perlcritic
complains that files are not tidy even though perltidy just ran over
them.
Due to the large number of
7 matches
Mail list logo
