sotn3m wrote:Code: Select all
* No versions of 'x11-base/opengl-update' are available
These mean that the named package has been masked or removed from the tree, you can uninstall it.
... When adding installed package 'kde-base/kreadconfig-3.5.0::installed':
... Ignoring run dependencies due to exception 'Error searching for '~kde-base/kde-env-3': no available versions' (paludis::AllMaskedError)
... When adding installed package 'kde-base/kcheckpass-3.5.0::installed':
... Ignoring run dependencies due to exception 'Error searching for '~kde-base/kde-env-3': no available versions' (paludis::AllMaskedError)
... When adding installed package 'kde-base/kdcop-3.5.1::installed':
... Ignoring run dependencies due to exception 'Error searching for '~kde-base/kde-env-3': no available versions' (paludis::AllMaskedError)
... When adding installed package 'kde-base/kdebugdialog-3.5.0::installed':
... Ignoring run dependencies due to exception 'Error searching for '~kde-base/kde-env-3': no available versions' (paludis::AllMaskedError)
... When adding installed package 'kde-base/kstart-3.5.0::installed':
... Ignoring run dependencies due to exception 'Error searching for '~kde-base/kde-env-3': no available versions'
(paludis::AllMaskedError)
... When adding installed package 'kde-misc/krusader-1.70.1::installed':
... Ignoring run dependencies due to exception 'Error searching for '~kde-base/kde-env-3': no available versions' (paludis::AllMaskedError)
... When adding installed package 'kde-misc/krename-3.0.11-r1::installed':
... Ignoring run dependencies due to exception 'Error searching for '~kde-base/kde-env-3': no available versions' (paludis::AllMaskedError)[/code]
These are a little different: kde-env has been removed and you've presumably uninstalled it, but the record of the installed packages still refers to it. To fix it, you need to reinstall the package depending on kde-env, ie kreadconfig, kcheckpass, etc. This sort of thing will happen occasionally when package dependencies get changed around - it's not an issue for Portage because it ignores the installed dependency information. IIRC there are plans to change Portage, so when that happens I suppose the devs'll come up with a nicer way to handle things.
Another way this can happen is if a package gets renamed or moved to a different category: Portage can automatically update its records, but Paludis doesn't support that yet (it will at some point). Until it does. the easiest way to handle it would be to remove the package using its old name and reinstall it with the new one, and reinstall any dependants to update the installed database.
Code: Select all
... When adding installed package 'dev-lang/tk-8.4.9::installed':
... When adding run dependencies as post dependencies:
... When adding PackageDepSpec 'virtual/x11':
... No visible packages matching 'virtual/x11', falling back to installed package
... When adding installed package 'app-vim/extra-syntax-2::installed':
... When adding run dependencies as post dependencies:
... When adding PackageDepSpec 'app-vim/doxygen-syntax':
... No visible packages matching 'app-vim/doxygen-syntax', falling back to installed package 'app-vim/doxygen-syntax-1.12::installed'
This is a mixture of the previous two: you can remove virtual/x11 and doxygen-syntax,
and reinstall tk and extra-syntax to update the old dependency record.