Re: [gentoo-user] no ebuilds for telegram

[n952162]

Okay, I'm blocked here, at the very beginning:

    sys-apps/portage:0

       (sys-apps/portage-*2.3.89-r3:0*/0::gentoo, ebuild scheduled for
    merge) pulled in by
         =sys-apps/portage-2.3.89-r3 (Argument)

       (sys-apps/portage-*2.3.49:0/0*::gentoo, installed) pulled in by
    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(-)]
    required by (app-portage/gentoolkit-0.4.2-r1:0/0::gentoo, installed)

I'm trying to update from 2.3.49 to 2.3.89 and it tells me it has a slot
conflict there.  I can hardly delete portage and then add it ...


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