I plan to update assimp from 3.3.1 to the latest release (5.0.1) in
rawhide this week. The following packages will be affected:
I will take care of the rebuilds and any fallout/updates that need to
It just hit me and I didn't find it on this list, so..
In spec after %cmake_install a
failed for the rawhide mass rebuild with no such directory.
After being pointed out (thanks Neal) to change that to
GPG key 0x6A6CD5B765632D3A - 2265 D7F3 A7B0 95CC 3918 630B 6A6C D5B7 6563 2D3A
I've been using f34 with gnome/wayland session on a 16MB machine which
has 8GB zram swap configured.
If I build anything large inside my desktop environment (llvm/clang)
from a gnome-terminal, systemd-oomd blows away my whole desktop slice.
This seems overly hostile.
Now in theory I can use systemd-run to run a shell but my
understanding is the DE is meant to be smarter here.
Is it at least launching firefox etc in new cgroups or are all
processes on my desktop in one big cgroup?
Even if it launched gnome-terminal in another group I assume this
would result in it blowing away all my open terminals just to kill the
compiler/linker that is consuming all the RAM/swap. Again this seems
Any ideas other than campaigning for systemd-oomd to be turned off again?