We currently get this message: WARN: postinst Neon has a policy of breaking API across minor versions, this means that any package that links against Neon may be broken after updating. They will remain broken until they are ported to the new API. You can downgrade Neon to the previous version by doing: emerge --oneshot '<net-libs/neon-0.29' You may also have to downgrade any package that has not been ported to the new API yet. But: 1. If any other package in the tree requires older versions, probably neon should be slotted 2. Most of the problems would be solved simply running revdep-rebuild, no? 3. Newer neon versions should be stabilized when depending packages are ported to new API Thanks Reproducible: Always
+ 05 Sep 2012; Pacho Ramos <pacho@gentoo.org> -neon-0.29.6.ebuild, + neon-0.29.6-r1.ebuild: + Drop suggestion to manually downgrade package as explained in bug #421643, + drop old. +