Bug#742004: perltidy.LOG file left behind

2014-04-08 Thread Russ Allbery
Don Armstrong writes: > On Tue, 18 Mar 2014, Russ Allbery wrote: >> I looked into this further. The problem is that Perl::Tidy now always >> attempts to create a log file in the current directory unless told to >> create it elsewhere with the logfile parameter to its constructor. >> (There doesn'

Bug#742004: perltidy.LOG file left behind

2014-04-07 Thread Don Armstrong
On Tue, 18 Mar 2014, Russ Allbery wrote: > I looked into this further. The problem is that Perl::Tidy now always > attempts to create a log file in the current directory unless told to > create it elsewhere with the logfile parameter to its constructor. > (There doesn't seem to be a way to tell it

Bug#742004: Info received (Bug#742004: perltidy.LOG file left behind)

2014-03-28 Thread Steven Hancock
This is fixed in version 20140328 at CPAN. On Wed, Mar 19, 2014 at 7:21 AM, Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > Thank you for the additional information you have supplied regarding > this Bug report. > > This is an automatically generated reply to let you know your messa

Bug#742004: Info received (Bug#742004: perltidy.LOG file left behind)

2014-03-25 Thread Steven Hancock
This bug has been traced to a memoization update which was added to speed up perltidy. A temporary workaround is to use --no-memoize, but I should have a fixed version on CPAN in a few days. Steve On Wed, Mar 19, 2014 at 7:21 AM, Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > Than

Bug#742004: perltidy.LOG file left behind

2014-03-19 Thread Steven Hancock
Don, I'll look into this and try to make a general fix. I'll try to get it by next week and will let you know. Thanks, Steve On Tue, Mar 18, 2014 at 4:53 PM, Don Armstrong wrote: > Steve: bringing you in on this; it appears perltidy now creates a > perltidy.LOG file, which causes a few problem

Bug#742004: perltidy.LOG file left behind

2014-03-18 Thread Don Armstrong
Steve: bringing you in on this; it appears perltidy now creates a perltidy.LOG file, which causes a few problems in Debian; see https://bugs.debian.org/742004 for the full saga. On Tue, 18 Mar 2014, Russ Allbery wrote: > I looked into this further. The problem is that Perl::Tidy now always > attem

Bug#742004: perltidy.LOG file left behind

2014-03-18 Thread Russ Allbery
Control: reassign -1 libperl-critic-perl Russ Allbery writes: > 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 per

Bug#742004: perltidy.LOG file left behind

2014-03-17 Thread Russ Allbery
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.L