Ticket #17142 (closed defect: fixed)
gnucash 2.2.7 on Leopard doesn't delete old log files
| Reported by: | robert.harris@… | Owned by: | dports@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.6.0 |
| Keywords: | Cc: | macsforever2000@… | |
| Port: | gnucash |
Description
On Leopard, gnucash 2.2.7 retains all log files forever regardless of the appropriate setting in the preferences.
The root cause is that Leopard's strptime() is broken, and always returns NULL in gnc_file_be_remove_old_files().
The reason why I am logging a bug against the port is that there appears to be an alternative version of strptime() supplied with the gnucash distribution, presumably for use on operating systems where no local implementation of this function is provided. I would like to suggest that the portfile is modified so that the gnucash's 'configure' script overrides that native strptime(). I don't know how to do this and would be grateful for a workaround.
Attachments
Change History
comment:3 in reply to: ↑ 2 Changed 5 years ago by robert.harris@…
Replying to robert.harris@…:
Replying to jmr@…:
Is there an upstream bug report for this issue?
Not that I'm aware of.
I've just logged 560052.
comment:4 Changed 4 years ago by macsforever2000@…
I'm not seeing anything obvious in the configure options related to strptime(). I'm attaching the complete output of ./configure --help for gnucash. Let me know if you see something to enable.
comment:7 follow-up: ↓ 8 Changed 3 years ago by jmr@…
Upstream finally checked in a workaround: http://svn.gnucash.org/trac/changeset/19461
comment:8 in reply to: ↑ 7 Changed 2 years ago by dports@…
- Owner changed from macports-tickets@… to dports@…
- Status changed from new to assigned
comment:9 Changed 2 years ago by dports@…
- Status changed from assigned to closed
- Resolution set to fixed
Replying to jmr@…:
Upstream finally checked in a workaround: http://svn.gnucash.org/trac/changeset/19461
And it's in 2.4.0, which I just updated the port to in r74828.
Is there an upstream bug report for this issue?