I'm not sure if this has been discussed yet but you may want to add pkgconfig(wayland-eglstream) to builddeps to resolve Fatal: Unknown symbol: libnvidia-egl-wayland.so.1. This effectively makes egl-wayland a dependency of this package during dependency resolution. Given that there is not that may people using wayland on Solus, unsure if we want to do this yet.

Enabled by default in fedora replacing swap partitions AFAICT. https://fedoraproject.org/wiki/Changes/SwapOnZRAM

Needs to be rebased against master

Can you now remove [RFC] from the entire stack. Looks in generally good shape now.

Same source nitpick here

Same source nitpick here

Source nitpick

Only one small nitpick.

I'm guessing it's failing as bison was recently updated. I'll have a look at updating it to 7.2.1.x and backporting a patch if required.

Including python modules just so tests pass is not required. Manual testing is sufficient.

Reopening for visibility until the underling issue is resolved

ffmpeg-chromium is shared between opera, vivaldi-snapshot and vivaldi-stable. Unfortunately there doesn't seem to be a single version of ffmpeg-chromium that supports all three for the time being.

Can you try and install the old version of ffmpeg-chromium and report back? sudo eopkg it https://packages.getsol.us/shannon/f/ffmpeg-chromium/ffmpeg-chromium-88.0.4324.192-10-1-x86_64.eopkg

DataDrake is working on ncurses/readline rebuilds atm. Don't want to touch ncurses to not step on her toes. We can look for a resolution after that. Sorry for the wait.

Maybe mention the package size difference as a percentage or give raw numbers.

Patched fifengine but this package is still completely borked. Read AUR comments: https://aur.archlinux.org/packages/unknown-horizons

Try git add MAINTAINERS.md, git commit --amend as normal then arc diff --edit to upload the updated patch to phabricator. Let me know if that helps

Ah i misunderstood. Feel free to submit a patch to compile with gcc is what i should've have said 👍

Okay feel free to submit a patch to use the bundled llvm for now. Might also be worth a look to see if they have a custom llvm patch that we can backport to our llvm instead.

If we just switch to builtin_libogg=yes does that fix the issue?

base commit rename

Rebase against libffi update