Re: [Gimp-developer] intltool 0.30 produces XML error in gimp-tips.xml
On Dec 1, 2004, at 5:57 AM, Sven Neumann wrote: Brion Vibber <[EMAIL PROTECTED]> writes: What I don't understand here is why does fink use autogen.sh at all? It doesn't; *I* do when I build Gimp from CVS to test it. OK then. I have changed the warning in autogen.sh. Hopefully it is more clear now. Thanks! The Fink GNOME package maintainers will include an updated intltools package along with coming GNOME 2.8 updates. -- brion vibber (brion @ pobox.com) PGP.sig Description: This is a digitally signed message part
Re: [Gimp-developer] intltool 0.30 produces XML error in gimp-tips.xml
Hi, Brion Vibber <[EMAIL PROTECTED]> writes: >> What I don't understand here is why does fink use autogen.sh at all? > > It doesn't; *I* do when I build Gimp from CVS to test it. OK then. I have changed the warning in autogen.sh. Hopefully it is more clear now. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] intltool 0.30 produces XML error in gimp-tips.xml
On Dec 1, 2004, at 4:55 AM, Sven Neumann wrote: Brion Vibber <[EMAIL PROTECTED]> writes: I'll see about submitting an update to the fink package, but perhaps autogen.sh should be a little pickier to make sure bogus builds don't make it out the door. I don't think so. If we would have let autogen.sh fail, people couldn't have been able to build GIMP from CVS until a fixed version of intltool was released (which wasn't the case for about a year). What I don't understand here is why does fink use autogen.sh at all? It doesn't; *I* do when I build Gimp from CVS to test it. -- brion vibber (brion @ pobox.com) PGP.sig Description: This is a digitally signed message part
Re: [Gimp-developer] intltool 0.30 produces XML error in gimp-tips.xml
Hi, Brion Vibber <[EMAIL PROTECTED]> writes: > autogen.sh checks for intltool < 0.28 or > 0.31 due to a known problem > with corrupt XML output, but if you have a bad version the script just > says "the problem is harmless, you may continue the build" and > automatically moves on. > > It appears however to actually produce a corrupt gimp-tips.xml if you > have intltool 0.30 (which is the current version available in the fink > package set for Mac OS X). Those tips containing get horribly > munged... On startup, Gimp complains on the console: > >Error while parsing '/opt/gimp-2.1/share/gimp/2.0/tips/gimp-tips.xml': >Error on line 48 char 29: ')' is not a valid character following the >characters ' > As a result, only the first 4 tips actually get shown on a build > compiled this way; the rest are discarded when the error halts XML > parsing. Rebuilding it with intltool 0.32.1 gets things working right. > > I'll see about submitting an update to the fink package, but perhaps > autogen.sh should be a little pickier to make sure bogus builds don't > make it out the door. I don't think so. If we would have let autogen.sh fail, people couldn't have been able to build GIMP from CVS until a fixed version of intltool was released (which wasn't the case for about a year). What I don't understand here is why does fink use autogen.sh at all? fink should use a released tarball and the released GIMP tarballs have been created with a working version of intltool and thus include working versions of the intltool scripts. You are not supposed to run autogen.sh unless you have a very good reason to do so. Does fink have such a reason? If so, why haven't we been told about it yet? Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] intltool 0.30 produces XML error in gimp-tips.xml
autogen.sh checks for intltool < 0.28 or > 0.31 due to a known problem with corrupt XML output, but if you have a bad version the script just says "the problem is harmless, you may continue the build" and automatically moves on. It appears however to actually produce a corrupt gimp-tips.xml if you have intltool 0.30 (which is the current version available in the fink package set for Mac OS X). Those tips containing get horribly munged... On startup, Gimp complains on the console: Error while parsing '/opt/gimp-2.1/share/gimp/2.0/tips/gimp-tips.xml': Error on line 48 char 29: ')' is not a valid character following the characters ' As a result, only the first 4 tips actually get shown on a build compiled this way; the rest are discarded when the error halts XML parsing. Rebuilding it with intltool 0.32.1 gets things working right. I'll see about submitting an update to the fink package, but perhaps autogen.sh should be a little pickier to make sure bogus builds don't make it out the door. -- brion vibber (brion @ pobox.com) PGP.sig Description: This is a digitally signed message part
