Bug#404888: glib2.0: cannot go into testing; causes gnucash regrsession

[Thomas Bushnell BSG]

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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20061229/3ef4a7c4/attachment-0001.pgp