On Fri, 2006-12-29 at 08:44 +0100, Martin Schulze wrote: > For the sake of the upcoming release, I wonder how many files / users > are affected by this change? Is it really release-critical? If not, > would it not helpe if Thomas provides a script in the gnucash package > that adjusts the keys that are now broken and documents this ... err... > change... in the release notes? What a ludicrous solution. I am going to assume (!) that upstream gnucash will make a suitable automagic change (Josselin or somebody already claimed that gnucash no longer writes these files; on what basis was that claim made?) and then include that if necessary. The problem affects all users of gnucash without exception. Best, of course, is to decide that a freeze means a freeze, and so we simply don't include a destabilizing upstream version of glib into the *frozen* release. Thomas
Attachment:
signature.asc
Description: This is a digitally signed message part