From 1da44cfe54343d1f5fa3b79ea12ea013c90ce4b8 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 15 Apr 2011 14:03:10 -0400 Subject: [PATCH] response --- ...etup_file_does_not_support_UTF-8_if_XS_is_installed.mdwn | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/doc/bugs/yaml_setup_file_does_not_support_UTF-8_if_XS_is_installed.mdwn b/doc/bugs/yaml_setup_file_does_not_support_UTF-8_if_XS_is_installed.mdwn index a0dad177b..da8f494ff 100644 --- a/doc/bugs/yaml_setup_file_does_not_support_UTF-8_if_XS_is_installed.mdwn +++ b/doc/bugs/yaml_setup_file_does_not_support_UTF-8_if_XS_is_installed.mdwn @@ -32,3 +32,9 @@ preferred one? > Upgrading YAML::XS ([[!debpkg libyaml-libyaml-perl]]) to current sid > version (0.34-1) fixes this bug for me. --[[intrigeri]] + +>> libyaml-syck-perl's description mentions that the module is now +>> deprecated. (I had to do some ugly workaround to make unicode work with +>> Syck earlier.) So it appears the new YAML::Xs is the +>> way to go longterm, and presumably YAML::Any will start depending on it +>> in due course? --[[Joey]] -- 2.26.2