Re: [Slightly OT] Interpreting cpan-testers failures

2008-03-21 Thread Michael Carman
Andreas J. Koenig wrote: So it seems you have the backward slashes in the archive which may or may not be correct. Confirmed! I installed the gnuwin32 versions of zip, unzip, and zipinfo. The IZArc created archive uses backslashes (visible in zipinfo) and unzip complains loudly about them. Ve

Re: [Slightly OT] Interpreting cpan-testers failures

2008-03-21 Thread Andreas J. Koenig
> On Fri, 21 Mar 2008 08:34:15 -0500, Michael Carman <[EMAIL PROTECTED]> > said: > The common theme is this: > > Output from '/usr/bin/make': > !!

Re: [Slightly OT] Interpreting cpan-testers failures

2008-03-21 Thread David Golden
On Fri, Mar 21, 2008 at 9:37 AM, Shawn Boyette ☠ <[EMAIL PROTECTED]> wrote: > Have you tried unpacking your own distro to see what it looks like? More to the point, unpack your distro with the CPAN shell: $ cpan cpan> look Tk::DiffText That will drop you into the directory that CPAN has u

Re: [Slightly OT] Interpreting cpan-testers failures

2008-03-21 Thread Shawn Boyette ☠
It's been a lng time since I've made a zipfile, but I seem to remember that you had to explicitly tell the old DOS PKZIP to retain directory structure. That is: its default was to flatten everything down to a simple pool of files. This was, however, forever ago. Have you tried unpacking your o

[Slightly OT] Interpreting cpan-testers failures

2008-03-21 Thread Michael Carman
I apologize for the somewhat OT posting, but I need some help. I uploaded a new version of a module (Tk-DiffText version 0.18) to CPAN and have been getting failure reports from CPAN-Testers ever since. The common theme is this: -