Robert Gonzalez

Yes, it is still present.

I'm not sure why the abi changed. I built glog without looking at the cmake file. The package is also 4 years old, maybe they had to make a change.

Is this a task that I can do or is it something the Solus team handles?

To check packages that rely on it, do I just run `eopkg info glog`? Also, if those packages themselves have breaking abi changes, those will need to be rebuilt, correct?

Sorry about that. I forgot about it and have been busy with school.

There must have been a gtk2 app that used it at one point. It must have been rewritten to gtk3 and used a newer gtksourceview version. Do we have to...

So, it seems safe to deprecate.

This issue is still present.

> @uni-dos: does running `sudo modprobe vfat` before updating resolve the issue for you? So: > > ```console > sudo modprobe vfat > sudo env CBM_DEBUG=1 eopkg it --reinstall linux-current...

Nothing changed