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
> >> t
Would anybody care to recommend a tool for browsing around (and
editing) a tree of somebody-else's C code?
I prefer emacs for day-to-day editing of my code (when I know what's
where), but I'm looking for something to browse around a tree of
unfamiliar source code and make minor changes. I briefly
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 think
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 actu
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
situation
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
onl
Neil,
On Friday, 2021-08-06 08:33:33 +0100, you wrote:
> ...
> ># emerge --depclean --pretend | $PAGER
> ># emerge --depclean -- ask --quiet
>
> How about emerge -ca | tee >depclean.txt
>
> Then if the list is short you can read it in the console and just hit y
> or n. Otherwise, hit n
On Thu, 5 Aug 2021 10:10:27 +0200, Dr Rainer Woitok wrote:
> > Why not write the output to a file ? -- eg
> > 'emerge --ask --depclean > '.
> > Then you can look at the output at leisure, even on another machine.
>
> Depending on the number of packages you've installed and depending on
> th
On 6/8/21 4:40 am, Frank Steinmetzger wrote:
> Am Tue, Aug 03, 2021 at 10:18:06AM +0200 schrieb Frank Steinmetzger:
>
>>> You could delete and rebuild the cache each time (or I think there is a
>>> way to do without it).
>> If the cache can be easily rebuilt, then there’d be no need to store it a
14 matches
Mail list logo
