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.5.9
* Fix goods/services search with AR/AP invoices (Chris T, #2938)
* Fix inventory activity report drill down over-inclusive (Chris T, #2926)
* Fix Ship/Receive column alignments (Chris T)
* Fix mailing recurring invoices shows invoice in-screen (Erik H, #3004)
* Fix missing column SQL error when posting recurring invoices (Erik H)
* Show an error when page assets (Dojo) are missing (Erik H)
* Fix new welcome page being referred to by absolute path (Erik H, #2994)
* Fix 'Not an ARRAY reference' error in recurring AP processing (Erik H, #2973)
* Fix recurring AP invoices posted but 'next date' unchanged (Erik H, #3019)
* Fix the fix for '.' missing in @INC (Erik H)
* Add lighttpd example config (Yves L)
* Fix regression in setup.pl with LedgerSMB 1.2 or SQL Ledger db (Yves L)
* Fix error when adding customer-specific price to customer (Erik H, #2643)
* Fix can't edit sales & purchase quotation through web UI (Erik H, #2617)
* Fix string match operator typo in company searches (Erik H)
* Fix LedgerSMB 1.2->1.5 migration script syntax errors (Erik H)
* Add migration non-standard (gl) 'account links' for 1.2->1.5 (Erik H)
* When including code with 'do', don't silently skip errors (David G, #3020)
Chris T is Chris Travers
Erik H is Erik Huelsmann
Yves L is Yves Lavoie
David G is David Godfrey
The release can be downloaded from our download site at
http://download.ledgersmb.org/f/Releases/1.5.9/
Additionally, the release can be downloaded from GitHub at
https://github.com/ledgersmb/LedgerSMB/releases/tag/1.5.9
or pulled from Docker Hub using the command
$ docker pull ledgersmb/ledgersmb:1.5.9
These are the sha256 checksums of the uploaded files:
48977307f6bb1cd60b5d43bfe763b373402115b11435afe5fde837a9c142f5ef ledgersmb-1.5.9.tar.gz
9236a6aaf650f5918e6e1bbfe4a149e7f17917363e7a7da8e0cffd3f0fad7a88 ledgersmb-1.5.9.tar.gz.asc
Hi
We need to trace to whom we sell our products but I can't find any product
sales breakdown
The closest I can find is in Goods and Services -> Reports -> Inventory
Activity, where I seemingly can see the number of sold items during a time
period. But when clicking the number, I just get a full list of all invoices,
NOT only the ones containing the requested part,
--
Med venlig hilsen
Kaare Rasmussen, Jasonic
Jasonic: Nordre Fasanvej 12, 2000 Frederiksberg
It had been commented by various people that they have been seeing error
messages regarding the apt.ledgesmb.org repository key being too small or
too "week" when the repository was being accessed, like the following
example comment:
apt update returns W: http://apt.ledgersmb.org/dists/xenial/InRelease:
Signature by key 1ED705D54028F70F45E32340D0F530B7F93ECF4F uses weak digest
algorithm (SHA1) at the end
I've created a 4K RSA key for the repository and have added it to the
configuration there, and updated the home page about it. Will be using
both the old and the new key for a bit, but then the old key will be
removed from the configuration.
--
Robert J. Clay
rjclay(a)gmail.com
jame(a)rocasa.us
Since the release of LedgerSMB v.1.5.8, which dropped the requirement
for App::LedgerSMB::Admin, I have been working on finishing the Debian
packaging for the new version, for both the ledgersmb package for Debian
itself as well as the new ledgersmb-1.5 package which is just for release
by our project. Note that the git packaging repositories for both are at
GitHub [1][2]. This email is to start a discussion as necessary regarding
the packaging, starting with some notes about how it's proceeding.
The intent of the debian/watch file plus the get-orig-source target in
debian/rules is to provide a way to automatically create an *.orig.tar.gz
file, especially for when new versions of LedgerSMB comes out. Using
that, the process will check for a new version. If one is found; it will
download the new archive as well as its associated *.asc pgp signature
file. Then verify the pgp signature against the downloaded archive. Then
repack it as necessary (needed for ledgersmb, possibly also useful for
ledgesmb-1.5) if the verification is good.
This had been working for both packages prior to the move from
SourceForge. I've been able to do some updating for the debian/watch file
(just in ledgersmb-1.5, so far) but not to where I can get the verification
step to work properly, although it does find the new version in the new
location at GitHub. (In order to proceed with the packaging, I manually
downloaded and verified the new 1.5.8 version.)
One big difference between LSMB v1.4.x and v1.5.x is that LedgerSMB is
now being run by Starman instead of by Apache; this is more an issue for
the ledgersmb package since it needs to also handle upgrades from v1.4.x.
I originally thought to handle the choice between which web proxy to use,
Apache or Nginx, by asking a question about it during the package install
and then proceeding from there. To that end, I added a debconf question
about it which defaults to 'None'. However, I could not figure a way to
take advantage of that selection during the package install in order to get
either apache or nginx to be installed as necessary. So what I've ended up
doing (and am in the process of testing with the ledgersmb-1.5 package) is
adding the creation of additional binary packages that provide for the
installation and configuration for apache or nginx and those depend on the
main package. (I wonder if they should be made mutually exclusive...)
That debconf question about a web proxy selection is not needed now and
will likely be removed.
--
Robert J. Clay
rjclay(a)gmail.com
jame(a)rocasa.us
[1] https://github.com/ledgersmb/pkg-ledgersmb
[2] https://github.com/ledgersmb/pkg-ledgersmb-1.5
