On 12/30/20 9:35 AM, Arve Barsnes wrote:
On Wed, 30 Dec 2020 at 08:46, n952162 wrote:
Well, yes, the current version, indeed requires python3_8. The version
that was installed on my system, however, to be updated, listed
python3_7 in the PYTHON_TARGETS section. That was the only difference
On Wednesday, 30 December 2020 07:22:34 GMT n952162 wrote:
> On 12/30/20 1:05 AM, Michael wrote:
> > On Tuesday, 29 December 2020 22:55:03 GMT Neil Bothwick wrote:
> >> On Tue, 29 Dec 2020 23:16:11 +0100, n952162 wrote:
> So, I tried to do an emerge on @system. I got another slot conflict!
>
On Wed, 30 Dec 2020 at 08:46, n952162 wrote:
> Well, yes, the current version, indeed requires python3_8. The version
> that was installed on my system, however, to be updated, listed
> python3_7 in the PYTHON_TARGETS section. That was the only difference
> between the two packages in the
On 12/30/20 1:05 AM, Michael wrote:
On Tuesday, 29 December 2020 22:55:03 GMT Neil Bothwick wrote:
On Tue, 29 Dec 2020 23:16:11 +0100, n952162 wrote:
So, I tried to do an emerge on @system. I got another slot conflict!
This time for mako, which I'd seen go by sometimes as a "package of
On 12/30/20 1:05 AM, Michael wrote:
On Tuesday, 29 December 2020 22:55:03 GMT Neil Bothwick wrote:
On Tue, 29 Dec 2020 23:16:11 +0100, n952162 wrote:
So, I tried to do an emerge on @system. I got another slot conflict!
This time for mako, which I'd seen go by sometimes as a "package of
On 12/30/20 1:21 AM, Dale wrote:
Michael wrote:
I expect in a few weeks the tree will settle on python3_9, so all this rinse
and repeat exercise with all the python updates should hopefully go quiet. :-)
It may not be a bad idea for the OP to sync again and see if that
helps. It's rare but
Michael wrote:
>
> I expect in a few weeks the tree will settle on python3_9, so all this rinse
> and repeat exercise with all the python updates should hopefully go quiet. :-)
It may not be a bad idea for the OP to sync again and see if that
helps. It's rare but in the past I've caught the
On Tuesday, 29 December 2020 22:55:03 GMT Neil Bothwick wrote:
> On Tue, 29 Dec 2020 23:16:11 +0100, n952162 wrote:
> > > So, I tried to do an emerge on @system. I got another slot conflict!
> > > This time for mako, which I'd seen go by sometimes as a "package of
> > > interest". It's only
On Tue, 29 Dec 2020 23:16:11 +0100, n952162 wrote:
> > So, I tried to do an emerge on @system. I got another slot conflict!
> > This time for mako, which I'd seen go by sometimes as a "package of
> > interest". It's only transgression: PYTHON_TARGET containing
> > python3_7.
> Note that both
n952162 wrote:
> On 12/29/20 11:07 PM, n952162 wrote:
>>
>>
>> So, I tried to do an emerge on @system. I got another slot conflict!
>> This time for mako, which I'd seen go by sometimes as a "package of
>> interest". It's only transgression: PYTHON_TARGET containing python3_7.
>>
>>
>
> Note
On 12/29/20 11:07 PM, n952162 wrote:
So, I tried to do an emerge on @system. I got another slot conflict!
This time for mako, which I'd seen go by sometimes as a "package of
interest". It's only transgression: PYTHON_TARGET containing python3_7.
Note that both the "scheduled for merge"
On 12/3/20 9:33 PM, n952162 wrote:
I'm trying to update the gentoo system that I last updated 6 weeks ago,
but it seems not to work. Can somebody explain to me why?
I tried and tried to figure out how I could determine what the fatal
slot conflict would be. No matter how I mixed things,
12 matches
Mail list logo
