> There's a new version of gnucash in unstable, 2.0.1-1, which is a
> substantial upgrade from the previous 1.8 tree.
Yes, I've been using 2.0 since it got into unstable. It works fine.
> Please could you confirm a few things and retest in the current version?
>
> 1. When you open your gnucash file after running the cron job and save
> the file normally, is it recompressed?
Yes, in my example, the file dated "2006-02-14 20:00" was the backup of
the file created by the "gnucash --add-price-quotes" call (uncompressed)
while the file dated "2006-02-15 00:37" was the newly saved one
(compressed again). The one dated "2006-02-14 00:36" was the backup of
my previous manually saved file.
> 2. In your bug report, which is the file being generated by the cron
> job? .xac files are normally backup files created by gnucash, your main
> data file (comptes-euro.gnucash) appears compressed from the bug report
> text.
I didn't look at the code, I just assumed that the xac file was the
latest version moved to a new name, since it kept the original
timestamp. So the timeline would be:
- I edit and save the file manually on "2006-02-14 00:36"
- cron runs "gnucash --add-price-quotes" on "2006-02-14 20:00"
- I edit and save the file manually on "2006-02-15 00:37"
Anyway, the problem is indeed fixed in 2.0.1-1, at least (I don't think
I checked while running 2.0.0). My latest file, generated by the cron
run, is compressed:
-rw-r--r-- 1 pavageau pavageau 658850 2006-08-17 20:00 comptes-euro.gnucash
and so are all the previous xac files.
Frank
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
