Comments

790 Comments

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).

Looks good after basic testing (CLI and even a game on X11). There are some (non-fatal) SELinux warnings, however.

BZ#1458086 snapd-2.27 is available
BZ#1471771 snapd-glib-1.16 is available
BZ#1481247 snapd-2.27.1 is available
BZ#1482173 snapd-2.27.2 is available

Looks good after basic testing (CLI and even a game on wayland).

BZ#1471771 snapd-glib-1.16 is available
BZ#1458086 snapd-2.27 is available
BZ#1481247 snapd-2.27.1 is available
BZ#1482173 snapd-2.27.2 is available

Looks good!

Works fine!

Works fine!

Works fine again, thanks for fixing this!

BZ#1456243 golang-googlecode-go-exp: FTBFS due to missing dependencies on Fedora 26+
BZ#1423669 golang-googlecode-go-exp: FTBFS in rawhide

Works

LGTM (and OpenCL on NVIDIA works fine)

karma

LGTM

karma

@besser82: Thanks for pointing that out, I managed to rebuild the hosed RPM database by manually copying the old library version back into place. dnf works again.

karma

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

karma

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.

karma

No issues encountered.

BZ#1448026 nano-2.8.2 is available

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.

karma

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.

karma

LGTM (and it didn't break any of my packages on rawhide, according to koschei)

No issues encountered during daily routine usage.

BZ#1444586 python-tinydb-3.2.3 is available