Bug#903744: Update ledgersmb package to 1.6.x series
Package: ledgersmb Severity: wishlist Owner: Robert James Clay jame@rocasa.us Found: 1.5.21-1
The current version of the LedgerSMB application in Debian is version 1.5.21 and the 1.5.x series was originally released 24 December 2016. Version 1.6.0 for the LedgerSMB application was released on 10 June 2018 and the most recent version of the 1.6.x series is version 1.6.2 which was released on 23 June 2018.
Update the ledgersmb package in Debian to the 1.6.x version series of the application.
Control: block 903744 by 901739 Control: tag confirm
An issue delaying the upgrade of the ledgersmb package to the 1.6.x series upstream version has been required Perl modules that are not yet in Debian. One that is still left is HTML::Escape [1] but that one (as it is currently in upstream) in turn requires Module::Build::Pluggable::PPPort [2] which is also not yet in Debian. And that one in turn requires Module::Build::Pluggable [3] which is also not in Debian.
On Sun, Jul 15, 2018 at 4:03 PM Robert J. Clay rjclay@gmail.com wrote:
One that is still left is HTML::Escape [1] but that one (as it is currently in upstream) in turn requires Module::Build::Pluggable::PPPort [2] which is also not yet in Debian. And that one in turn requires Module::Build::Pluggable [3] which is also not in Debian.
Those are all now in Debian so I'll be starting work on updating the ledgersmb Debian package for the 1.6.x series.
Processing control commands:
block 903744 by 901739
Bug #903744 [ledgersmb] Update ledgersmb package to 1.6.x series 903744 was not blocked by any bugs. 903744 was not blocking any bugs. Added blocking bug(s) of 903744: 901739
tag confirm
Unknown command or malformed arguments to command.
Your message dated Sat, 13 Oct 2018 02:45:42 +0000 with message-id E1gB9vy-000ABD-QE@fasolo.debian.org and subject line Bug#903744: fixed in ledgersmb 1.6.5+ds-1 has caused the Debian Bug report #903744, regarding Update ledgersmb package to 1.6.x series to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.)
participants (2)
-
Debian Bug Tracking System -
Robert J. Clay