1 |
On 5/16/20 12:23 PM, n952162 wrote: |
2 |
> Oh oh oh! Are you saying ... given "..." in this: |
3 |
> |
4 |
> Synopsis: emerge [options] [action] [ebuild | tbz2file | file | @set | |
5 |
> atom] ... |
6 |
> |
7 |
> that the solution to my problems is to - for each conflict - to select |
8 |
> one of the two and put it on the same command line? |
9 |
> |
10 |
> e.g: |
11 |
> |
12 |
> sudo emerge -av =sys-apps/portage-2.3.89-r3 |
13 |
> =app-portage/gemato-14.3 =dev-python/setuptools-44.1.0 |
14 |
> dev-python/certifi-2019.11.28 |
15 |
Maybe. The issue is to first understand (for each slot conflict) what |
16 |
is pulling in each of the conflicting versions. The newer version is |
17 |
probably being pulled in as the default (highest version not flagged or |
18 |
masked or ...). The older version is likely being pulled in by an older |
19 |
version of some other package. Rather than specifying specific version, |
20 |
just include the other package also. |
21 |
|
22 |
The basic idea is to upgrade as few packages at a time as possible - but |
23 |
you can't do just one because of these conflicts. So starting with |
24 |
"emerge -1 portage" and seeing the older version of portage is being |
25 |
pulled in by gentookit, just "emerge -1 portage gentoolkit". You may |
26 |
have to go through many iterations to find a set of packages which will |
27 |
cleanly upgrade together. |
28 |
> |
29 |
> |
30 |
> On 05/16/20 18:16, Jack wrote: |
31 |
>> On 2020.05.16 11:56, n952162 wrote: |
32 |
>>> Okay, I'm blocked here, at the very beginning: |
33 |
>>> |
34 |
>>> sys-apps/portage:0 |
35 |
>>> |
36 |
>>> (sys-apps/portage-*2.3.89-r3:0*/0::gentoo, ebuild scheduled for |
37 |
>>> merge) pulled in by |
38 |
>>> =sys-apps/portage-2.3.89-r3 (Argument) |
39 |
>>> |
40 |
>>> (sys-apps/portage-*2.3.49:0/0*::gentoo, installed) pulled in by |
41 |
>>> sys-apps/portage[python_targets_python2_7(-),python_targets_python3_6(-),-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)] |
42 |
>>> |
43 |
>>> required by (app-portage/gentoolkit-0.4.2-r1:0/0::gentoo, installed) |
44 |
>>> |
45 |
>>> I'm trying to update from 2.3.49 to 2.3.89 and it tells me it has a |
46 |
>>> slot |
47 |
>>> conflict there. I can hardly delete portage and then add it ... |
48 |
>> First, if you post a slot conflict, post the whole thing. (This one |
49 |
>> is OK, but your previous one for gentoolkit only showed one of the two |
50 |
>> entries. In this case, you probably need to upgrade gentoolkit and |
51 |
>> portage at the same time. |
52 |
>> |
53 |
>>> |
54 |
>>> |
55 |
>>> On 05/16/20 17:38, n952162 wrote: |
56 |
>>>> |
57 |
>>>> e.g. |
58 |
>>>> |
59 |
>>>> sudo emerge -av =*sys-apps/portage-2.3.89-r3 |
60 |
>>>> <https://gitweb.gentoo.org/repo/gentoo.git/tree/sys-apps/portage/portage-2.3.89-r3.ebuild>* |
61 |
>>>> |
62 |
>>>> |
63 |
>>>> |
64 |
>>>> ? |
65 |
>>>> |
66 |
>>>> I got (amongst tons of other stuff): |
67 |
>>>> |
68 |
>>>> * Error: The above package list contains packages which cannot be |
69 |
>>>> * installed at the same time on the same system. |
70 |
>>>> |
71 |
>>>> (app-portage/gentoolkit-0.4.2-r1:0/0::gentoo, installed) pulled |
72 |
>>>> in by |
73 |
>>>> app-portage/gentoolkit required by @selected |
74 |
>>>> |
75 |
>>>> On 05/16/20 16:19, Jack wrote: |
76 |
>>>>> On 5/16/20 8:53 AM, n952162 wrote: |
77 |
>>>>>> I did an emerge --sync and then "emerge -v1 portage" and it blew |
78 |
>>>>>> up all |
79 |
>>>>>> over the place. Log in the attachment. |
80 |
>>>>>> |
81 |
>>>>>> How can I get things reestablished? Or, does gentoo simply |
82 |
>>>>>> require a |
83 |
>>>>>> smarter user than me, and I should go back to ubuntu? |
84 |
>>>>> |
85 |
>>>>> I think the bottom line is that Gentoo needs to be updated more often |
86 |
>>>>> than yearly. Others may also comment, but right now, I think a |
87 |
>>>>> reinstall might be easier than working through all the problems, |
88 |
>>>>> unless you are trying to learn more about how things work. |
89 |
>>>>> |
90 |
>>>>> My first question is why you have portage-9999 unmasked? I suggest |
91 |
>>>>> going for the lowest version currently in the tree. I'm not sure if |
92 |
>>>>> your first step should really be portage itself, or upgrading |
93 |
>>>>> packages where the installed version is now masked due to security |
94 |
>>>>> errors or being too out of date. |
95 |
>>>>> |
96 |
>>>>> Jack |
97 |
>>>>> |
98 |
>>>>>> |
99 |
>>>>>> |
100 |
>>>>>> On 05/14/20 23:36, Rich Freeman wrote: |
101 |
>>>>>>> On Thu, May 14, 2020 at 5:10 PM n952162 <n952162@×××.de> wrote: |
102 |
>>>>>>>> On 05/14/20 22:46, Rich Freeman wrote: |
103 |
>>>>>>>>> On Thu, May 14, 2020 at 4:13 PM n952162 <n952162@×××.de> wrote: |
104 |
>>>>>>>>>> Action: sync for repo: gentoo, returned code = 0 |
105 |
>>>>>>>>>> |
106 |
>>>>>>>>>> * An update to portage is available. It is _highly_ |
107 |
>>>>>>>>>> recommended |
108 |
>>>>>>>>>> * that you update portage now, before any other packages are |
109 |
>>>>>>>>>> updated. |
110 |
>>>>>>>>>> |
111 |
>>>>>>>>>> * To update portage, run 'emerge --oneshot portage' now. |
112 |
>>>>>>>>> ...and? Did you update portage as it was _highly_ recommended |
113 |
>>>>>>>>> that |
114 |
>>>>>>>>> you do so first? What version of portage are you using? This |
115 |
>>>>>>>>> appears |
116 |
>>>>>>>>> on the top line of emerge --info. |
117 |
>>>>>>>>> |
118 |
>>>>>>>> $ emerge --info |
119 |
>>>>>>>> Portage 2.3.49 (python 3.6.5-final-0, default/linux/x86/17.0, |
120 |
>>>>>>>> gcc-7.3.0, |
121 |
>>>>>>>> glibc-2.26-r7, 4.14.65-gentoo x86_64) |
122 |
>>>>>>> That version of portage has been removed from the repo for over a |
123 |
>>>>>>> year. |
124 |
>>>>>>> |
125 |
>>>>>>> I would update your system so that is current and then try |
126 |
>>>>>>> again. I |
127 |
>>>>>>> believe that version of portage should still support EAPI 7 but |
128 |
>>>>>>> there |
129 |
>>>>>>> could be some other issue that is giving it problems with more |
130 |
>>>>>>> recent |
131 |
>>>>>>> packages in the tree. |
132 |
>>>>>>> |
133 |
>>>>>> |
134 |
>>>>> |
135 |
>>>> |
136 |
>>> |
137 |
>> |
138 |
> |
139 |
> |