Re: MARC::Charset 1.34

2013-02-11 Thread Galen Charlton
Hi, On Mon, Feb 11, 2013 at 12:12 PM, Leif Andersson wrote: > So - however it happend - the "corrupt" file had been gzipped twice. > > At least a partly explanation to this mystery :) > Wild. Thanks for chasing down further. Regards, Galen -- Galen Charlton gmcha...@gmail.com

Re: MARC::Charset 1.34

2013-02-11 Thread Leif Andersson
Ah, I still had one of those bad archives left. So I could see that the file size differed. The bad .tar.gz was 182.056 bytes The good 191.865 And after unzipping the corrupt file I got a .tar file of size 191.865 ! gzipped twice? Well, I renamed the unzipped corrupt .tar file to .tar.gz And now

Re: MARC::Charset 1.34

2013-02-11 Thread Galen Charlton
Hi, On Mon, Feb 11, 2013 at 11:52 AM, Leif Andersson wrote: > Corrupt tar file RESOLVED. > Thanks for the update. I'm inclined to agree with your guess that a mirror was corrupt. Out of curiosity, are you using ActiveState or Strawberry? Regards, Galen -- Galen Charlton gmcha...@gmail.com

Re: MARC::Charset 1.34

2013-02-11 Thread Leif Andersson
Corrupt tar file RESOLVED. But here's the background anyway. I downloaded the MARC-Charset-1.34.tar.gz to Windows7. "The archive is corrupt" was the error message from WinRAR on Windows. Other utils on the same platform agreed. I made a second download with the same result.

Re: MARC::Charset 1.34

2013-02-11 Thread Galen Charlton
Hi, On Mon, Feb 11, 2013 at 10:50 AM, Leif Andersson wrote: > It gunzips fine, but then there seems to be something wrong with the tar > file... > Could you elaborate? In particular, what platform are you on and what error message are you getting? I tried installing MARC::Charset 1

Re: MARC::Charset 1.34

2013-02-11 Thread Leif Andersson
It gunzips fine, but then there seems to be something wrong with the tar file... /Leif Andersson Stockholm University Library

MARC::Charset 1.34

2013-02-11 Thread Galen Charlton
Hi, I have uploaded version 1.34 of MARC::Charset to CPAN. This is a minor bugfix and portability release. Changes from 1.33 are: - RT#83257: use AnyDBM_File rather than hardcode GDBM_File To improve portability, use AnyDBM_File to select a DBM rather than rely on GDBM_File. GDBM_File app