1 |
On 05/20/20 22:08, Rich Freeman wrote: |
2 |
> On Wed, May 20, 2020 at 3:49 PM n952162 <n952162@×××.de> wrote: |
3 |
>> On 05/20/20 21:24, Daniel Frey wrote: |
4 |
>>> On 5/20/20 12:06 PM, n952162 wrote: |
5 |
>>>> The command was: |
6 |
>>>> |
7 |
>>>> emerge -vu dev-qt/qtgui dev-qt/qtx11extras dev-qt/qtopengl |
8 |
>>>> dev-qt/qtprintsupport dev-qt/qtwidgets dev-qt/qtxml |
9 |
>>>> dev-qt/linguist-tools dev-qt/qtnetwork dev-qt/qtsvg dev-qt/qtcore |
10 |
>>>> |
11 |
>>>> The output to that is attached. |
12 |
>>>> |
13 |
>>>> I tried just emerging zlib with the static-libs USE flag ... that log is |
14 |
>>>> also attached. |
15 |
>>>> |
16 |
>>>> On 05/20/20 18:59, Ashley Dixon wrote: |
17 |
>>>>> On Wed, May 20, 2020 at 02:35:52PM +0200, n952162 wrote: |
18 |
>>>>>> I have a slot conflict for sys-libs/zlib, whereby both users want |
19 |
>>>>>> the same package. Studying the USE variables shows that the new |
20 |
>>>>>> package wants, additionally, the "static-libs" USE flag. |
21 |
>>>>>> |
22 |
>>>>>> I thought, the way to handle this is to add the static-libs USE |
23 |
>>>>>> variable in /etc/portage/package.use and re-emerge with |
24 |
>>>>>> --changed-use. Unfortunately, that gives me the same conflict. |
25 |
>>>>> Can you attach the full output of emerge ? |
26 |
>>>>> |
27 |
>>> This is most likely due to so many packages that need to be upgraded |
28 |
>>> at the same time. You're only asking to update a few select packages |
29 |
>>> and it's borking because it's finding packages outside your request |
30 |
>>> that also need to be updated at the same time. |
31 |
>>> |
32 |
>> Because of a static-libs USE flag? |
33 |
>> Is it the case that - if a package is installed with a USE flag, every |
34 |
>> user of that package that doesn't specify that USE flag gets kicked out? |
35 |
> No. The problem is that you asked the system to update a few packages. |
36 |
> |
37 |
> Those packages require an updated version of openssl to work. |
38 |
> However, you have a bunch of other packages (like |
39 |
> openssh/wget/ruby/curl/etc) that use the old version of openssl. |
40 |
|
41 |
|
42 |
Well, you're talking about openssl here. I'm trying to go a step at a |
43 |
time and looking at the first conflict in that first log file: zlib. |
44 |
Why will |
45 |
|
46 |
sys-libs/zlib:0 |
47 |
|
48 |
(*sys-libs/zlib-1.2.11-r2:0/1::gentoo*, installed) pulled in by |
49 |
>=sys-libs/zlib-1.2.8-r1[_abi_x86_64(-)_] required by |
50 |
(dev-libs/glib-2.52.3:2/2::gentoo, installed) |
51 |
... |
52 |
|
53 |
(*sys-libs/zlib-1.2.11-r2:0/1::gentoo*, ebuild scheduled for merge) |
54 |
pulled in by |
55 |
|
56 |
>=sys-libs/zlib-1.2.8-r1[*static-libs(+)*?,abi_x86_32(-)?,_abi_x86_64(-)?_,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_riscv_lp64d(-)?,abi_riscv_lp64(-)?,abi_s390_32(-)?,abi_s390_64(-)?] required by (dev-libs/openssl-1.1.1g:0/1.1::gentoo, ebuild scheduled for merge) |
57 |
|
58 |
|
59 |
Why would these packages need an updated version of zlib if the only |
60 |
thing different to what they currently have is that the new version has |
61 |
the libraries linked in to it - one less load-time dependency: |
62 |
|
63 |
dev-libs/glib-2.52.3:2/2::gentoo |
64 |
media-libs/mesa-18.1.9:0/0::gentoo |
65 |
dev-libs/boost-1.65.0:0/1.65.0::gentoo |
66 |
media-libs/tiff-4.0.9-r4:0/0::gentoo |
67 |
net-misc/curl-7.61.1:0/0::gentoo |
68 |
app-arch/libarchive-3.3.1:0/13::gentoo |
69 |
dev-libs/nss-3.37.3:0/0::gentoo |
70 |
media-video/ffmpeg-3.3.6:0/55.57.57::gentoo |
71 |
media-libs/libpng-1.6.34:0/16::gentoo |
72 |
net-libs/libssh2-1.8.0-r1:0/0::gentoo |
73 |
dev-libs/libxml2-2.9.8:2/2::gentoo |
74 |
net-libs/gnutls-3.5.19:0/30::gentoo |
75 |
sys-libs/binutils-libs-2.30-r4:0/2.30-r1::gentoo |
76 |
dev-db/sqlite-3.24.0:3/3::gentoo |
77 |
x11-libs/cairo-1.14.12:0/0::gentoo |
78 |
dev-libs/openssl-1.0.2p:0/0::gentoo |
79 |
sys-apps/pciutils-3.5.6:0/0::gentoo |
80 |
sys-apps/file-5.33-r4:0/0::gentoo |
81 |
x11-libs/libpciaccess-0.14:0/0::gentoo |
82 |
dev-libs/elfutils-0.170-r1:0/0::gentoo |
83 |
sys-libs/cracklib-2.9.6-r1:0/0::gentoo |
84 |
media-libs/freetype-2.9.1-r3:2/2::gentoo |
85 |
|
86 |
|
87 |
|
88 |
> |
89 |
> So portage is going to try to rebuild those packages for you. |
90 |
> However, it can't do that, because the versions you have installed are |
91 |
> so old that their ebuilds are no longer in the repository, so portage |
92 |
> doesn't know how to rebuild them. |
93 |
|
94 |
|
95 |
Isn't the source and build instructions to everything on my system here, |
96 |
too? |
97 |
I mean, if it had to rebuild all the users of zlib, but wasn't being |
98 |
requested to update them. |
99 |
|
100 |
|
101 |
> |
102 |
> Portage can't upgrade them either, because you told portage to only |
103 |
> update that small list of packages and their dependencies, and those |
104 |
> other packages aren't dependencies of the packages you listed. |
105 |
> |
106 |
> You can either try to get the update for all of @world to work at the |
107 |
> same time. Or you can try to add more packages to the list. |
108 |
|
109 |
Tried that. The sorry results are attached ... |
110 |
|
111 |
> |
112 |
> And make sure you use -1 or --oneshot on the command line. |
113 |
|
114 |
Yes, I've finally grasped that, thank you, all. |
115 |
|
116 |
> |
117 |
> If you added all the packages from that list (without version numbers) |
118 |
> to that command line that might help. That is the list starting with |
119 |
> wget and ending with virtualbox (and 4 more) - you'll need to either |
120 |
> add --verbose-conflicts to get the 4 more, or see what else pops up |
121 |
> after you add these packages to the list. |
122 |
|
123 |
|
124 |
Okay, that's a good tip - when I get to openssl. But I think I should |
125 |
be able to solve zlib, first.... |
126 |
|
127 |
|
128 |
> |
129 |
> Something that might also help is running: |
130 |
> emerge -auDv --changed-use --keep-going --with-bdeps=y --changed-deps |
131 |
> --backtrack=100 @system |
132 |
|
133 |
Attached ... |
134 |
|
135 |
> That is going to be another big update, but much smaller than @world, |
136 |
> so maybe you'll get fewer errors to have to resolve that way. I'm not |
137 |
> sure if that will be better or worse than dealing with all of @world. |
138 |
> |
139 |
> It will probably take you a while to manually resolve all the |
140 |
> conflicts this way - this is a pretty normal occurrence if you update |
141 |
> Gentoo only once a year/etc. Obviously I have a half decent idea of |
142 |
> the sorts of issues you're running into and sorting through this mess |
143 |
> would probably take me days unless I just did nothing else. This is |
144 |
> not a situation you want to be in normally. |
145 |
> |
146 |
> You could also try doing a progressive update by pulling git snapshots |
147 |
> of the repository a month or two apart since the time of your last |
148 |
> update. Then you won't have so many changes to do at each time. |
149 |
> However, you might run into issues if source files aren't available, |
150 |
> since you're now trying to install packages that will no longer be |
151 |
> mirrored. |
152 |
> |
153 |
|
154 |
Actually, I installed this system just a month or two ago, but I used a |
155 |
CD I burned of the minimal-install-disk that is perhaps a year old. I |
156 |
wanted to have all my systems have the same basis, until I proficient |
157 |
enough to do a stage-1 installation ... I guess this is the way I'm |
158 |
learning how to get there :-( |