There's an error in the vala bindings (cheader_filename points at the wrong file name: AppStream-1.0.h instead of appstream.h), which breaks builds of two of my packages (appcenter, slingshot-launcher).

There's an error in the vala bindings (cheader_filename points at the wrong file name: AppStream-1.0.h instead of appstream.h), which breaks builds of two of my packages (appcenter, slingshot-launcher).

This update hosed by RPM database, which I could only rebuild by manually copying the old library back onto my system.

I'm not sure what happened, but dnf crashed when doing the upgrade containing this dnf update with a "Floating point exception", and now I can't run dnf anymore because I get "Segmentation fault" or errors in db5.

The default background image(s) is no longer present, resulting in black (or, apparently, blue) desktop backgrounds after updating.

All folders (normalish, standard, tv-wide, wide) in the folder /usr/share/backgrounds/f26/default are empty.

Over the past two weeks of using this, I ran into a bug / unwanted (and undocumented) change in behavior: local RPM packages can't be installed into the build environment anymore. I reported this issue at https://github.com/rpm-software-management/mock/issues/72

Changing my karma from +1 to -1 as a result, since this is a regression of the expected behavior for the default configuration.