Mention workaround.
parent
626cf1b741
commit
5c863d3eb5
|
@ -27,3 +27,8 @@ Joey, as a (hopefully) temporary workaround, what do you think of
|
||||||
explicitely using YAML::Syck (or whatever other YAML implementation
|
explicitely using YAML::Syck (or whatever other YAML implementation
|
||||||
that does not expose this bug) rather than letting YAML::Any pick its
|
that does not expose this bug) rather than letting YAML::Any pick its
|
||||||
preferred one?
|
preferred one?
|
||||||
|
|
||||||
|
--[[intrigeri]]
|
||||||
|
|
||||||
|
> Upgrading YAML::XS ([[!debpkg libyaml-libyaml-perl]]) to current sid
|
||||||
|
> version (0.34-1) fixes this bug for me. --[[intrigeri]]
|
||||||
|
|
Loading…
Reference in New Issue