Hello,
I tested your patch with my setup and everything works OK for me.
* Balances
* Budgets
* Commodities
* Multiple-file inclusion
All of the above work OK.
I don't know if it's too late to get in for 6.8 because of the
ports lock, but whether it goes in now o
I hope, i am not too late, but i would really like to see the bug in
ledger fixed for next -stable. (I run 3.2.1 since Aug 25 on all my four
amd64 machines with no problems and before there were the crashes mentioned
in github as #1850)
On Wed, Sep 09, 2020 at 10:57:04AM +0200, Martin Ziemer wrot
On Tue, Aug 25, 2020 at 12:29:26PM +0200, Martin Ziemer wrote:
> On Tue, Aug 25, 2020 at 10:06:29AM +0100, Stuart Henderson wrote:
> > On 2020/08/25 10:56, Martin Ziemer wrote:
> > > This patch updates ledger from v3.1.3 to v3.2.1
> >
> > > +MODPY_VERSION = ${MODPY_DEFAULT_VERSION_3}
> >
On Tue, Aug 25, 2020 at 10:06:29AM +0100, Stuart Henderson wrote:
> On 2020/08/25 10:56, Martin Ziemer wrote:
> > This patch updates ledger from v3.1.3 to v3.2.1
>
> > +MODPY_VERSION = ${MODPY_DEFAULT_VERSION_3}
> ^
> please mind spaces vs tabs
I changed the space
On 2020/08/25 10:56, Martin Ziemer wrote:
> This patch updates ledger from v3.1.3 to v3.2.1
> +MODPY_VERSION = ${MODPY_DEFAULT_VERSION_3}
^
please mind spaces vs tabs
Otherwise OK with me (I don't use this though so can't do any meaningful
testing).
This patch updates ledger from v3.1.3 to v3.2.1
Since v3.2.0 ledger supports python3, so i changed the python version
to 3.
A lot of the examples from contrib, which were installed to
share/examples/ledger, dont work. (In github those examples are often
12 years old)
Looked at Debian and FreeBSD
