| 1 |
e.g. |
| 2 |
|
| 3 |
sudo emerge -av =*sys-apps/portage-2.3.89-r3 |
| 4 |
<https://gitweb.gentoo.org/repo/gentoo.git/tree/sys-apps/portage/portage-2.3.89-r3.ebuild>* |
| 5 |
|
| 6 |
? |
| 7 |
|
| 8 |
I got (amongst tons of other stuff): |
| 9 |
|
| 10 |
* Error: The above package list contains packages which cannot be |
| 11 |
* installed at the same time on the same system. |
| 12 |
|
| 13 |
(app-portage/gentoolkit-0.4.2-r1:0/0::gentoo, installed) pulled in by |
| 14 |
app-portage/gentoolkit required by @selected |
| 15 |
|
| 16 |
On 05/16/20 16:19, Jack wrote: |
| 17 |
> On 5/16/20 8:53 AM, n952162 wrote: |
| 18 |
>> I did an emerge --sync and then "emerge -v1 portage" and it blew up all |
| 19 |
>> over the place. Log in the attachment. |
| 20 |
>> |
| 21 |
>> How can I get things reestablished? Or, does gentoo simply require a |
| 22 |
>> smarter user than me, and I should go back to ubuntu? |
| 23 |
> |
| 24 |
> I think the bottom line is that Gentoo needs to be updated more often |
| 25 |
> than yearly. Others may also comment, but right now, I think a |
| 26 |
> reinstall might be easier than working through all the problems, |
| 27 |
> unless you are trying to learn more about how things work. |
| 28 |
> |
| 29 |
> My first question is why you have portage-9999 unmasked? I suggest |
| 30 |
> going for the lowest version currently in the tree. I'm not sure if |
| 31 |
> your first step should really be portage itself, or upgrading packages |
| 32 |
> where the installed version is now masked due to security errors or |
| 33 |
> being too out of date. |
| 34 |
> |
| 35 |
> Jack |
| 36 |
> |
| 37 |
>> |
| 38 |
>> |
| 39 |
>> On 05/14/20 23:36, Rich Freeman wrote: |
| 40 |
>>> On Thu, May 14, 2020 at 5:10 PM n952162 <n952162@×××.de> wrote: |
| 41 |
>>>> On 05/14/20 22:46, Rich Freeman wrote: |
| 42 |
>>>>> On Thu, May 14, 2020 at 4:13 PM n952162 <n952162@×××.de> wrote: |
| 43 |
>>>>>> Action: sync for repo: gentoo, returned code = 0 |
| 44 |
>>>>>> |
| 45 |
>>>>>> * An update to portage is available. It is _highly_ recommended |
| 46 |
>>>>>> * that you update portage now, before any other packages are |
| 47 |
>>>>>> updated. |
| 48 |
>>>>>> |
| 49 |
>>>>>> * To update portage, run 'emerge --oneshot portage' now. |
| 50 |
>>>>> ...and? Did you update portage as it was _highly_ recommended that |
| 51 |
>>>>> you do so first? What version of portage are you using? This appears |
| 52 |
>>>>> on the top line of emerge --info. |
| 53 |
>>>>> |
| 54 |
>>>> $ emerge --info |
| 55 |
>>>> Portage 2.3.49 (python 3.6.5-final-0, default/linux/x86/17.0, |
| 56 |
>>>> gcc-7.3.0, |
| 57 |
>>>> glibc-2.26-r7, 4.14.65-gentoo x86_64) |
| 58 |
>>> That version of portage has been removed from the repo for over a year. |
| 59 |
>>> |
| 60 |
>>> I would update your system so that is current and then try again. I |
| 61 |
>>> believe that version of portage should still support EAPI 7 but there |
| 62 |
>>> could be some other issue that is giving it problems with more recent |
| 63 |
>>> packages in the tree. |
| 64 |
>>> |
| 65 |
>> |
| 66 |
> |
Archives