The nessus packages were updated to add 2.3.1, however the Nessus metapackage was not updated, so an emerge -uD world will emerge the 3 or 4 packages for nessus, and then upon completion, issuing another emerge -uD world will downgrade it back to 2.3.0 - back and forth. Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: Round robin between 2.3.0/2.3.1 Expected Results: Upgrading to 2.3.1 should have worked. I attempted to create a 2.3.1 ebuild in my overlay, however it doesn't seem to read it.
Need a 2.3.1 ebuild for the nessus meta package netmon peeps.
just rename the old one
so that's what I didn't finish the day I passed out on my keyboard... *sigh*. In CVS. Sorry for trouble guys.