Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#67859 - [hledger] Output of negative numbers mangled in 1.19, fixed in 1.19.1

Attached to Project: Community Packages
Opened by Jorge Luis Martinez Gomez (jol) - Wednesday, 09 September 2020, 21:27 GMT
Last edited by Felix Yan (felixonmars) - Saturday, 16 January 2021, 22:59 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Felix Yan (felixonmars)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

At least the output of the register and balance subcommands have their formatting around negative numbers mangled.

This is fixed when upgrading to 1.19.1.

Additional info:
* package version(s): 1.19-1 and 1.19-3

Steps to reproduce:

```
$ cat test.hledger
2020-09-09 foo
account:opening -10 USD
assets:wallet 10 USD
$ LEDGER_FILE=test.hledger hledger r
2020-09-09 foo account:opening .. USD .. USD
assets:wallet 10 USD 0
$ LEDGER_FILE=test.hledger hledger b
-10 USD account:opening
10 USD assets:wallet
--------------------
0
```

If I upgrade to 1.19.1, the output is then:

```
$ LEDGER_FILE=test.hledger hledger r
2020-09-09 foo account:opening -10 USD -10 USD
assets:wallet 10 USD 0
$ LEDGER_FILE=test.hledger hledger b
-10 USD account:opening
10 USD assets:wallet
--------------------
0
```
This task depends upon

Closed by  Felix Yan (felixonmars)
Saturday, 16 January 2021, 22:59 GMT
Reason for closing:  Fixed
Additional comments about closing:  1.19.1
Comment by Jorge Luis Martinez Gomez (jol) - Wednesday, 09 September 2020, 21:32 GMT
The text in the report got its spaces collapsed. I'll attach the output as a file, then.
   hledger-bug-1.19.txt (0.9 KiB)
Comment by Jorge Luis Martinez Gomez (jol) - Monday, 28 September 2020, 16:23 GMT
The package has been updated, so this issue is fixed.

Loading...