why are new upstream versions of glib being uploaded?

[Marc 'HE' Brockschmidt]

Thomas Bushnell BSG <tb at becket.net> writes:
> Why are new upstream releases being added to upstable of the glib2.0
> package?  We are in a freeze, I thought.

Yes, but the new glib2.0 release is from upstream's stable series, where
only bugs are fixed. I reviewed all changes before Loic Minier uploaded
the new version and thought them to not a problem.

> And one seems perhaps to be responsible for a regression in gnucash
> (see #404585).

Yes, this is due to a stricter input validation in gkeyfile.c. The
validation is an ugly C replacement for this:
m!^[-_/+.[:alnum:]]+(\[[-_.@[:alnum:]]+\])?$!

This change should probably be reverted for etch (or be reduced to a
warning), as we can't see which other applications use weird stuff as
keys. lool, could you please comment on that?

Marc