- devel - lists.freelock.com

LedgerSMB 1.12.1 released
by Erik Huelsmann 05 Jan '25

05 Jan '25

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.12.1 * Ignore Content-Type header on GET requests (#8562) * Fix persisting of E-mail workflows without attachments (#8564) * Fix printing of GL and cash transfer transactions (#8580) * Fix error of Cash > Use [AR] Overpayment menus (#8582) For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.12.1/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.12.1 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.12.1 Or pulled from the GitHub Container Registry $ docker pull ghcr.io/ledgersmb/ledgersmb:1.12.1 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.12.1 These are the sha256 checksums of the uploaded files: de9377bdbff18d3e2f3622115e0db0aee70c546030132961d029d6976348c152 ledgersmb-1.12.1.tar.gz 37268f86bd4c7bb5e7679e270c9221ec7013360892ccf1cbe7b3e12d06647f1c ledgersmb-1.12.1.tar.gz.asc

1 0

LedgerSMB Community overview 2024
by Erik Huelsmann 04 Jan '25

04 Jan '25

With the new year just started, it's time to provide an overview of what our community has achieved over the past year. At the end of last year, I wished everybody a healthy and prosperous 2024 and now is a time to look back and see how we did. == Community interest == The website seems to generate roughly the same amount of interest as earlier years; with 10% more hits than last year, there's really no evidence of change in interest either way (up or down). From the increase in number of Stars on GitHub (Stars went up from 360 on 25 February 2024 to 432 today - in line with the increase last year), we can conclude that there is still interest in the project. This is supported by the fact that we see new people attend the ledgersmb chat channel on Matrix, with many contributing their bugs and experience. Over 2024, I added release notifications through various social channels hoping to attract interest from additional sources; release notifications were posted to: * Mastodon * freshcode.club * Facebook * LinkedIn * Twitter Additionally, I've been responding on Reddit to inquiries of people who want to self-host their accounting. The efforts have resulted in significantly more hits on our site from other sources than GitHub and search engines. == Releases == With the release of 1.12.0 on 14 December 2024, we didn't quite realize our goal to release 1.12 close to a year after 1.11 (03 October 2023). With releases in the third quarter, we aim to provide mature software before year-end -- when most companies close their books. We didn't let ourselves be pressured by the delay, keeping focus on releasing high quality software. We were able to include a sizeable list of new functionalities, changes and (code) cleanups through 835 commits, 622 files changed, 175,155 added lines and 136,214 removed lines of code (and comments) between 1.11.0 and 1.12.0. With 23 releases across 3 maintenance branches in 2024, the project was a bit quieter than 2023; mostly because periods between bug reports have increased -- some months no bugs were reported; something that hasn't happened before in my 10 years of contribution to the project: 1.10 (10): 1.10.29 - 1.10.38 1.11 (12): 1.11.8 - 1.11.19 1.12 (1): 1.12.0 Which excludes the alpha, beta and release candidate releases. All releases included Docker container images for 32-bit ARM (ARM/v7), 64-bit ARM (ARM64) and 64-bit Intel (AMD64), which can be run on a wide variety of ARM devices, including Raspberry Pi's. == Development progress == This year saw lower numbers of commits than last year. Although the number of commits was lower, the number of pull requests (597) is much lower than last year (736) which is probably a combination of not opening a separate PR for every little thing and a period of slower development in the second half of the year. The number of active developers - derived from accepted commits - was lower than last year (6) by 1 (5 this year). This year, too, we were able to close a long-standing bug, continuing last year's focus to close issues in the 7-year-and-older range: * #2162: Aging statement shows local currency for foreign currency invoices (regressed in 2016) Project commits on all branches (excluding merges): 538 Erik Huelsmann 32 Yves Lavoie 4 Neil Tiffin 6 Walid Mujahid 2 Christian Eriksson By comparison, these are the figures for 2023: 672 Erik Huelsmann 72 Yves Lavoie 15 Aung Zaw Win 6 Christian Eriksson 6 Neil Tiffin 1 John Locke Please note that the number of commits is in no way a measure of time spent on the project. Also note that these numbers don't include the time spent by those taking the effort to report their problems and taking the time to respond to developer questions as well as helping to test solutions when developers think they solved the problem. Similarly, there was a lot of activity with respect to issues: Number of open issues at 2024-01-01: 117 of which remain open today: 101 Issues closed: 60 of which created before 2024-01-01: 16 Issues created: 65 of which still open: 21 Number of open issues today: 122 This amount of development activity triggers many CI/CD jobs. To run our test workloads, we have been using GitHub Actions as well as CircleCI, each set up to test different aspects. The 122 issues that are open today summarize into these statistics: * 5 bite-sized: issue ideal to start with our code base * 7 help-wanted: these are issues we need someone to get involved * 5 sponor-wanted: these will be developed when someone helps out by footing bills * 65 type:enhancement: generally requests for new or improved features * 17 type:bug (Note that an issue may fall into more than one category or none at all.) == New functionality and improvements == 1.12 improves on 1.11's use of workflows by moving reconciliations to the same infrastructure. The implementation of workflows for AR/AP transactions is now used to show an audit trail. It also adds an audit trail - which can be inspected from setup.pl - for database upgrades, including feedback to administrators when an upgrade requires additional action (this implements #8363). Substantial work has been done on improving database upgrades even including upgrades from 1.3; this shows the project's commitment to help all users moving to new and supported versions, even if they are on long-unsupported versions. == Helping SQL-Ledger users migrate == The project is looking for SQL Ledger users who want to migrate to LedgerSMB to test and improve the migration procedure, now that new development of SQL-Ledger seems to have stalled. == Looking forward to 2025 == In 2025, we'll likely release 1.13 around the third quarter; again in a release cycle a bit shorter than a year. This year the 1.11 release branch will reach End-Of-Life status on 03 October. And last but not least, I'm hoping for 1 or 2 new contributors (not necessarily developers: translators, testers, documentation writers or UI artists are all greatly appreciated!). If you want to contribute, but don't know where to start, please contact me. == In closing == Thanks to everybody who contributed to any of the above in any way, especially to Neil Tiffin for taking the time to discuss (and thereby sharpen) planned changes and helping out with documentation-writing Computerisms.ca for hosting our DNS Freelock.com for hosting our website and mailing lists Efficito.com for hosting our mailing list archive, apt repository, release and download server GitHub.com, CircleCI and coveralls.io for hosting our development workflow My special personal thanks go to my GitHub Sponsors for supporting me for time, efforts and (financial) resources dedicated to the project! Leaves me only to wish everybody in our community - and their loved ones - a safe and productive 2025! -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

LedgerSMB 1.12.0 released
by Erik Huelsmann 15 Dec '24

15 Dec '24

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: Highlights of changelog for 1.12.0 Added functionalities * AR/AP transaction history similar to invoices (#7773) * More consistency checks in setup.pl (#7649) * Ability to include documentation in Chart of Account definition files (#7651) * Highlighting of unapproved payments on invoices and transactions (#7777) * Enhancements for migrations from 1.3 * Support for external template rendering engines like weasyprint (#8440) Changed functionalities * Default cookie names no longer include LedgerSMB version number (#7639) * Ship To addresses now immutable (#8365) Removed functionalities * 'Class' removed from Company and Person entry and search (#8086, #8087) Bugs fixed * Countries in setup.pl from Locale::CLDR; use reference data instead (#7648) * AR/AP items in vouchers can be saved only once (#6895) * Transactions and invoices with attachments can't be saved (#6018) * Aging statement shows functional instead of foreign currency amounts (#2162) * Incorrect starting balance of fx-based reconciliations (#8295) * Ship To on orders, quotes and purchase invoices (#8329) For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.12.0/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.12.0 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.12.0 Or pulled from the GitHub Container Registry $ docker pull ghcr.io/ledgersmb/ledgersmb:1.12.0 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.12.0 These are the sha256 checksums of the uploaded files: 26553fa962b938d36af9376206bfce6e72151447c7e01ec51b7f6b1c19580d6c ledgersmb-1.12.0.tar.gz 8f977454e6d34c497d043f7160ebe576ebd4d0b123331738e04268e913066b10 ledgersmb-1.12.0.tar.gz.asc

1 0

Adding to OpenBSD. Is this a good time now?
by chris＠bennettconstruction.us 19 Nov '24

19 Nov '24

A lot of Perl modules need to be imported into OpenBSD in order for it to be installable. I plan on asking for help to do this from OpenBSD users. It seems like LedgerSMB would now be a good import with all of the development of testing, etc. Are there any big changes on the immediate horizon for 1.5? I'm not running LedgerSMB because of the work that needs to be done first. As a side note, I am working on getting the forums back up, but $$ are a bit of a problem right now. Trying to find a baremetal server outside of the USA that I can afford hasn't been successful so far. I found one, but they charge $30 for remote access for 24 hours. I can't afford $90 a month, which is most of what I am finding. Thanks, Chris Bennett

3 2

ledgersmb REMOVED from testing
by Debian testing watch 16 Nov '24

16 Nov '24

FYI: The status of the ledgersmb source package in Debian's testing distribution has changed. Previous version: 1.6.33+ds-2.2 Current version: (not in testing) Hint: <https://release.debian.org/britney/hints/auto-removals> # 1027472 The script that generates this mail tries to extract removal reasons from comments in the britney hint files. Those comments were not originally meant to be machine readable, so if the reason for removing your package seems to be nonsense, it is probably the reporting script that got confused. Please check the actual hints file before you complain about meaningless removals. -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information.

1 0

LedgerSMB 1.11.19 released
by Erik Huelsmann 02 Nov '24

02 Nov '24

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.11.19 * Fix post-and-approve action failing to approve transactions (#8442) * Fix failure to load modules using Perl 5.40 (#8468) For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.11.19/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.11.19 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.11.19 Or pulled from the GitHub Container Registry $ docker pull ghcr.io/ledgersmb/ledgersmb:1.11.19 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.11.19 These are the sha256 checksums of the uploaded files: 0b88b220864860adced4fdf47ab69b3dc89da44e690996a7e005384e659eb0fc ledgersmb-1.11.19.tar.gz 9c3515c6f0782c2be49788cf1c82d3de978938d07622b821f32336a6885215e1 ledgersmb-1.11.19.tar.gz.asc

1 0

Processed: severity of 1027472 is grave
by Debian Bug Tracking System 02 Nov '24

02 Nov '24

Processing commands for control(a)bugs.debian.org: > severity 1027472 grave Bug #1027472 [src:ledgersmb] ledgersmb: upstram says 1.6 is unsupported and insecure. Newer upstream version 1.10 available Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1027472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027472 Debian Bug Tracking System Contact owner(a)bugs.debian.org with problems

2 1

ledgersmb is marked for autoremoval from testing
by Debian testing autoremoval watch 01 Nov '24

01 Nov '24

ledgersmb 1.6.33+ds-2.2 is marked for autoremoval from testing on 2024-11-15 It is affected by these RC bugs: 1027472: ledgersmb: upstram says 1.6 is unsupported and insecure. Newer upstream version 1.10 available https://bugs.debian.org/1027472 For more information on the autoremoval process, including hints to prevent autoremoval can be found on the wiki: https://wiki.debian.org/Autoremoval This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/ma… Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gath…

1 0

[NOTICE] Upcoming 1.12 release -- looking for translators & testers
by Erik Huelsmann 27 Oct '24

27 Oct '24

Hi, In preparation for the 1.12 release, the project is looking for existing and new translators to update the software translations (see https://app.transifex.com/ledgersmb/ledgersmb/ledgersmb-112/) Any contribution is greatly appreciated, even if the translation is not complete: others can pick up where you left off. Also: translations are not just for 1.12: reusable translations will be used to translate 1.11 too. Soon a beta release will be published. In order to make the 1.12 release as stable as reasonably possible, the project needs beta testers: people who execute their most common workflows on (a copy!) of their data. We need these people to report the issues they run into, but also their successes! Regards, -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

2 1

LedgerSMB 1.11.18 released
by Erik Huelsmann 13 Oct '24

13 Oct '24

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.11.18 * Fix specifying an alternative database server port number (#8400) * Fix hostname with hyphen breaks ledgersmb-admin database URI (#8415) * Allow ledgersmb-admin to use pre-created databases, e.g. DigitalOcean (#8422) * Fix PNL and B/S CSV output missing 'heading_account' column (#8428) For installation instructions and system requirements, see https://github.com/ledgersmb/LedgerSMB/blob/1.11.18/README.md The release can be downloaded from our download site at https://download.ledgersmb.org/f/Releases/1.11.18 The release can be downloaded from GitHub at https://github.com/ledgersmb/LedgerSMB/releases/tag/1.11.18 Or pulled from the GitHub Container Registry $ docker pull ghcr.io/ledgersmb/ledgersmb:1.11.18 Or pulled from Docker Hub using the command $ docker pull ledgersmb/ledgersmb:1.11.18 These are the sha256 checksums of the uploaded files: 4ac427cab5839a555bb438ff16c05610c951dd0e48ca216ce5f2ac5f4cb69dab ledgersmb-1.11.18.tar.gz 8bc0c43abf2790ecd98bcb6c550faacc7fc09ae73f61ae6d74981737a49d366d ledgersmb-1.11.18.tar.gz.asc

1 0