Package: perltidy
Version: 20180220-1
Severity: normal

Upstream has released 20181120, which improves perltidy's ability to
detect consecutive variable assignments that should be aligned.  This
unfortunately means that there is some code that passes with 20180220
and fails with 20181120 which, when fixed for 20181120, fails with
20180220.  This makes mismatches of versions particularly painful.

Since Travis-CI pulls directly from CPAN, this means that I have to
choose between skipping Travis-CI tests for perltidy (by way of
Perl::Critic), which I don't want to do because they're useful for
pull requests, and having tests fail on my local system.

Could you package the 20181120 release?  I'm also happy to help if you
would like.

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

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

Versions of packages perltidy depends on:
ii  perl  5.28.1-3

perltidy recommends no packages.

perltidy suggests no packages.

-- no debconf information

Reply via email to