[Pkg-sql-ledger-discussion] Bug#675816: ledgersmb: Unable to upgrade from 1.2 db to 1.3 db

[Robert James Clay]

On Sun, 2012-06-03 at 10:06 -0400, Moshe Yudkowsky wrote:
> 
> Subject: ledgersmb: Unable to upgrade from 1.2 db to 1.3 db
> Package: ledgersmb
> Version: 1.3.15-2
> Severity: important
> 
> All my databases are 1.2 databases. I'm following the update 
> instructions for 1.3, using the "setup.pl" page via my browser.
> 
> The updates fail with an apache 500 error -- the db is created but all 
> the tables are empty. Re-running the update process does _not_ repair 
> the db, as might be expected.
> 
> While many errors show up, the final pre-500 errors in Apache are:
> 
> [Fri Jun 01 17:44:40 2012] [error] [client 127.0.0.1] LINE 1: SELECT 
> version FROM defaults, referer: http://localhost/ledgersmb/setup.pl
> [Fri Jun 01 17:44:40 2012] [error] [client 127.0.0.1]                ^ 
> at LedgerSMB/Database.pm line 310., referer: 
> http://localhost/ledgersmb/setup.pl
> [Fri Jun 01 17:44:43 2012] [error] [client 127.0.0.1] Directory index 
> forbidden by Options directive: /usr/share/ledgersmb/css/, referer: 
> http://localhost/ledgersmb/setup.pl
> [Fri Jun 01 17:44:49 2012] [error] [client 127.0.0.1] commit ineffective 
> with AutoCommit enabled at scripts/setup.pl line 519., referer: 
> http://localhost/ledgersmb/setup.pl
> 
> (the ones above seem to indicate a problem with the httpd conf file in 
> /etc/ledgersmb)
> 
> [Fri Jun 01 17:45:46 2012] [error] [client 127.0.0.1] Bareword found 
> where operator expected at LedgerSMB/Template/TXT.pm line 116, near "'.' 
> get_extension", referer: http://localhost/ledgersmb/setup.pl  ....

> These appear to be the fatal errors. A look upstream shows that there's 
> a report of this error:
> 
> http://www.mail-archive.com/ledger-smb-users@lists.sourceforge.net/msg05917.html
> 
> but I haven't been able to determine if this problem was ever solved.

   I'm checking into that, as I also have not found where the person who
originally posted about a simliar issue noted how or if he resolved it.


>  Otherwise I'll end up with 1.3.17 or 1.2.x installed 
> from the site directly, or some similar fix.

   Note that the next package upload will be at least for v1.3.17 (done
but not yet made available); possibly for v1.3.18, as I expect that to
be released fairly soon (within the next week or two).





Jame