Yes, we can downgrade. This is only in master so I'm not massively concerned about the upgrade path. If the next release is going to be 1.3 then we can either revert the upgrade or be creative and "upgrade" to 1.2.9+really+1.2.
The libxml-namespacesupport-perl recipe has an anonymous python function [1] to “fix” the upstream URL, but is in fact pointing to a development release [2]. The latest release is actually 1.12 [3]. Further, the python anonymous function breaks ptest-perl.bbclass Is it acceptable to revert to the release version? This will lead to a “version going backwards” error being thrown. If this is ok, simply assign this bug to me and I will submit a patch to publish released version. [1] http://git.openembedded.org/openembedded-core/tree/meta/recipes-extended/perl/libxml-namespacesupport-perl_1.12.9.bb#n13 [2] https://metacpan.org/pod/release/PERIGRIN/XML-NamespaceSupport-1.12_9/lib/XML/NamespaceSupport.pm [3] https://metacpan.org/pod/release/PERIGRIN/XML-NamespaceSupport-1.12/lib/XML/NamespaceSupport.pm
Patch in flight: http://lists.openembedded.org/pipermail/openembedded-core/2018-March/149127.html Also available on contrib: http://git.openembedded.org/openembedded-core-contrib/log/?h=timo/libxml-simple-perl-2.25
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=fbf3b0cab7fd072df56043fc4587001147b7b993