Could you please consider moving the following packages from ~ppc64 to ppc64. You cannot currently compile the nessus package on ppc64 successfully because it's dependancy of nessus-core fails to build (even though it's marked ppc64). The problem with the core-package is that the config.guess and config.sub are dated 2001 and it's not aware of the ppc64 arch. This 2.2.4 package should also probably be masked. Consider moving these from ~ppc64 to ppc64 to resolve the problem: net-analyzer/libnasl-2.3.1 * net-analyzer/nessus-plugins-2.3.1 * net-analyzer/nessus-core-2.3.1 * net-analyzer/nessus-2.3.1 * net-analyzer/nessus-libraries-2.3.1 * Reproducible: Always Steps to Reproduce: 1. 2. 3.
I'm working on this one - seems that things compile fine when I apply the config.* and compile by hand, but the ebuild fails - investigating
in talking with omkhar, he rightly notes nessus 2.3.x is experimental. we will focus on fixing the 2.2.4 nessus-core config problem then. i agree this is the right course.
ok 2.2.4-r1 is in portage, I've set all archs to testing in case the updated conf.guess and conf.sub break autoconfing on other archs - notifying the other archs as an FYI, test when you can
Patch sent upstream http://bugs.nessus.org/show_bug.cgi?id=1236
this patch is needed on sparc.
btw, repoman complains that the file for the patch is too big.. why don't you just the gnuconfig_update() from the gnuconfig eclass ?
moving the patch was on my todo list. I will look into the mentioned eclass.
all fixed up with proper eclass-age - please test per before
x86: it seems to work ok.. but not keywording since x86 users have no advantage in upgrading amd64: works.. and I marked it stable
Marked 2.2.4-r1 stable on SPARC so that nessus-core will build again.
Seems okay on ppc, but since there is no advantage to bumping for ppc, I'll leave the keywords alone for now.
closing out