Looks like `eselect news` only works with paludis and additionally does a poor job when paludis is installed but not configured: With paludis not installed: # eselect news list !!! Error: Can't load module news Killed No obvious hint why it failed unless you check the code. With paludis installed but not configured (fresh install): # eselect news list Unhandled exception: * In program paludis --list-repositories: * When making environment from specification '': * When loading paludis configuration: * Paludis configuration error: Paludis configuration error: Can't find configuration directory (tried '/root/.paludis', '/etc/paludis') (paludis::PaludisConfigNoDirectoryError) Unread news items: (none found) Unhandled exception: * In program paludis --list-repositories: * When making environment from specification '': * When loading paludis configuration: * Paludis configuration error: Paludis configuration error: Can't find configuration directory (tried '/root/.paludis', '/etc/paludis') (paludis::PaludisConfigNoDirectoryError) Read news items: (none found) Use case here was simply installing paludis-0.24.1 with portage-2.1.2.5 (which triggered the message about unread news and further pointed to `eselect news`)
Ok, spb just told me that the news module is part of paludis, which invalidates this bug mostly. Sorry for not checking that earlier. The error about not being able to load a module could be more explicit though that the module couldn't be found.
would be nice if this bug is fixes soon thx
try 'eselect news-tng'
Is there a fix for that, I mean that paludis calls news-tng instead of news. Where does this come from?
(In reply to comment #4) > Is there a fix for that, I mean that paludis calls news-tng instead of news. > Where does this come from? The module was renamed from "news-tng" to "news" in app-admin/eselect-1.2_rc1. So if you install this version you get the new functionality with the familiar "eselect news" command.