February 2007 - Koha-bugs - lists.koha-community.org

[Bug 1024] Reservoir imports without ISBN fail
by bugzilla-daemon＠daddy.katipo.co.nz 02 Feb '07

02 Feb '07

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1024 rch(a)liblime.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Comment #2 from rch(a)liblime.com 2007-02-02 12:36 ------- further tests indicate this is fixed. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1284] Typo in Install.pm prevents checking for GD::Barcode
by bugzilla-daemon＠daddy.katipo.co.nz 01 Feb '07

01 Feb '07

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1284 mjr(a)ttllp.co.uk changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Comment #1 from mjr(a)ttllp.co.uk 2007-02-02 10:37 ------- That shouldn't be there. Fix committed to CVS. Thanks for the report. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1284] New: Typo in Install.pm prevents checking for GD::Barcode
by bugzilla-daemon＠daddy.katipo.co.nz 01 Feb '07

01 Feb '07

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1284 Summary: Typo in Install.pm prevents checking for GD::Barcode Product: Koha Version: 2.2.7 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Installation AssignedTo: mjr(a)ttllp.co.uk ReportedBy: sylvar(a)gmail.com QAContact: koha-bugs(a)nongnu.org Note the misspelling 'Barcorde' in line 850 of Install.pm: unless (eval {require GD::Barcorde}) { if ($#missing>=0) { # only when $#missing >= 0 so this isn't fatal push @missing,"You will need GD::Barcode for the new barcode generator"; } } ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0