1 |
Rich Freeman <rich0@g.o> writes: |
2 |
|
3 |
> On Sun, Sep 20, 2015 at 1:24 PM, J. Roeleveld <joost@××××××××.org> wrote: |
4 |
>> On Sunday 20 September 2015 16:25:34 lee wrote: |
5 |
>>> So I decided I'd better ask what to do. It's hard to believe that we |
6 |
>>> are seriously expected to remove lots of software which we might not be |
7 |
>>> able to install again just to do an update. All these conflicts give me |
8 |
>>> the impression that something in the repo is broken and needs to be |
9 |
>>> fixed. |
10 |
>> |
11 |
>> I have no such issues, neither do most people. |
12 |
>> Which seems to indicate the issue is not with the repo. |
13 |
>> Lets look at the actual contents of your world-file. (see above) |
14 |
>> |
15 |
> |
16 |
> So, first, I don't think it is a good idea to just start uninstalling |
17 |
> packages first and then try to fix them. That might or might not |
18 |
> work, but it certainly isn't the first thing I'd try. |
19 |
|
20 |
+1 |
21 |
|
22 |
> Second, this could very well be a problem with the repo, which is the |
23 |
> whole point of the debate around dynamic dependencies. Current |
24 |
> practices tend to create situations that our package managers can't |
25 |
> handle. They don't break for everybody instantly, which is why |
26 |
> they're so insidious, and also why changing the practice was somewhat |
27 |
> controversial when it first came up a year ago. |
28 |
|
29 |
Which means? I mean, I don't exactly have a lot of stuff installed and |
30 |
nonetheless "slot conflicts". Perhaps they don't matter and thereby |
31 |
don't classify as something that the package management couldn't handle. |
32 |
|
33 |
Now if there is something that the package management cannot handle, |
34 |
what messages would I get? |
35 |
|
36 |
> I hate to post it a 3rd time, but before we bicker 14 more times on |
37 |
> this, could somebody please just try adding --backtrack=50, and if |
38 |
|
39 |
Ok --- I haven't changed anything yet other than running emerge --sync |
40 |
again today: |
41 |
|
42 |
|
43 |
,---- |
44 |
| heimdali ~ # emerge -j 8 -a --update --newuse --deep --with-bdeps=y --backtrack=500 @world |
45 |
| |
46 |
| * IMPORTANT: 4 news items need reading for repository 'gentoo'. |
47 |
| * Use eselect news read to view new items. |
48 |
| |
49 |
| |
50 |
| These are the packages that would be merged, in order: |
51 |
| |
52 |
| Calculating dependencies... done! |
53 |
| |
54 |
| !!! Multiple package instances within a single package slot have been pulled |
55 |
| !!! into the dependency graph, resulting in a slot conflict: |
56 |
| |
57 |
| dev-libs/boost:0 |
58 |
| |
59 |
| (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for merge) pulled in by |
60 |
| (no parents that aren't satisfied by other packages in this slot) |
61 |
| |
62 |
| (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for merge) pulled in by |
63 |
| dev-libs/boost:0/1.55.0= required by (dev-libs/librevenge-0.0.2:0/0::gentoo, installed) |
64 |
| ^^^^^^^^^^ |
65 |
| (and 2 more with the same problem) |
66 |
| |
67 |
| dev-util/boost-build:0 |
68 |
| |
69 |
| (dev-util/boost-build-1.55.0:0/0::gentoo, installed) pulled in by |
70 |
| =dev-util/boost-build-1.55* required by (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for merge) |
71 |
| ^ ^^^^^ |
72 |
| |
73 |
| (dev-util/boost-build-1.56.0:0/0::gentoo, ebuild scheduled for merge) pulled in by |
74 |
| =dev-util/boost-build-1.56* required by (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for merge) |
75 |
| ^ ^^^^^ |
76 |
| |
77 |
| x11-drivers/nvidia-drivers:0 |
78 |
| |
79 |
| (x11-drivers/nvidia-drivers-355.11:0/0::gentoo, ebuild scheduled for merge) pulled in by |
80 |
| (no parents that aren't satisfied by other packages in this slot) |
81 |
| |
82 |
| (x11-drivers/nvidia-drivers-340.93:0/0::gentoo, ebuild scheduled for merge) pulled in by |
83 |
| ~x11-drivers/nvidia-drivers-340.93 required by (media-video/nvidia-settings-340.58:0/0::gentoo, ebuild scheduled for merge) |
84 |
| ^ ^^^^^^ |
85 |
| |
86 |
| media-video/ffmpeg:0 |
87 |
| |
88 |
| (media-video/ffmpeg-2.6.3:0/54.56.56::gentoo, ebuild scheduled for merge) pulled in by |
89 |
| (no parents that aren't satisfied by other packages in this slot) |
90 |
| |
91 |
| (media-video/ffmpeg-2.2.14:0/52.55.55::gentoo, installed) pulled in by |
92 |
| media-video/ffmpeg:0/52.55.55=[vdpau] required by (media-libs/mlt-0.9.0:0/0::gentoo, installed) |
93 |
| ^^^^^^^^^^^^ |
94 |
| |
95 |
| |
96 |
| It may be possible to solve this problem by using package.mask to |
97 |
| prevent one of those packages from being selected. However, it is also |
98 |
| possible that conflicting dependencies exist such that they are |
99 |
| impossible to satisfy simultaneously. If such a conflict exists in |
100 |
| the dependencies of two different packages, then those packages can |
101 |
| not be installed simultaneously. |
102 |
| |
103 |
| For more information, see MASKED PACKAGES section in the emerge man |
104 |
| page or refer to the Gentoo Handbook. |
105 |
| |
106 |
| |
107 |
| !!! The ebuild selected to satisfy "sci-libs/hdf5" has unmet requirements. |
108 |
| - sci-libs/hdf5-1.8.14-r1::gentoo USE="cxx fortran threads zlib -debug -examples -fortran2003 -mpi -static-libs -szip" |
109 |
| |
110 |
| The following REQUIRED_USE flag constraints are unsatisfied: |
111 |
| threads? ( !cxx !fortran ) |
112 |
| |
113 |
| The above constraints are a subset of the following complete expression: |
114 |
| cxx? ( !mpi ) mpi? ( !cxx ) threads? ( !cxx !mpi !fortran ) fortran2003? ( fortran ) |
115 |
| |
116 |
| (dependency required by "media-libs/openimageio-1.3.5::gentoo" [installed]) |
117 |
| (dependency required by "@selected" [set]) |
118 |
| (dependency required by "@world" [argument]) |
119 |
| heimdali ~ # |
120 |
`---- |
121 |
|
122 |
|
123 |
I tried without --backtrace, and it gives me the same output. |
124 |
|
125 |
|
126 |
> that doesn't work just try running emerge -1 on the packages that are |
127 |
> causing the block by depending on the older package version? |
128 |
|
129 |
I suppose the newer versions of the packages are the ones that are |
130 |
causing the blocks. You could argue that other versions of packages are |
131 |
causing the blocks, but I would argue that there weren't any blocks |
132 |
before the newer versions of the packages were available, hence the |
133 |
newer versions obviously cause the blocks. That is to say that I'm |
134 |
unsure which packages you're referring to as those causing the blocks. |
135 |
|
136 |
Anyway: |
137 |
|
138 |
|
139 |
,---- |
140 |
| heimdali ~ # emerge -a -1 boost |
141 |
| |
142 |
| * IMPORTANT: 4 news items need reading for repository 'gentoo'. |
143 |
| * Use eselect news read to view new items. |
144 |
| |
145 |
| |
146 |
| These are the packages that would be merged, in order: |
147 |
| |
148 |
| Calculating dependencies... done! |
149 |
| [ebuild U ] sys-devel/automake-wrapper-10 [9] |
150 |
| [ebuild U ] dev-util/boost-build-1.56.0 [1.55.0] PYTHON_TARGETS="python2_7%*" |
151 |
| [ebuild r U ] dev-libs/boost-1.56.0-r1 [1.55.0-r2] PYTHON_TARGETS="python3_4* -python3_3*" |
152 |
| [ebuild rR ] dev-libs/librevenge-0.0.2 |
153 |
| [ebuild U ] dev-util/mdds-0.12.1 [0.10.3] |
154 |
| [ebuild rR ] app-text/libwps-0.3.1 |
155 |
| [ebuild NS ] sys-devel/automake-1.15 [1.11.6-r1, 1.13.4] |
156 |
| [ebuild r U ] dev-libs/icu-55.1 [54.1-r1] |
157 |
| [ebuild r U ] app-text/libetonyek-0.1.3 [0.1.1] |
158 |
| [ebuild rR ] app-text/libebook-0.1.2 |
159 |
| [ebuild rR ] media-libs/libcdr-0.1.1 |
160 |
| [ebuild rR ] app-text/libmspub-0.1.2 |
161 |
| [ebuild rR ] media-libs/libvisio-0.1.1 |
162 |
| [ebuild rR ] gnustep-base/gnustep-base-1.24.6-r1 |
163 |
| [ebuild rR ] media-libs/raptor-2.0.9 |
164 |
| [ebuild r U ] dev-cpp/libcmis-0.5.0-r1 [0.5.0] |
165 |
| [ebuild r U ] dev-libs/libixion-0.9.0 [0.7.0] PYTHON_TARGETS="python2_7%*" |
166 |
| [ebuild r U ] dev-libs/liborcus-0.7.1 [0.7.0] |
167 |
| [ebuild r U ] media-libs/harfbuzz-0.9.41 [0.9.38] USE="-fontconfig%" |
168 |
| [ebuild r U ] net-libs/webkit-gtk-2.4.9-r200 [2.4.8-r200] |
169 |
| [ebuild r U ] app-office/libreoffice-4.4.5.2 [4.4.1.2] PYTHON_TARGETS="python3_4* -python3_3*" |
170 |
| |
171 |
| The following packages are causing rebuilds: |
172 |
| |
173 |
| (dev-libs/libixion-0.9.0:0/0.10::gentoo, ebuild scheduled for merge) causes rebuilds for: |
174 |
| (dev-libs/liborcus-0.7.1:0/0::gentoo, ebuild scheduled for merge) |
175 |
| (dev-libs/icu-55.1:0/55::gentoo, ebuild scheduled for merge) causes rebuilds for: |
176 |
| (media-libs/harfbuzz-0.9.41:0/0.9.18::gentoo, ebuild scheduled for merge) |
177 |
| (media-libs/libcdr-0.1.1:0/0::gentoo, ebuild scheduled for merge) |
178 |
| (app-text/libebook-0.1.2:0/0::gentoo, ebuild scheduled for merge) |
179 |
| (media-libs/libvisio-0.1.1:0/0::gentoo, ebuild scheduled for merge) |
180 |
| (gnustep-base/gnustep-base-1.24.6-r1:0/0::gentoo, ebuild scheduled for merge) |
181 |
| (app-office/libreoffice-4.4.5.2:0/0::gentoo, ebuild scheduled for merge) |
182 |
| (media-libs/raptor-2.0.9:2/2::gentoo, ebuild scheduled for merge) |
183 |
| (net-libs/webkit-gtk-2.4.9-r200:2/2::gentoo, ebuild scheduled for merge) |
184 |
| (app-text/libmspub-0.1.2:0/0::gentoo, ebuild scheduled for merge) |
185 |
| (dev-util/mdds-0.12.1:0/0.12.1::gentoo, ebuild scheduled for merge) causes rebuilds for: |
186 |
| (dev-libs/libixion-0.9.0:0/0.10::gentoo, ebuild scheduled for merge) |
187 |
| (app-office/libreoffice-4.4.5.2:0/0::gentoo, ebuild scheduled for merge) |
188 |
| (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for merge) causes rebuilds for: |
189 |
| (dev-cpp/libcmis-0.5.0-r1:0.5/0.5::gentoo, ebuild scheduled for merge) |
190 |
| (dev-libs/liborcus-0.7.1:0/0::gentoo, ebuild scheduled for merge) |
191 |
| (app-text/libetonyek-0.1.3:0/0::gentoo, ebuild scheduled for merge) |
192 |
| (app-text/libebook-0.1.2:0/0::gentoo, ebuild scheduled for merge) |
193 |
| (app-office/libreoffice-4.4.5.2:0/0::gentoo, ebuild scheduled for merge) |
194 |
| (dev-libs/librevenge-0.0.2:0/0::gentoo, ebuild scheduled for merge) |
195 |
| (app-text/libwps-0.3.1:0/0::gentoo, ebuild scheduled for merge) |
196 |
| (dev-libs/libixion-0.9.0:0/0.10::gentoo, ebuild scheduled for merge) |
197 |
| |
198 |
| !!! The following installed packages are masked: |
199 |
| - net-firewall/shorewall-4.6.6.2::gentoo (masked by: package.mask) |
200 |
| /usr/portage/profiles/package.mask: |
201 |
| # Ian Delaney <idella4@g.o> (21 Jul 2015) |
202 |
| # Packages deprecated in favour of new form of |
203 |
| # net-firewall/shorewall |
204 |
| # Bug #560392 |
205 |
| |
206 |
| For more information, see the MASKED PACKAGES section in the emerge |
207 |
| man page or refer to the Gentoo Handbook. |
208 |
| |
209 |
| |
210 |
| Would you like to merge these packages? [Yes/No] |
211 |
`---- |
212 |
|
213 |
|
214 |
What should I learn from this? That we |
215 |
|
216 |
|
217 |
+ need to update kinda recursively (because the package management can't |
218 |
do that for us because it's so complicated that only users with many |
219 |
years of experience with Gentoo can figure out how to upgrade |
220 |
eventually, sometimes requiring the combined effort of a mailing |
221 |
list), |
222 |
|
223 |
+ need to rebuild (large) packages (like libreoffice) which I expect to |
224 |
be upgraded and thus get rebuilt later anyway (to keep the package |
225 |
management happy because it cannot figure this out for us and give us |
226 |
a choice to upgrade these (large) packages as well while we are at |
227 |
it), |
228 |
|
229 |
+ have to do other things to keep the system up to date we somehow don't |
230 |
know about, like 'emerge -a --changed-deps=y @world' (because the |
231 |
package management doesn't really know how to update the whole system |
232 |
to begin with (because it's so complicated))? |
233 |
|
234 |
|
235 |
You see me confused. And now I don't really feel like updating |
236 |
anymore. But I still want to [pouts]. |
237 |
|
238 |
|
239 |
-- |
240 |
Again we must be afraid of speaking of daemons for fear that daemons |
241 |
might swallow us. Finally, this fear has become reasonable. |