Gentoo Archives: gentoo-user

From: Michael Niggli <m.niggli@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] "emerge --update --deep --newuse world" fails to update all packages
Date: Sat, 23 Feb 2008 20:44:05
Message-Id: 47C08590.8080800@gmail.com
In Reply to: Re: [gentoo-user] "emerge --update --deep --newuse world" fails to update all packages by Erik
1 Erik wrote:
2 > Zac Medico skrev:
3 >> Erik wrote:
4 >> > I did "emerge --update --deep --newuse world" and it says:
5 >> > Calculating world dependencies... done!
6 >> >>>> Auto-cleaning packages...
7 >> >>>> No outdated packages were found on your system.
8 >>
9 >> > But it seems like it is wrong about "No outdated packages were
10 >> found on
11 >> > your system.", because when I run "emerge -p world" it says:
12 >>
13 >> > These are the packages that would be merged, in order:
14 >>
15 >> > Calculating world dependencies... done!
16 >> > [ebuild U ] media-gfx/digikam-0.9.2 [0.9.1] LINGUAS="-fa% -nds%"
17 >> > [blocks B ] media-plugins/digikamimageplugins (is blocking
18 >> > media-gfx/digikam-0.9.2)
19 >>
20 >>
21 >> > So it seems like media-gfx/digikam is outdated despite what "emerge
22 >> > --update --deep --newuse world" said. I just wonder how much sense
23 >> this
24 >> > behaviour makes.
25 >>
26 >>
27 >> It seems like something that you have installed depends on
28 >> digikam-0-9.1 so the deep world update pulled that in instead of the
29 >> new version. You can use the --debug option if you want to examine
30 >> the dependency strings to see which package pulled in the lower version.
31 > That package depending on digikam-0.9.1 would be digikamimageplugins.
32 The output of emerge indicates that digikam-0.9.2 cannot be installed
33 because you have digikamimageplugins installed. In this case, this is
34 because the plugins have been merged into digikam itself ( see
35 http://www.kde-apps.org/content/show.php/DigikamImagePlugins?content=16082
36 ), so you can simply unmerge digikamimageplugins and rerun the update.
37 Blocks can usually be resolved by unmerging an offending package. Do
38 that with care, however, or you'll do something like the OP of the
39 recent 'emerge can not work !' thread :-)
40
41
42 Michael
43
44 --
45 gentoo-user@l.g.o mailing list