Hi all! So, I gotta admit as upstream dev of two of the modules that failed, that this is partly my fault. And I am happy to report that I have fixed it upstream for two packages.
The root cause is that librdf-ns-perl is based on a crowd-sourced database, and sometimes crowd-sourced things change. The occasional breakage is usually a small price to pay for access to the large, crowdsourced database, but for a stable environment, like Debian, it can cause some headaches. Finding the right balance can sometimes be hard, and I therefore suggested one change to librdf-ns-perl that made it into this release, and that has now been reverted. I still think that the change is appropriate, and I think it should not be applied, as it merely fixes a symptom and not the root cause, and might lead to breakage for those who do not rely on RDF::NS for the entire lifetime of the distribution, but upgrades from upstream. Moreover, I suspect it doesn't fix the problem for librdf-aref-perl, that's still failing, right? The breakage seen there is directly due to that a prefix has changed in the crowdsourced database, and only upstream can really fix that. The actual root cause in libatteanx-serializer-rdfa-perl and librdf-trine- serializer-rdfa-perl was a particularly embarrassing and silly mistake on my part. It just failed very rarely, since testers would generally have both RDF::NS and RDF::Prefixes installed... I have now released a new upstream version of both, and I think that librdf-ns-perl should be unchanged from the upstream. Best, Kjetil