1 |
On Sat, 19 Sep 2015 21:36:06 +0200, lee wrote: |
2 |
|
3 |
> emerge -j 8 -a --update --newuse --deep --with-bdeps=y |
4 |
> @world |
5 |
> |
6 |
> * IMPORTANT: 4 news items need reading for repository 'gentoo'. |
7 |
> * Use eselect news read to view new items. |
8 |
> |
9 |
> |
10 |
> These are the packages that would be merged, in order: |
11 |
> |
12 |
> Calculating dependencies... done! |
13 |
> |
14 |
> !!! Multiple package instances within a single package slot have been |
15 |
> pulled !!! into the dependency graph, resulting in a slot conflict: |
16 |
> |
17 |
> dev-libs/boost:0 |
18 |
> |
19 |
> (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for |
20 |
> merge) pulled in by (no parents that aren't satisfied by other packages |
21 |
> in this slot) |
22 |
> |
23 |
> (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for |
24 |
> merge) pulled in by dev-libs/boost:0/1.55.0= required by |
25 |
> (dev-libs/librevenge-0.0.2:0/0::gentoo, installed) |
26 |
> ^^^^^^^^^^ (and 2 more with the same problem) |
27 |
> |
28 |
> dev-util/boost-build:0 |
29 |
> |
30 |
> (dev-util/boost-build-1.55.0:0/0::gentoo, installed) pulled in by |
31 |
> =dev-util/boost-build-1.55* required by |
32 |
> (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for merge) |
33 |
> ^ |
34 |
> ^^^^^ |
35 |
> |
36 |
> (dev-util/boost-build-1.56.0:0/0::gentoo, ebuild scheduled for merge) |
37 |
> pulled in by =dev-util/boost-build-1.56* required by |
38 |
> (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for merge) |
39 |
> ^ |
40 |
> ^^^^^ |
41 |
> |
42 |
> media-video/ffmpeg:0 |
43 |
> |
44 |
> (media-video/ffmpeg-2.6.3:0/54.56.56::gentoo, ebuild scheduled for |
45 |
> merge) pulled in by (no parents that aren't satisfied by other packages |
46 |
> in this slot) |
47 |
> |
48 |
> (media-video/ffmpeg-2.2.14:0/52.55.55::gentoo, installed) pulled in by |
49 |
> media-video/ffmpeg:0/52.55.55=[vdpau] required by |
50 |
> (media-libs/mlt-0.9.0:0/0::gentoo, installed) |
51 |
> ^^^^^^^^^^^ |
52 |
These are unimportant, it is simply portage telling you it is not |
53 |
updating some packages to the latest available and why. Personally, I |
54 |
believe this sort of output should only be shown when using --verbose. |
55 |
|
56 |
> It may be possible to solve this problem by using package.mask to |
57 |
> prevent one of those packages from being selected. However, it is also |
58 |
> possible that conflicting dependencies exist such that they are |
59 |
> impossible to satisfy simultaneously. If such a conflict exists in |
60 |
> the dependencies of two different packages, then those packages can |
61 |
> not be installed simultaneously. |
62 |
> |
63 |
> For more information, see MASKED PACKAGES section in the emerge man |
64 |
> page or refer to the Gentoo Handbook. |
65 |
> |
66 |
> |
67 |
> !!! The ebuild selected to satisfy "sci-libs/hdf5" has unmet |
68 |
> requirements. |
69 |
> - sci-libs/hdf5-1.8.14-r1::gentoo USE="cxx fortran threads zlib -debug |
70 |
> -examples -fortran2003 -mpi -static-libs -szip" |
71 |
> |
72 |
> The following REQUIRED_USE flag constraints are unsatisfied: |
73 |
> threads? ( !cxx !fortran ) |
74 |
|
75 |
This is blocking you and the reason is given, if you have the threads |
76 |
flag on, cxx and fortran must be off. You have both threads and cxx on |
77 |
which won't work. |
78 |
|
79 |
> Why can't we just update like we can with any other distribution but |
80 |
> have to run into dependency problems all the time instead? |
81 |
|
82 |
These aren't dependency problems, they are conflicting USE flags, a |
83 |
situation that cannot arise with a binary distro. If you want the |
84 |
flexibility that USE flags offer, you have to accept that not all |
85 |
combinations will work together. |
86 |
|
87 |
> What do I do when I need to update /right now/ and find myself being |
88 |
> blocked with cryptic messages like the above that leave me stranded? |
89 |
|
90 |
That's the real problem, that the messages are so cryptic. The solution |
91 |
is simple, working out what needs to be done from the messages is not. |
92 |
|
93 |
> Once I used 'emerge --sync', there is no way to turn it back to continue |
94 |
> to be able to install software if needed when the update cannot be |
95 |
> performed. Updates simply need to work, there's no way around that. |
96 |
|
97 |
You can always roll back by masking the updates if necessary, and the |
98 |
old ebuilds are always available. Now that the tree is using git, it is |
99 |
probably possibly to sync back to yesterday if you need to. |
100 |
|
101 |
|
102 |
-- |
103 |
Neil Bothwick |
104 |
|
105 |
WINDOWS: Will Install Needless Data On Whole System |