This has high priority since we are suppling a vulnerable version since a lot of time... but I am unable to bump it :-S I attach ebuild diff and build.log (some months ago the problem was at runtime, as I was getting warning on every started program depending on it) Thanks Reproducible: Always
Created attachment 260860 [details, diff] libxml2.ebuild.diff
Created attachment 260862 [details, diff] libxml2-2.7.8-reactivate-script.patch
Created attachment 260863 [details, diff] libxml2-2.7.8-xpath-freeing.patch
Created attachment 260865 [details, diff] libxml2-2.7.8-xpath-freeing2.patch
Created attachment 260867 [details, diff] libxml2-2.7.8-xpath-memory.patch
Created attachment 261079 [details, diff] patch just use this or this(ebuild with subj path) https://github.com/megabaks/stuff/tree/master/dev-libs/libxml2
libxml2-2.7.8-xpath-freeing.patch appears to have a bug. It's missing the {} after the added if, so it's always popping. libxml2-2.7.8-xpath-freeing2.patch appears to be correct.
(In reply to comment #7) > libxml2-2.7.8-xpath-freeing.patch appears to have a bug. It's missing the {} > after the added if, so it's always popping. libxml2-2.7.8-xpath-freeing2.patch > appears to be correct. > Yes, but the second patch should fix it and, then, build shouldn't die :-/
Created attachment 261528 [details] build.log
+*libxml2-2.7.8 (11 Feb 2011) + + 11 Feb 2011; Pacho Ramos <pacho@gentoo.org> -libxml2-2.7.6.ebuild, + +libxml2-2.7.8.ebuild, +files/libxml2-2.7.8-reactivate-script.patch, + +files/libxml2-2.7.8-xpath-freeing.patch, + +files/libxml2-2.7.8-xpath-freeing2.patch, + +files/libxml2-2.7.8-xpath-memory.patch: + Version bump including security fixes, bump to eapi3, remove old. +