On Mon, 10 Jan 2022 at 08:50, Dale wrote:
>
> Howdy,
>
> I've been dealing with this for a while. When I do my updates, it
> either omits seamonkey because the rust version installed is to new or
> downgrades rust. I keyworded rust to see if emerge could sort it out
> itself but Seamonkey then c
Am 10.01.22 um 07:44 schrieb Lee K:
On Mon, Jan 10, 2022 at 01:59:13AM +0100, Morgan Wesström wrote:
On a freshly updated system (emerge -uDN @world):
"emerge @changed-deps" wants to reinstall 0 packages.
"emerge -u --changed-deps=y" wants to reinstall 24 packages.
"emerge -uD --changed-dep
Am 10.01.22 um 01:59 schrieb Morgan Wesström:
On a freshly updated system (emerge -uDN @world):
"emerge @changed-deps" wants to reinstall 0 packages.
"emerge -u --changed-deps=y" wants to reinstall 24 packages.
"emerge -uD --changed-deps=y" wants to reinstall 181 packages.
A couple of years
Arve Barsnes wrote:
> On Mon, 10 Jan 2022 at 08:50, Dale wrote:
>> Howdy,
>>
>> I've been dealing with this for a while. When I do my updates, it
>> either omits seamonkey because the rust version installed is to new or
>> downgrades rust. I keyworded rust to see if emerge could sort it out
>> i
On 2022-01-10 07:44, Lee K wrote:
On Mon, Jan 10, 2022 at 01:59:13AM +0100, Morgan Wesström wrote:
Can someone please elaborate on what's going on here, what the difference is
between --changed-deps=y and @changed-deps, if that difference is intended and
what the recommended update procedure is
On Mon, 10 Jan 2022 at 11:33, Dale wrote:
> I read in a bug report that this is fixed in a overlay. Makes me wonder
> why this has been going on for a month or so without a 'in tree' fix.
> I'd rather not add a overlay but if it is the only fix, may have too.
An alternative to adding the whole o
On Mon, 10 Jan 2022 at 12:28, Arve Barsnes wrote:
>
> On Mon, 10 Jan 2022 at 11:33, Dale wrote:
> > I read in a bug report that this is fixed in a overlay. Makes me wonder
> > why this has been going on for a month or so without a 'in tree' fix.
> > I'd rather not add a overlay but if it is the
On 09/01/2022 23:29, gevisz wrote:
Unfortunately, you missed my previous message in this thread
where I wrote that I do have Ubuntu 20.04 on the same computer.
However, tensorflow fails to run on it because it is not compiled
to be inconsistent with my videocard. So, Gentoo is my only option
for
>
> Thank you for your reply, Mark.
>
> Unfortunately, you missed my previous message in this thread
> where I wrote that I do have Ubuntu 20.04 on the same computer.
> However, tensorflow fails to run on it because it is not compiled
> to be inconsistent with my videocard. So, Gentoo is my only o
On 2022-01-09 05:13, gevisz wrote:
Yes, masking some new package can work in this case.
However, it is not so easy as it may seem because it is not the new
version of tensorflow that I should mask in my case as on the day
when the tensorflow recompilation failed its version remained the same
and
On 08/01/2022 22:44, Nikos Chantziaras wrote:
This is weird. When doing:
emerge -auDU @world
Portage says:
!!! Problems have been detected with your world file
!!! Please run emaint --check world
!!! Ebuilds for the following packages are either all
!!! masked or don't exist:
me
11 matches
Mail list logo
