Bug 815901 – net-im/telepathy-logger-0.8.2-r1: xml.parsers.expat.ExpatError: not well-formed (invalid token): line 33, column 26

• Product: Gentoo Linux
• Status: UNCONFIRMED ---

[Description Geoff Madden 2021-10-03 06:12:46 UTC]

Created attachment 742596 [details]
build log for telepathy-logger-0.8.2-r1

telepathy logger has a problem with the definitions in the extension directory,& consequently stops compiling

[Comment 1 Geoff Madden 2021-10-03 06:14:07 UTC]

Created attachment 742599 [details]
emerge info for a new build on a new processor

[Comment 2 Andreas Sturmlechner 2021-10-03 09:08:07 UTC]

@bug reporter: Missing emerge --info.

A weird error message to tell us about missing PYTHON_REQ_USE="xml(+)" maybe...?

[Comment 3 Geoff Madden 2021-10-04 06:09:30 UTC]

Comment on attachment 742599 [details]
emerge info for a new build on a new processor

dunno what went on,with the emerge.inf file as that was supposed to be the build.log

[Comment 4 Geoff Madden 2021-10-04 06:10:16 UTC]

Created attachment 742899 [details]
emerge info

[Comment 5 Geoff Madden 2021-10-04 06:25:30 UTC]

Actually I'm at a loss as to why this file is pulled into a kde install,though I see that net-libs/telepathy-logger-qt has it as an indispensable part of the install.Also I'm at a loss as to why this version fallsover,whereas on other machines it appears to compile ok (so far).

[Comment 6 Geoff Madden 2021-10-09 07:38:57 UTC]

Created attachment 743937 [details]
elibtool.log

[Comment 7 Sam James 2021-10-09 08:03:51 UTC]

Aha, may be locale related: https://forums.gentoo.org/viewtopic-t-1119586-start-0.html.

[Comment 8 Ionen Wolkens 2021-10-09 08:29:21 UTC]

Yep, seem still affected. Nice digging that old thread.

LANG=en_AU emerge = fails
LANG=en_AU LC_CTYPE=C emerge = fails
LANG=en_AU LC_CTYPE=C.utf8 emerge = works
LANG=en.AU.utf8 emerge = works too of course

My old guess wasn't fully educated, it actually need .utf8 and so EAPI defaults won't cut it.

Since this is a python ebuild the fix is simple though, toss python_export_utf8_locale at start of src_configure.

[Comment 9 Ionen Wolkens 2021-10-09 09:00:40 UTC]

(In reply to Ionen Wolkens from comment #8)
> Since this is a python ebuild the fix is simple though, toss
> python_export_utf8_locale at start of src_configure.
Then again, that function still looks kind of fragile.

[Comment 10 Geoff Madden 2021-10-14 07:30:28 UTC]

(In reply to Ionen Wolkens from comment #9)
> (In reply to Ionen Wolkens from comment #8)
> > Since this is a python ebuild the fix is simple though, toss
> > python_export_utf8_locale at start of src_configure.
> Then again, that function still looks kind of fragile.

I was able to get a compile on different machines by making the locale a *.utf-8
in my case it was en_AU.
The original problem was caused by the machine being set to en_AU,which went unnoticed on the original @system install and was not till I was installing the kde framework that it showed up

[Comment 11 Anthony Mendez 2021-10-28 06:40:38 UTC]

Same problem fixed by switching locale from 'en_US' to 'en_US.utf8'.