Today when I tried to do my daily "emerge --update ... @world", portage
spitted out a lot of "Multiple package instances within a single package
slot have been pulled" messages.
I thought this could be due to the depreciation of python3_6 so I added
*/* PYTHON_TARGETS: python3_6 python3_7
*/* P
On Thu, 7 May 2020 10:04:37 +0200, Dan Johansson wrote:
> Today when I tried to do my daily "emerge --update ... @world", portage
> spitted out a lot of "Multiple package instances within a single
> package slot have been pulled" messages.
>
> I thought this could be due to the depreciation of p
On Thu May 7 10:04:37 2020, Dan Johansson wrote:
> Today when I tried to do my daily "emerge --update ... @world", portage
> spitted out a lot of "Multiple package instances within a single package
> slot have been pulled" messages.
So THIS would have been the issue you should have given us to
On 07.05.20 13:59, Franz Fellner wrote:
On Thu May 7 10:04:37 2020, Dan Johansson wrote:
Today when I tried to do my daily "emerge --update ... @world", portage
spitted out a lot of "Multiple package instances within a single package
slot have been pulled" messages.
So THIS would have been t
On 07.05.20 16:30, Dan Johansson wrote:
On 07.05.20 13:59, Franz Fellner wrote:
On Thu May 7 10:04:37 2020, Dan Johansson wrote:
Today when I tried to do my daily "emerge --update ... @world", portage
spitted out a lot of "Multiple package instances within a single package
slot have been pull
On Fri, 8 May 2020 16:20:46 +0200, Dan Johansson wrote:
> After that "initial" update was done, I removed the added entries
> (including the "PYTHON_SINGLE_TARGET: python2_7" ones) and started a
> new emerge update. With exception of one package (net-misc/s3cmd)
> everything went as it should.
s
6 matches
Mail list logo
