Your message dated Wed, 23 Apr 2014 22:47:38 +0200
with message-id <[email protected]>
and subject line Re: Bug#742004: perltidy.LOG file left behind
has caused the Debian Bug report #742004,
regarding perltidy.LOG file left behind
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
742004: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742004
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libtest-perl-critic-perl
Version: 1.02-1
Severity: normal
This may acutally be a bug in Perl::Critic or perltidy, but since this
is the interface I'm calling, reporting it here.
With this upgrade:
[UPGRADE] perltidy:i386 20120701-1 -> 20130922-1
Test::Perl::Critic now leaves perltidy.LOG files behind in the current
directory after the test has completed. Since the results are all
reported via normal test results, this seems pointless, and it leaves
build clutter behind.
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.12-1-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libtest-perl-critic-perl depends on:
ii libperl-critic-perl 1.121-1
ii perl 5.18.2-2+b1
libtest-perl-critic-perl recommends no packages.
libtest-perl-critic-perl suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Tue, Apr 08, 2014 at 08:49:43AM -0700, Russ Allbery wrote:
> Don Armstrong <[email protected]> writes:
> > I've now uploaded a new version of perltidy which should not have this
> > problem.
>
> Thank you!
I interpret this to mean that the bug has been fixed, so I'm closing
#742004 accordingly.
Florian
--- End Message ---
