Release of ledgersmb-1.5 v1.5.11-1
An initial version of the debian package for ledgersmb-1.5 for version 1.5.11-1 has been released and uploaded to our apt package repository for 'main' in stretch. It has also been uploaded to our PPA, for 'artful' (the future v17.10). (The Debian source packages are available as well.) Note that this version of the package does not include ledgersmb-1.5-apache for the Apache proxy configuration as there is still an unresolved issue with that but does include ledgersmb-1.5-nginx for the Nginx proxy configuration. The ledgersmb-1.5-lighttpd and ledgersmb-1.5-varnish proxy configuration packages are also still in the process of being added. At our apt package repository[1]: ledgersmb-1.5_1.5.11-1_all.deb ledgersmb-1.5-nginx_1.5.11-1_all.deb At our PPA[2]: ledgersmb-1.5_1.5.11-1~ubuntu17.11.1_all.deb ledgersmb-1.5-nginx_1.5.11-1~ubuntu17.11.1_all.deb -- Robert J. Clay rjclay@gmail.com, jame@rocasa.us GPG ID: 2448 3AE0 874D 8696 6DCD ECF4 198C AB6F 43B7 EA9A [1] https://apt.ledgersmb.org/ [2] https://launchpad.net/~ledgersmb/+archive/ubuntu/main/+packages
On Fri, Sep 15, 2017 at 8:20 PM, Robert J. Clay <rjclay@gmail.com> wrote:
Note that this version of the package does not include ledgersmb-1.5-apache for the Apache proxy configuration as there is still an unresolved issue with that
Still need to figure out the problem with the install of that package, with the following being an example of the error that was being seen: dpkg: error processing package ledgersmb-1.5-apache (--install): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: ledgersmb-1.5-apache The open issue for that is: https://github.com/ledgersmb/pkg-ledgersmb-1.5/issues
The ledgersmb-1.5-lighttpd and ledgersmb-1.5-varnish proxy configuration packages are also still in the process of being added.
I do have the additional stanzas in debian/control for those proxy binary package. And I also have initial versions of the maintainer scripts needed for them both, but they need updating and testing (basically, regarding where the config files go as well as for needed restart/reloads after they're installed) before they can be added to release package. -- Robert J. Clay rjclay@gmail.com, jame@rocasa.us GPG ID: 2448 3AE0 874D 8696 6DCD ECF4 198C AB6F 43B7 EA9A
participants (1)
-
Robert J. Clay