Erik wrote:
Zac Medico skrev:
Erik wrote:
> I did "emerge --update --deep --newuse world" and it says:
> Calculating world dependencies... done!
>>>> Auto-cleaning packages...
>>>> No outdated packages were found on your system.
> But it seems like it is wrong about "No outdated packages were
found on
> your system.", because when I run "emerge -p world" it says:
> These are the packages that would be merged, in order:
> Calculating world dependencies... done!
> [ebuild U ] media-gfx/digikam-0.9.2 [0.9.1] LINGUAS="-fa% -nds%"
> [blocks B ] media-plugins/digikamimageplugins (is blocking
> media-gfx/digikam-0.9.2)
> So it seems like media-gfx/digikam is outdated despite what "emerge
> --update --deep --newuse world" said. I just wonder how much sense
this
> behaviour makes.
It seems like something that you have installed depends on
digikam-0-9.1 so the deep world update pulled that in instead of the
new version. You can use the --debug option if you want to examine
the dependency strings to see which package pulled in the lower version.
That package depending on digikam-0.9.1 would be digikamimageplugins.
The output of emerge indicates that digikam-0.9.2 cannot be installed
because you have digikamimageplugins installed. In this case, this is
because the plugins have been merged into digikam itself ( see
http://www.kde-apps.org/content/show.php/DigikamImagePlugins?content=16082
), so you can simply unmerge digikamimageplugins and rerun the update.
Blocks can usually be resolved by unmerging an offending package. Do
that with care, however, or you'll do something like the OP of the
recent 'emerge can not work !' thread :-)
Michael
--
gentoo-user@lists.gentoo.org mailing list
