On 8/6/21 11:07 PM, antlists wrote:
On 06/08/2021 19:41, n952162 wrote:
It might not hurt if that error message included the suggestion to run
"emerge -u portage" to update it. It does say that the solution is to
update portage - it just doesn't explicitly tell you how to do so.
The way
On 06/08/2021 19:41, n952162 wrote:
It might not hurt if that error message included the suggestion to run
"emerge -u portage" to update it. It does say that the solution is to
update portage - it just doesn't explicitly tell you how to do so.
The way out of my dilema would be first to emerge
On Fri, Aug 6, 2021 at 2:41 PM n952162 wrote:
>
> On 8/6/21 8:22 PM, Rich Freeman wrote:
> > On Fri, Aug 6, 2021 at 8:37 AM n952162 wrote:
> >> I was complaining, mostly, that isodate had to be the thing that was
> >> incompatible with my configuration. Maybe there is a unavoidable reason
> >>
On 8/6/21 8:22 PM, Rich Freeman wrote:
On Fri, Aug 6, 2021 at 8:37 AM n952162 wrote:
I was complaining, mostly, that isodate had to be the thing that was
incompatible with my configuration. Maybe there is a unavoidable reason
that that package had to move to the newest EAPI, or maybe it was
On Fri, Aug 6, 2021 at 8:37 AM n952162 wrote:
>
> I was complaining, mostly, that isodate had to be the thing that was
> incompatible with my configuration. Maybe there is a unavoidable reason
> that that package had to move to the newest EAPI, or maybe it was just a
> sense that it's cool to be
On 8/6/21 5:09 PM, Peter Humphrey wrote:
On Friday, 6 August 2021 12:58:59 BST n952162 wrote:
(sorry, Peter, for the direct email, apparently a mis-click)
It's easily forgiven. For who among us has never misclicked?
:)
:-)))
On Friday, 6 August 2021 12:58:59 BST n952162 wrote:
> (sorry, Peter, for the direct email, apparently a mis-click)
It's easily forgiven. For who among us has never misclicked?
:)
--
Regards,
Peter.
On 8/6/21 2:37 PM, n952162 wrote:
On 8/6/21 2:16 PM, Rich Freeman wrote:
On Tue, Aug 3, 2021 at 2:03 AM n952162 wrote:
Well, what you say is likely true, but does "old software" really need
to be kept working? Couldn't problems necessarily only be dealt with
in the newest versions?
I
On 8/6/21 2:16 PM, Rich Freeman wrote:
On Tue, Aug 3, 2021 at 2:03 AM n952162 wrote:
Well, what you say is likely true, but does "old software" really need
to be kept working? Couldn't problems necessarily only be dealt with
in the newest versions?
I think you are misunderstanding what
On Tue, Aug 3, 2021 at 2:03 AM n952162 wrote:
>
> Well, what you say is likely true, but does "old software" really need
> to be kept working? Couldn't problems necessarily only be dealt with
> in the newest versions?
>
I think you are misunderstanding what actually went wrong in your
On 8/3/21 5:54 PM, Peter Humphrey wrote:
On Tuesday, 3 August 2021 15:51:15 BST Arve Barsnes wrote:
On Tue, 3 Aug 2021 at 15:58, Neil Bothwick wrote:
I don't see them when syncing from a cron script, when all output is
captured and emailed, but do when running sync on a shell. It seems you
On Tuesday, 3 August 2021 15:51:15 BST Arve Barsnes wrote:
> On Tue, 3 Aug 2021 at 15:58, Neil Bothwick wrote:
> > I don't see them when syncing from a cron script, when all output is
> > captured and emailed, but do when running sync on a shell. It seems you
> > only see this when running sync
On Tue, 3 Aug 2021 at 15:58, Neil Bothwick wrote:
> I don't see them when syncing from a cron script, when all output is
> captured and emailed, but do when running sync on a shell. It seems you
> only see this when running sync interactively.
I see these messages in the output from my cron
On 8/3/21 3:58 PM, Neil Bothwick wrote:
On Tue, 3 Aug 2021 15:35:41 +0200, n952162 wrote:
You should have seen a message from emerge --sync telling you that a
new version of portage was available and to run emerge -1au portage
before updating anything else.
I find no informational messages
On Tue, 3 Aug 2021 15:35:41 +0200, n952162 wrote:
> > You should have seen a message from emerge --sync telling you that a
> > new version of portage was available and to run emerge -1au portage
> > before updating anything else.
> I find no informational messages containing "portage", "emerge",
On 8/3/21 12:52 PM, Neil Bothwick wrote:
On Tue, 3 Aug 2021 07:20:47 +0200, n952162 wrote:
I read that, but I last updated 2 months ago. So, this update breaks
because portage was updated and new ebuilds using that are already being
pushed out?
You should have seen a message from emerge
On Tue, 3 Aug 2021 07:20:47 +0200, n952162 wrote:
> I read that, but I last updated 2 months ago. So, this update breaks
> because portage was updated and new ebuilds using that are already being
> pushed out?
You should have seen a message from emerge --sync telling you that a new
version of
On 8/3/21 8:29 AM, cal wrote:
On 8/2/21 11:03 PM, n952162 wrote:
On 8/3/21 7:37 AM, cal wrote:
On 8/2/21 10:26 PM, n952162 wrote:
On 8/3/21 7:20 AM, n952162 wrote:
On 8/2/21 10:10 PM, David Haller wrote:
Hello,
On Mon, 02 Aug 2021, n952162 wrote:
!!! All ebuilds that could satisfy
On 8/2/21 11:03 PM, n952162 wrote:
> On 8/3/21 7:37 AM, cal wrote:
>> On 8/2/21 10:26 PM, n952162 wrote:
>>> On 8/3/21 7:20 AM, n952162 wrote:
On 8/2/21 10:10 PM, David Haller wrote:
> Hello,
>
> On Mon, 02 Aug 2021, n952162 wrote:
>> !!! All ebuilds that could satisfy
>>
On 8/3/21 7:37 AM, cal wrote:
On 8/2/21 10:26 PM, n952162 wrote:
On 8/3/21 7:20 AM, n952162 wrote:
On 8/2/21 10:10 PM, David Haller wrote:
Hello,
On Mon, 02 Aug 2021, n952162 wrote:
!!! All ebuilds that could satisfy
On 8/2/21 10:26 PM, n952162 wrote:
> On 8/3/21 7:20 AM, n952162 wrote:
>> On 8/2/21 10:10 PM, David Haller wrote:
>>> Hello,
>>>
>>> On Mon, 02 Aug 2021, n952162 wrote:
!!! All ebuilds that could satisfy
"dev-python/isodate[python_targets_python3_8(-)?,python_targets_python3_9(-)?]"
On 8/3/21 7:20 AM, n952162 wrote:
On 8/2/21 10:10 PM, David Haller wrote:
Hello,
On Mon, 02 Aug 2021, n952162 wrote:
!!! All ebuilds that could satisfy
"dev-python/isodate[python_targets_python3_8(-)?,python_targets_python3_9(-)?]"
have been masked.
!!! One of the following masked packages is
On 8/2/21 10:10 PM, David Haller wrote:
Hello,
On Mon, 02 Aug 2021, n952162 wrote:
!!! All ebuilds that could satisfy
"dev-python/isodate[python_targets_python3_8(-)?,python_targets_python3_9(-)?]"
have been masked.
!!! One of the following masked packages is required to complete your
request:
Hello,
On Mon, 02 Aug 2021, n952162 wrote:
>!!! All ebuilds that could satisfy
>"dev-python/isodate[python_targets_python3_8(-)?,python_targets_python3_9(-)?]"
>have been masked.
>!!! One of the following masked packages is required to complete your
>request:
>-
Sorry, I have to bitch.
This kept me going for several additional gentoo hours:
!!! All ebuilds that could satisfy
"dev-python/isodate[python_targets_python3_8(-)?,python_targets_python3_9(-)?]"
have been masked.
!!! One of the following masked packages is required to complete your
request:
-
25 matches
Mail list logo
