hi, i think 2.0.10a build of nessus is broken. it builds packages in wrong order. a 'screenshot': root@1g root # emerge -pv nessus These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild N ] net-analyzer/nessus-core-2.0.10a +X -debug +gtk2 -prelude +tcpd 53 kB [ebuild N ] net-analyzer/nessus-plugins-2.0.10a 0 kB [ebuild N ] net-analyzer/nessus-libraries-2.0.10a +ssl 0 kB [ebuild N ] net-analyzer/nessus-2.0.10a [empty/missing/bad digest] Total size of downloads: 53 kB the above build order is incorrect, nessus-libraries is the first to be build, as nessus-core depends on nessus-libraries regards,
hmm it seems that its not ebuild's fault: DEPEND=">=net-analyzer/nessus-libraries-${PV} >=net-analyzer/libnasl-${PV} >=net-analyzer/nessus-core-${PV} >=net-analyzer/nessus-plugins-${PV}" seems that emerge fails to build the packages in correct order when libnasl is already installed. i removed libnasl and now the packages are correctly build. strange...
$ emerge -pve nessus | grep -e net-analyzer [ebuild N ] net-analyzer/nessus-libraries-2.0.9 +ssl 0 kB [2] [ebuild N ] net-analyzer/libnasl-2.0.9 0 kB [2] [ebuild N ] net-analyzer/nessus-core-2.0.9 +X -debug +gtk2 +prelude +tcpd 0 kB [2] [ebuild N ] net-analyzer/nessus-plugins-2.0.9 0 kB [2] [ebuild N ] net-analyzer/nessus-2.0.9 [empty/missing/bad digest] [2] when I try to do a empty-tree emerge of nessus.. Which looks like it does what is expected of it. One way to re-produce your error is to install libnasl and then remove nessus-libraries. And then try to re-emerge nessus-core / nessus-plugins after that... But this does not happen during normal operation of the emerge process. I will put this bug in the "invalid" pile. If you think differently please re-open it.
