Despite what Josselin has said, I can see no indication from a brief perusal of the upstream branch sources in trac that upstream gnucash either no longer uses these key files or has changed away from the keys with embedded spaces. I have asked gnucash upstream for their thoughts on the long-term issue, but that doesn't address what Debian should do now. It seems to me that there are four ways forward: 1) Decide that glib should not migrate into testing (it is a freeze, after all); if there are particular fixes of RC issues in more recent versions, then those fixes should be added, but otherwise the wholesale importation of many changes should not be permitted. 2) Decide that glib can migrate into testing, with the particular change of checking key values reverted to its pre-2.12.5 behavior, since this is a destabilizing change in the Debian context. 3) Decide that glib can migrate into testing with the destabilizing change intact, migrate an upstream gnucash fix into testing at the same time. 4) Decide that glib can migrate into testing with the destabilizing change intact, and gnucash does not, since the gnucash bug is only severity important. I have ranked these in the order I prefer them, of course. I apologize if there are further options I have not listed. Note that option (3) depends on upstream's ability to fix the problem quickly, *and* is likely to be error prone. If our priority is the *release*, then options (1) and (2) are the best choices. Thomas
Attachment:
signature.asc
Description: This is a digitally signed message part