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.16
* Fix incorrectly encoded UTF-8 characters on journal entry (#5583)
* Fix multiple updates in payment screen resetting user input (#5614)
* Improve error message when missing cash discount configuraition (#5632)
* Fix payment information for credit accounts which are Persons (#5632)
* Fix memos sometimes being associated with incorrect payment rows (#5646)
* Fix wrong fx value due to formatted exchangerate used in calculation (#5656)
* Fix decimal places setting not applied for AR/AP transactions (#5657)
* Fix duplicated income statement figures due to reversed year end (#5682)
For installation instructions and system requirements, see
https://github.com/ledgersmb/LedgerSMB/blob/1.8.16/README.md
The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.8.16
The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.8.16
Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.8.16
These are the sha256 checksums of the uploaded files:
17a2e068e6655b833e209aa954b51bc6b8bb82fa4ea87bade9abefdc98cadff2 ledgersmb-1.8.16.tar.gz
7f0cd165beb22953712a11c2380dc587966e588bfc25cca75166e7d94bba3a93 ledgersmb-1.8.16.tar.gz.asc
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.32
* Fix multiple updates in payment screen resetting user input (#5614)
* Improve error message when missing cash discount configuraition (#5632)
* Fix payment information for credit accounts which are Persons (#5632)
* Fix memos sometimes being associated with incorrect payment rows (#5646)
* Fix wrong fx value due to formatted exchangerate used in calculation (#5656)
* Fix decimal places setting not applied for AR/AP transactions (#5657)
* Fix duplicated income statement figures due to reversed year end (#5682)
For installation instructions and system requirements, see
https://github.com/ledgersmb/LedgerSMB/blob/1.7.32/README.md
The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.7.32
The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.7.32
Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.7.32
These are the sha256 checksums of the uploaded files:
22fb6f99d68c7a1372949f7a7ecef5f76c3ce8ebec610f73d6076a44b19b266a ledgersmb-1.7.32.tar.gz
9c13b3bf6fbb13d61c4adef3e342eb86c8027808dddedbab30cae4027fe1d9d3 ledgersmb-1.7.32.tar.gz.asc
Hi,
Due to some turbulence around FreeNode (none of which I care to repeat
here), almost all open source projects have left the FreeNode IRC network.
This applies to the LedgerSMB project too.
Some projects moved to the OFTC network, a new IRC network called
libera.chat was created and many projects moved there. Some projects
decided to ditch IRC completely and move to Discourse, Slack or Matrix. For
many projects, this simply meant discontinuing their 'official' IRC channel
as they already had Discourse, Slack or Matrix presence.
LedgerSMB has had Matrix (See https://element.io/) presence for many years.
Our Matrix channel used to me "bridged" to the FreeNode IRC channel. This
connection has now been severed; meaning that at the moment, we only have a
Matrix channel as our community support channel.
Now that the ties have been severed, this begs the question: should we
create a new bridge to IRC (e.g. to the libera.chat network)? Or do we not
need an IRC network at all and will we be happy to stick with our existing
Matrix channel (see https://app.element.io/#/room/#ledgersmb:matrix.org)?
As the project committee, we'd love to hear from you so we can best serve
you.
Thank you for sharing your considerations!
--
Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.
Last weekend, the project created the 1.9 release branch as part of the
preparations for the upcoming 1.9 release now planned for late July/early
August.
This mail is a call to translators to update the LedgerSMB translations on
Transifex (https://www.transifex.com/ledgersmb/ledgersmb/dashboard/) while
there is still time.
Please note that some translations don't have any active translators
assigned at the moment, yet are in need of updating. So for those of you
who are wondering what to give back to the community, please sign up and
spend some time translating terms for your favorite language. There's no
need to be all-or-nothing about this: all contributions are appreciated -
there's no need to wait for a moment where you have time to do a full
translation.
While working on the 1.9 translation, all translations that match those in
1.7 and 1.8 are being copied to those versions by Transifex automatically,
so by contributing to 1.9, you also contribute to 1.7 and 1.8.
If you don't want to sign up with Transifex: no problem, contact me
off-list and we can figure out a way to shepherd your contributions into a
release.
--
Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.
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.15
* Improve reconciliation of data entered before migration to 1.8
* Fix AR/AP transaction+invoice 'New' button throwing an error (#5539)
* Fix transaction total in AR/AP transactions with applied payments (#5528)
* Stop doubling of the number of lines in an AR/AP transaction on Save (#5529)
* Fix vendors appearing in the AR customer drop-down and vice versa (#5534)
* Fix second and consecutive Save actions on invoices throwing an error (#5532)
* Only limit Customer/Vendor History by country with explicit filter (#4361)
For installation instructions and system requirements, see
https://github.com/ledgersmb/LedgerSMB/blob/1.8.15/README.md
The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.8.15
The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.8.15
Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.8.15
These are the sha256 checksums of the uploaded files:
819fad10619041981a44aa18849ca00a2630e6447c6e2ff7003e81d022e6095d ledgersmb-1.8.15.tar.gz
9d21b09abbeb867ffd5da5e940b24ac6b60013479c76b532196f0bf33f0e9aea ledgersmb-1.8.15.tar.gz.asc
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.31
* Stop doubling of the number of lines in an AR/AP transaction on Save (#5529)
* Fix vendors appearing in the AR customer drop-down and vice versa (#5534)
* Fix second and consecutive Save actions on invoices throwing an error (#5532)
* Only limit Customer/Vendor History by country with explicit filter (#4361)
For installation instructions and system requirements, see
https://github.com/ledgersmb/LedgerSMB/blob/1.7.31/README.md
The release can be downloaded from our download site at
https://download.ledgersmb.org/f/Releases/1.7.31
The release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.7.31
Or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.7.31
These are the sha256 checksums of the uploaded files:
e7c3bcd0e8771374982658968b0ead909aad77ca0517ad28ef17a709f452bcd2 ledgersmb-1.7.31.tar.gz
849ae7fa4b1726d3d7fdb9a77df013a9c50bd8af746a660569e18224464671a8 ledgersmb-1.7.31.tar.gz.asc
I'm running debian buster with postgresql 11. I install from tarball.
Thanks for the assistance,
Louis
On Fri, 4 Jun 2021, lsmbdev wrote:
> Hi Louis,
>
> You've got me with this one.
>
> I haven't seen it before.
>
> Erik may have and he should be up and about in the next few hours.
>
> Regardless we will find an answer for you.
>
> What platform (OS) are you installing on?
>
> And did you install from source or the tarball?
>
> Regards
> David G
>
> Sent from my Galaxy
>
>
> -------- Original message --------
> From: Louis <lbmlist(a)hethcote.com>
> Date: 4/6/21 12:59 (GMT+08:00)
> To: lsmbdev <lsmbdev(a)sbts.com.au>, users(a)lists.ledgersmb.org
> Subject: RE: [ledgersmb-users] Question re 1.7.29 upgrade from 1.6.32
>
>
>
> Ok, made it through starting the service. login.pl works and tells you to
> run setup.pl. Logged on to setup and selected upgrade db.
>
> Now I'm getting
>
> "
> Error!
>
> Can't locate object method "verify_helpers" via package
> "LedgerSMB::Database" at lib/LedgerSMB/Scripts/setup.pm line 242.
>
> dbversion: hethcote, company: 1.7.29
> "
>
> Is this a know problem?
>
>
> On Fri, 4 Jun 2021, lsmbdev wrote:
>
> > Hi Louis,
> >
> > The name of the service (what you use on the command line to start/stop/reload/etc) is declared inside the
> .service
> > file.
> > It actually doesn't have to be the same as the name of the service file, although it most often is.
> >
> > You are welcome to change the name if that will help with remembering the service name.
> >
> > We possibly should look at the service name and it's file name before 1.9 release to ensure we are following
> > accepted standards
> >
> > Regards
> > David G
> >
> >
> >
> > Sent from my Galaxy
> >
> >
> > -------- Original message --------
> > From: Louis <lbmlist(a)hethcote.com>
> > Date: 4/6/21 09:22 (GMT+08:00)
> > To: users(a)lists.ledgersmb.org
> > Subject: [ledgersmb-users] Question re 1.7.29 upgrade from 1.6.32
> >
> >
> > Greetigns,
> >
> > Looking at https://ledgersmb.org/content/upgrade-ledgersmb-17-16-or-15
> >
> > " Stop the LedgerSMB application server (e.g. Starman)
> > $ sudo service starman-ledgersmb stop
> > .
> > .
> > .
> > Upgrade the LedgerSMB Starman SysV or systemd scripts (the new scripts
> > can be found in /usr/local/ledgersmb/conf/systemd/ )
> > $ sudo cp /usr/local/ledgersmb/conf/systemd/ledgersmb_starman.service \
> > /etc/systemd/system/ledgersmb.service
> > $ sudo systemctl daemon-reload
> >
> > Start the LedgerSMB application server again (Starman example given,
> > as before):
> > $ sudo service starman-ledgersmb start
> > "
> >
> > Am I misunderstanding something? It seems as though documentation has me
> > stop the service for 1.6 as starman-ledgersmb, then copy the file
> > ledgersmb_starman.service to /etc/systemd/system/ledgersmb.service.
> > After the daemon-reload, I start service starman-ledgersmb.
> >
> >
> > It seems to me that
> > /usr/local/ledgersmb/conf/systemd/ledgersmb_starman.service should be
> > copied to /etc/systemd/system/starman-ledgersmb.service to keep the
> > service name the same.
> >
> >
> > Systemd is not my strong suit so I want to confirm the steps before trying
> > them out.
> >
> > Thanks all,
> >
> > Louis
> > _______________________________________________
> > users mailing list -- users(a)lists.ledgersmb.org
> > To unsubscribe send an email to users-leave(a)lists.ledgersmb.org
> >
> >
> >
>
Ok, made it through starting the service. login.pl works and tells you to
run setup.pl. Logged on to setup and selected upgrade db.
Now I'm getting
"
Error!
Can't locate object method "verify_helpers" via package
"LedgerSMB::Database" at lib/LedgerSMB/Scripts/setup.pm line 242.
dbversion: hethcote, company: 1.7.29
"
Is this a know problem?
On Fri, 4 Jun 2021, lsmbdev wrote:
> Hi Louis,
>
> The name of the service (what you use on the command line to start/stop/reload/etc) is declared inside the .service
> file.
> It actually doesn't have to be the same as the name of the service file, although it most often is.
>
> You are welcome to change the name if that will help with remembering the service name.
>
> We possibly should look at the service name and it's file name before 1.9 release to ensure we are following
> accepted standards
>
> Regards
> David G
>
>
>
> Sent from my Galaxy
>
>
> -------- Original message --------
> From: Louis <lbmlist(a)hethcote.com>
> Date: 4/6/21 09:22 (GMT+08:00)
> To: users(a)lists.ledgersmb.org
> Subject: [ledgersmb-users] Question re 1.7.29 upgrade from 1.6.32
>
>
> Greetigns,
>
> Looking at https://ledgersmb.org/content/upgrade-ledgersmb-17-16-or-15
>
> " Stop the LedgerSMB application server (e.g. Starman)
> $ sudo service starman-ledgersmb stop
> .
> .
> .
> Upgrade the LedgerSMB Starman SysV or systemd scripts (the new scripts
> can be found in /usr/local/ledgersmb/conf/systemd/ )
> $ sudo cp /usr/local/ledgersmb/conf/systemd/ledgersmb_starman.service \
> /etc/systemd/system/ledgersmb.service
> $ sudo systemctl daemon-reload
>
> Start the LedgerSMB application server again (Starman example given,
> as before):
> $ sudo service starman-ledgersmb start
> "
>
> Am I misunderstanding something? It seems as though documentation has me
> stop the service for 1.6 as starman-ledgersmb, then copy the file
> ledgersmb_starman.service to /etc/systemd/system/ledgersmb.service.
> After the daemon-reload, I start service starman-ledgersmb.
>
>
> It seems to me that
> /usr/local/ledgersmb/conf/systemd/ledgersmb_starman.service should be
> copied to /etc/systemd/system/starman-ledgersmb.service to keep the
> service name the same.
>
>
> Systemd is not my strong suit so I want to confirm the steps before trying
> them out.
>
> Thanks all,
>
> Louis
> _______________________________________________
> users mailing list -- users(a)lists.ledgersmb.org
> To unsubscribe send an email to users-leave(a)lists.ledgersmb.org
>
>
>
Greetigns,
Looking at https://ledgersmb.org/content/upgrade-ledgersmb-17-16-or-15
" Stop the LedgerSMB application server (e.g. Starman)
$ sudo service starman-ledgersmb stop
.
.
.
Upgrade the LedgerSMB Starman SysV or systemd scripts (the new scripts
can be found in /usr/local/ledgersmb/conf/systemd/ )
$ sudo cp /usr/local/ledgersmb/conf/systemd/ledgersmb_starman.service \
/etc/systemd/system/ledgersmb.service
$ sudo systemctl daemon-reload
Start the LedgerSMB application server again (Starman example given,
as before):
$ sudo service starman-ledgersmb start
"
Am I misunderstanding something? It seems as though documentation has me
stop the service for 1.6 as starman-ledgersmb, then copy the file
ledgersmb_starman.service to /etc/systemd/system/ledgersmb.service.
After the daemon-reload, I start service starman-ledgersmb.
It seems to me that
/usr/local/ledgersmb/conf/systemd/ledgersmb_starman.service should be
copied to /etc/systemd/system/starman-ledgersmb.service to keep the
service name the same.
Systemd is not my strong suit so I want to confirm the steps before trying
them out.
Thanks all,
Louis
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
