This queue is for tickets about the Spreadsheet-ParseExcel CPAN distribution.
Maintainer(s)' notes
If you are reporting a bug in Spreadsheet::ParseExcel here are some pointers
1) State the issues as clearly and as concisely as possible. A simple program or Excel test file (see below) will often explain the issue better than a lot of text.
2) Provide information on your system, version of perl and module versions. The following program will generate everything that is required. Put this information in your bug report.
#!/usr/bin/perl -w
print "\n Perl version : $]";
print "\n OS name : $^O";
print "\n Module versions: (not all are required)\n";
my @modules = qw(
Spreadsheet::ParseExcel
Scalar::Util
Unicode::Map
Spreadsheet::WriteExcel
Parse::RecDescent
File::Temp
OLE::Storage_Lite
IO::Stringy
);
for my $module (@modules) {
my $version;
eval "require $module";
if (not $@) {
$version = $module->VERSION;
$version = '(unknown)' if not defined $version;
}
else {
$version = '(not installed)';
}
printf "%21s%-24s\t%s\n", "", $module, $version;
}
__END__
3) Upgrade to the latest version of Spreadsheet::ParseExcel (or at least test on a system with an upgraded version). The issue you are reporting may already have been fixed.
4) Create a small example program that demonstrates your problem. The program should be as small as possible. A few lines of codes are worth tens of lines of text when trying to describe a bug.
5) Supply an Excel file that demonstrates the problem. This is very important. If the file is big, or contains confidential information, try to reduce it down to the smallest Excel file that represents the issue. If you don't wish to post a file here then send it to me directly: jmcnamara@cpan.org
6) Say if the test file was created by Excel, OpenOffice, Gnumeric or something else. Say which version of that application you used.
7) If you are submitting a patch you should check with the maintainer whether the issue has already been patched or if a fix is in the works. Patches should be accompanied by test cases.
Asking a question
If you would like to ask a more general question there is the Spreadsheet::ParseExcel Google Group.
Owner: |
Nobody in particular
|
Requestors: |
SAPER [...] cpan.org
|
Cc: |
|
AdminCc: |
|
|
Severity: |
Important |
Broken in: |
(no value)
|
Fixed in: |
(no value)
|
|
Mon Jan 08 04:48:36 2007
SAPER [...] cpan.org - Ticket created
Hello,
Makefile.PL lacks some of Spreadsheet::ParseExcel prerequisites,
Jcode and Unicode::Map, leading to compilation errors during the
tests:
t/basic.....NOK 4/8
# Failed test 'use Spreadsheet::ParseExcel::FmtJapan;'
# at t/basic.t line 10.
# Tried to use 'Spreadsheet::ParseExcel::FmtJapan'.
# Error: Can't locate Jcode.pm in @INC
# BEGIN failed--compilation aborted at t/basic.t line 10.
# Compilation failed in require at (eval 22) line 2.
# BEGIN failed--compilation aborted at (eval 22) line 2.
After manually installing these modules, all tests successfully pass.
Regards,
--
Close the world, txEn eht nepO.
Sat Mar 31 06:55:09 2007
SZABGAB [...] cpan.org - Correspondence added
Starting from 0.29 we try to skip tests that has prereq which aren't met
in the current installation.
thanks for submitting this bug report
Gabor
Sat Mar 31 06:55:11 2007
The RT System itself - Status changed from 'new' to 'open'
Sat Mar 31 06:55:13 2007
SZABGAB [...] cpan.org - Status changed from 'open' to 'resolved'