June 2021 - users - lists.freelock.com

LedgerSMB 1.8.14 released
by Erik Huelsmann 03 Jun '21

03 Jun '21

The LedgerSMB development team is happy to announce yet another new version of its open source ERP and accounting application. This release contains the following fixes and improvements: Changelog for 1.8.14 * Follow-up (fix) to upgrades blocked by files attached to transactions For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.8.14/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.8.14 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.8.14 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.8.14 These are the sha256 checksums of the uploaded files: 655c3a6571d584ca8cac55c01ced75f64299fcdc44bfa273cd45e32a1f3edbbe ledgersmb-1.8.14.tar.gz c7a55e1a5b48ef525cefb932a9d8ebd3ee7d167fb94b38cd1dee502b7d1a5ef6 ledgersmb-1.8.14.tar.gz.asc

1 0

LedgerSMB 1.7.30 released
by Erik Huelsmann 03 Jun '21

03 Jun '21

The LedgerSMB development team is happy to announce yet another new version of its open source ERP and accounting application. This release contains the following fixes and improvements: Changelog for 1.7.30 * Follow-up (fix) to upgrades blocked by files attached to transactions For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.7.30/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.7.30 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.7.30 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.7.30 These are the sha256 checksums of the uploaded files: 9d70f9a392d8283128cca62a757e2d1e4c1febcb8a9ba44d90be4bb4d530f4a0 ledgersmb-1.7.30.tar.gz 41064f1f5fedc29ae46ac0410c1da8e09dcb0ae642573564449c1b6f6f4047ce ledgersmb-1.7.30.tar.gz.asc

1 0

Re: Stuck upgrading 1.6.27 to anything beyond
by Louis B. Moore 03 Jun '21

03 Jun '21

Thank you, I'm trying to get up to 1.8.x the mkdir got me a step further, then a permissions fix. Made it to 1.6.32, starting to look at 1.7.26 as the next hop. Louis On Thu, 3 Jun 2021, lsmbdev wrote: > Hi Louis, > > What version were you intending to upgrade to? > > For the "no such file or directory" error you can try manually creating the parent dir with > > mkdir "/tmp/deleted_transaction_files/" > > That is not the ideal solution, but may allow the upgrade to proceed. > (I'm not at a computer so can't try testing to confirm cause or if this will help) > > Regards > David G > > Sent from my Galaxy > > > -------- Original message -------- > From: "Louis B. Moore" <lbmoore(a)hethcote.com> > Date: 3/6/21 12:24 (GMT+08:00) > To: Erik Huelsmann <ehuels(a)gmail.com> > Cc: users(a)lists.ledgersmb.org > Subject: [ledgersmb-users] Re: Stuck upgrading 1.6.27 to anything beyond > > > > Different error: > > Error! > Can't create directory /tmp/deleted_transaction_files/hethcote: No such > file or directory at > /usr/local/ledgersmb/sql/changes/1.6/track-deleted-transactions.sql.checks.pl > line 38. > > dbversion: , company: 1.6.31 > > > Created directory: > > > Error! > Can't create directory /tmp/deleted_transaction_files/hethcote: > Permission denied at > /usr/local/ledgersmb/sql/changes/1.6/track-deleted-transactions.sql.checks.pl > line 38. > > dbversion: , company: 1.6.31 > > > Chowned directory: > > success. > > > > > Thank you! > > > > > > > > > > > > On Thu, 3 Jun 2021, Erik Huelsmann wrote: > > > Hi Louis, > > > > > > On Wed, Jun 2, 2021 at 8:06 PM Louis <lbmlist(a)hethcote.com> wrote: > > > > Greetings, > > > > I was beginning to move from the 1.6 line when I encountered an error. I > > was able to isolate the error to the upgrade from 1.6.27 -> 1.6.28 which > > dies with: > > > > Error! > > > > Error applying upgrade script ./sql/changes/1.6/track-deleted-transactions.sql: ERROR: update or delete > > on table "transactions" violates foreign key constraint > > "file_transaction_ref_key_fkey" on table "file_transaction" > > > > DETAIL: Key (id)=(17812) is still referenced from table "file_transaction". at > > /usr/local/ledgersmb/tools/../lib/LedgerSMB/Database/Change.pm line 227. > > > > dbversion: , company: 1.6.28 > > > > > > This happened at postgresql 9.6 and also at 11. > > > > Can anyone help me past this issue? > > > > > > Yes, I think I can: instead of upgrading to 1.6.28, could you try upgrading to 1.6.31 or 1.6.32? There is a fix in > .31 > > which should fix this exactproblem:https://github.com/ledgersmb/LedgerSMB/commit/846886b3e36bd32d… > 9542f388a07a2a > > 5209456ce790b04251bc9bd7d179ea85cb1R6 > > > > > > Let me know if that solves your problem! > > > > > > Regards, > > > > -- > > Bye, > > Erik. > > > > http://efficito.com -- Hosted accounting and ERP. > > Robust and Flexible. No vendor lock-in. > > > > >

1 0

Stuck upgrading 1.6.27 to anything beyond
by Louis 03 Jun '21

03 Jun '21

Greetings, I was beginning to move from the 1.6 line when I encountered an error. I was able to isolate the error to the upgrade from 1.6.27 -> 1.6.28 which dies with: Error! Error applying upgrade script ./sql/changes/1.6/track-deleted-transactions.sql: ERROR: update or delete on table "transactions" violates foreign key constraint "file_transaction_ref_key_fkey" on table "file_transaction" DETAIL: Key (id)=(17812) is still referenced from table "file_transaction". at /usr/local/ledgersmb/tools/../lib/LedgerSMB/Database/Change.pm line 227. dbversion: , company: 1.6.28 This happened at postgresql 9.6 and also at 11. Can anyone help me past this issue? Thank you, Louis

4 4