Bug#1005086: Please package Perl::Critic::Community

[Russ Allbery]

Package: libperl-critic-freenode-perl
Version: 0.033-1
Severity: normal
X-Debbugs-Cc: rra at debian.org

Perl::Critic::Freenode has become Perl::Critic::Community, which
also means that all of the policies that it installs have been
renamed to Community::* from Freenode::*.

Unfortunately, perlcritic produces a mandatory warning when one
suppresses an unknown policy in perlcriticrc, which makes this
awkward.  Since Debian unstable has the old package and old policy
names, but installing Perl::Critic::Freenode from CPAN (in CI, for
instance) will install the current version with the Community names,
there is no way to write a perlcriticrc suppressing those policies
and have it work in both environments right now.

Could you therefore prioritize packaging Perl::Critic::Community?
I can then switch to the Community::* names when developing on
Debian unstable/testing.

Thanks!


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'unstable-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.15.0-3-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libperl-critic-freenode-perl depends on:
ii  libpath-tiny-perl                                        0.122-1
ii  libperl-critic-perl                                      1.140-1
ii  libperl-critic-policy-variables-prohibitlooponhash-perl  0.008-1
ii  libperl-critic-pulp-perl                                 99-1
ii  libppi-perl                                              1.271-1
ii  perl                                                     5.32.1-6
ii  perl-base [libscalar-list-utils-perl]                    5.32.1-6

libperl-critic-freenode-perl recommends no packages.

libperl-critic-freenode-perl suggests no packages.

-- no debconf information