[kdesrc-build] [Bug 399610] Runtime Error: The KDE Project database could not be understood because of invalid character
https://bugs.kde.org/show_bug.cgi?id=399610 --- Comment #9 from Michael Pyne --- Thanks for the update. If it helps, it's already fixed upstream. https://github.com/perlpunk/YAML-PP-p5/commit/48a79a4190d52ab280b0f5296e81298b8424419a -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 399610] Runtime Error: The KDE Project database could not be understood because of invalid character
https://bugs.kde.org/show_bug.cgi?id=399610 --- Comment #8 from Gregor Mi --- I installed YAML::XS with sudo zypper in perl-YAML-LibYAML Now, the KDE project database can now be parsed even without the "" -- displayname: Éric Bischoff <- +- displayname: "Éric Bischoff" Side note: "one of (YAML::XS, YAML::PP, YAML::Syck)" I always skipped YAML::XS because it was not obvious which package to choose, see some of the output of $ zypper se perl-yaml S | Name | Summary | Type ---+---+---+--- | perl-YAML | YAML Ain't Markup Language™ | package | perl-YAML-LibYAML | Perl YAML Serialization using XS and libyaml | package | perl-YAML-PP | YAML 1.2 processor | package | perl-YAML-Perl| Pure Perl YAML Implementation | package | perl-YAML-Syck| Fast, lightweight YAML loader and dumper | package | perl-YAML-Tiny| Read/Write YAML files with as little code as possible | package -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 399610] Runtime Error: The KDE Project database could not be understood because of invalid character
https://bugs.kde.org/show_bug.cgi?id=399610 Michael Pyne changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #7 from Michael Pyne --- I've reported a bug against YAML::PP (at what appears to be the right upstream) with a testcase: https://github.com/perlpunk/YAML-PP-p5/issues/5 In the meantime Ben has committed a workaround that should permit kdesrc-build to work again. Thanks for the report, I wouldn't have noticed because I use YAML::XS myself. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 399610] Runtime Error: The KDE Project database could not be understood because of invalid character
https://bugs.kde.org/show_bug.cgi?id=399610 --- Comment #6 from Michael Pyne --- I think this is a YAML::PP bug, but it is possible to adjust metadata.yaml to allow Éric's name to still be spelled properly: diff --git a/projects/extragear/utils/keurocalc/metadata.yaml b/projects/extragear/utils/keurocalc/metadata.yaml index 2f89c70..f706b2f 100644 --- a/projects/extragear/utils/keurocalc/metadata.yaml +++ b/projects/extragear/utils/keurocalc/metadata.yaml @@ -2,7 +2,7 @@ description: Utility to handle currency conversions between European currencies hasrepo: true icon: null members: -- displayname: Éric Bischoff +- displayname: "Éric Bischoff" username: bischoff name: KEuroCalc projectpath: extragear/utils/keurocalc Putting the string in quotes makes clear to YAML::PP that it's a string and not some other potential bit of YAML syntax. All the online validators I can find claim the original was valid YAML, and the spec itself seems to confirm that as well (allowing any printable Unicode character to be part of a "plain scalar"). Interestingly, using "☃ric Bischoff" as the name, without quotes, *also* works with YAML::PP. So I suspect this is an instance of the Perl "Unicode bug" affecting strings that have characters in the range U+0080-U+0100; these are treated internally as local-8-bit strings instead of utf8 by default and this has some implications for how other Perl operators process those strings even if they were read in as utf8. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 399610] Runtime Error: The KDE Project database could not be understood because of invalid character
https://bugs.kde.org/show_bug.cgi?id=399610 --- Comment #5 from Michael Pyne --- YAML::XS does indeed work fine. I can reproduce the error by forcing the use of YAML::PP. So a decent workaround for now is YAML::XS, but I will see about ensuring YAML::PP can work as well, or remove it as an option. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 399610] Runtime Error: The KDE Project database could not be understood because of invalid character
https://bugs.kde.org/show_bug.cgi?id=399610 --- Comment #4 from Michael Pyne --- (In reply to Ben Cooksley from comment #3) > Hmm. Not sure what to do in that case. > > Michael, do we need to encode all the names in the metadata.yaml files that > use non-ASCII characters to keep Perl's YAML interpreter happy? > > (Python doesn't seem to mind UTF-8) No, UTF-8 should be quite acceptable, there shouldn't need to be an ASCII requirement here. Gregor, does installing the Perl YAML::XS module fix the issue? It's something to the effect of libyaml-libyaml-perl on Debian distros. YAML::PP appears to suppose utf-8, but I might not be passing the utf-8 encoding information right in Perl. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 399610] Runtime Error: The KDE Project database could not be understood because of invalid character
https://bugs.kde.org/show_bug.cgi?id=399610 --- Comment #3 from Ben Cooksley --- Hmm. Not sure what to do in that case. Michael, do we need to encode all the names in the metadata.yaml files that use non-ASCII characters to keep Perl's YAML interpreter happy? (Python doesn't seem to mind UTF-8) -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 399610] Runtime Error: The KDE Project database could not be understood because of invalid character
https://bugs.kde.org/show_bug.cgi?id=399610 --- Comment #2 from Gregor Mi --- With removing the É from the name I just wanted to show that this causes the error. I also think that this is not the right way to solve the problem. Here my locale output: $ locale LANG=de_DE.UTF-8 LC_CTYPE=en_US.UTF-8 LC_NUMERIC="de_DE.UTF-8" LC_TIME="de_DE.UTF-8" LC_COLLATE="de_DE.UTF-8" LC_MONETARY="de_DE.UTF-8" LC_MESSAGES="de_DE.UTF-8" LC_PAPER="de_DE.UTF-8" LC_NAME="de_DE.UTF-8" LC_ADDRESS="de_DE.UTF-8" LC_TELEPHONE="de_DE.UTF-8" LC_MEASUREMENT="de_DE.UTF-8" LC_IDENTIFICATION="de_DE.UTF-8" LC_ALL= $ echo $LANG de_DE.UTF-8 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 399610] Runtime Error: The KDE Project database could not be understood because of invalid character
https://bugs.kde.org/show_bug.cgi?id=399610 --- Comment #1 from Ben Cooksley --- Mangling Éric's name in this case is the wrong thing to do I think. Please check the LANG value on your system, along with the output of "locale" to ensure that you are running a UTF-8 locale. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 399610] Runtime Error: The KDE Project database could not be understood because of invalid character
https://bugs.kde.org/show_bug.cgi?id=399610 Gregor Mi changed: What|Removed |Added CC||bcooks...@kde.org -- You are receiving this mail because: You are watching all bug changes.
