registry team mailing list archive

[Michael Werle <launchpad-micha@xxxxxxxxxxxxxxxx>]

Just FYI, I've encountered another bug in gnustep-base1.19.3.

It appears to have something to do with unicode characters in incoming
XML plist files, and then using the data contained in the plist in an
NSDictionary.  This affects Oolite save-games, which may end up
containing unicode characters.

This new issue does not occur in gnustep-base1.20.  I've not managed to
isolate it yet, and probably won't considering that it's a non-issue in
the current stable release of gnustep.   As far as I'm concerned,
gnustep-base1.19.3 is broken beyond my interest to devote more time to
it, and upstream certainly won't.

I have sadly decided to drop direct support for Lucid due to these
issues - we are continuing to distribute Oolite in an autopackage which
includes a known good version of the gnustep-base library.

More detailed testing with gnustep-base1.20 over the last few weeks
indicates that, apart from the initial bug raised in this thread, it
appears to otherwise be good to use.  According to upstream, the fix for
the whitespace bug will be included in gnustep-base1.20.1.

I would suggest Ubuntu consider upgrading Lucid, and definitely
Maverick, to gnustep-base1.20.1 when it becomes available.  If that is
considered too high a risk, perhaps downgrading to gnustep-base1.18
might be an option?

-- 
gnustep - parsing of XML property lists broken
https://bugs.launchpad.net/bugs/585179
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for Debian.