> I leave to you the task now of locating the bug report that you didn't > bother looking for the first time.
I got the same error, and quickly scanned bugs.debian.org/gnucash for hash-for-each. I found this bug, with no explanation or pointer to the "correct" bug. So now I will spend some time looking through bugs that don't have "hash-for-each" in the subject line until I find the right bug, and then find out whether there is a fix for the bug. Is there any reason to subject users to this? Couldn't you just have merged the bug report with the preexisting bug? I understand you're trying to teach someone a lesson, but I think it's a disservice to our users. Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
