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