Upcoming Ledger Release

[Alexis]

Hello everyone,
a while ago I wanted to publish a new ledger release, but didn't
(and I'd rather not have you asking why ;)

Ledger's bitrot is becoming more and more of a problem (especially with
newer boost versions, namely 1.58, 1.59, and 1.60)
so I think a new release is quite necessary.

I pushed the latest changes to the next and the release/3.1.1 branch
and kindly ask that anyone willing to spend some time and effort
test those changes and report any issues.

Hopefully there are no (or only minor) issues.

To test ledger please:
  * build the release/3.1.1 branch
  * run the tests (make test)
  * do your own test with your personal workflow
  * report success or any issues to this mailing list,
be sure to include the operating system,
boost version, and build output

I'm setting a fixed release date: Monday, 11th of January 2016,
and will release on this day unless there are major blocking issues.
This gives those you want to participate roughly a week to test the
latest changes.

Some folks wanted the next release to be numbered 3.2.0 instead of
3.1.1, and I'd like the community to decide. If you have an opinion
on the matter please reply to this email and make your mark.

  The next ledger release should be numbered:

[ ] 3.1.1
[ ] 3.2.0


Thanks,
Alexis

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Upcoming Ledger Release

[Martin Michlmayr]

* John Wiegley  [2016-01-02 09:02]:
> Why would it be named 3.2? Does it have any new features or change any APIs?
> 3.1.1 sounds like the correct number to me.

There's at least the new --no-revalued option and support for newer
Boost.  See doc/NEWS for a (probably incomplete) list of changes.

I'm for 3.2 due to some new features and the number of bug fixes, but
3.1.1 is fine with me.

I don't think the version number matters as much as getting a new
release out.

-- 
Martin Michlmayr
http://www.cyrius.com/

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

untrusted datafile execution

[Madis Väin]

Hei!

I'm not a C++ programmer and it's probably better I ask this not try to 
figure it out myself.

The way ledger currently reads data files inputted is there any way to 
execute code within that system? Is the executing somehow sandboxed or 
might the execution of untrusted input lead to somebody getting access to 
my server if I allow such form of data input?

So the question is would it be safe to allow people to upload their data 
files to a service and run them through Ledger CLI to give an output?

Regards,
Madis


-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Upcoming Ledger Release

[Martin Michlmayr]

* Alexis  [2016-01-02 14:01]:
> To test ledger please:

I'm on Debian 8.2 with boost 1.55.0.2.  All ledger tests pass.

Furthermore, the test suite of my personal finance system going back
to 2008 passes.

-- 
Martin Michlmayr
http://www.cyrius.com/

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Upcoming Ledger Release

[John Wiegley]

> Alexis   writes:

> Ledger's bitrot is becoming more and more of a problem (especially with
> newer boost versions, namely 1.58, 1.59, and 1.60) so I think a new release
> is quite necessary.

Ledger's development proceeds at the pace of my needs -- since we don't have
others working on the C++ support, and I have many other matters demanding my
attention.

So, you can be certain it always works with the version of Boost supported by
Nix, since that's what I build it with. It's not actively "rotting". It's just
that we don't have someone dedicated to making it build with the latest Boost
on every possible platform. And I cannot be that person.

> Some folks wanted the next release to be numbered 3.2.0 instead of 3.1.1,
> and I'd like the community to decide. If you have an opinion on the matter
> please reply to this email and make your mark.

Why would it be named 3.2? Does it have any new features or change any APIs?
3.1.1 sounds like the correct number to me.

-- 
John Wiegley  GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com  60E1 46C4 BD1A 7AC1 4BA2

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: untrusted datafile execution

[John Wiegley]

> Madis Väin  writes:

> So the question is would it be safe to allow people to upload their data
> files to a service and run them through Ledger CLI to give an output?

It should be safe (-ish, no guarantees) if you don't compile in the Python
support.

-- 
John Wiegley  GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com  60E1 46C4 BD1A 7AC1 4BA2

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Re-naming accounts..

[Martin Michlmayr]

* Mark Scannell  [2016-01-02 13:31]:
> I have a complex structure of three account sets, all with 
> Ass|Lia|Inc|Exp|Equ, and sub-categories in Assets (Current, Pension, and 
> Fixed). I'd like to apply a regular expression to re-order the structure of 
> the accounts for reporting purposes, without changing the underlying data.
> 
> I know I can do this in the source data, but I'd rather not do that.

I'm not sure what you mean by re-order the structure, but if you want
to change the account names, you can create an account alias.

account Assets:newname
alias Assets:oldname

2015-01-02 * Test
Assets:oldname 10.00 EUR
Equity

$ ledger -f d reg assets
2015-01-02 Test  Assets:newname  10.00 EUR 10.00 EUR

-- 
Martin Michlmayr
http://www.cyrius.com/

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Re-naming accounts..

[Martin Blais]

You could easly write a wrapper script that applies your renames to another
file and then runs your report on that.
Always generate & delete the intermediate file.

Beancount's approach would be different: A plugin would be used to rewrite
the account names in the transactions data structures directly.



On Sat, Jan 2, 2016 at 4:31 PM, Mark Scannell  wrote:

> Hello all --
>
> Is it possible to apply a regular expression to rename accounts?
>
> I have a complex structure of three account sets, all with
> Ass|Lia|Inc|Exp|Equ, and sub-categories in Assets (Current, Pension, and
> Fixed). I'd like to apply a regular expression to re-order the structure of
> the accounts for reporting purposes, without changing the underlying data.
>
> I know I can do this in the source data, but I'd rather not do that.
>
> Thanks!
>
> Mark
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Ledger" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ledger-cli+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re-naming accounts..

[Mark Scannell]

Hello all --

Is it possible to apply a regular expression to rename accounts?

I have a complex structure of three account sets, all with 
Ass|Lia|Inc|Exp|Equ, and sub-categories in Assets (Current, Pension, and 
Fixed). I'd like to apply a regular expression to re-order the structure of 
the accounts for reporting purposes, without changing the underlying data.

I know I can do this in the source data, but I'd rather not do that.

Thanks!

Mark

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.