I am unpushing this for now because we need to push 1.7-18 (exactly) stable as it was included in the F30 Final compose. We must freeze the stable repos containing exactly the same content that was in the compose. This can be pushed again after 1.7-18 is pushed stable.
It seems to work OK here? I tried to do the same as @lruzicka:
That worked fine here, it did not fail, I am sitting at the Sugar 'desktop' right now, with the packages from this update.
Looks like gnome-initial-setup may be broken with this, according to openQA:
After install of a live image built with this update, the installed system just boots to an empty desktop where g-i-s should be appearing, but isn't. Will debug this further soon.
Looking into it, I believe there is a genuine mistake in this update which causes the denials @bluepencil and @mattf are seeing. More details in https://bugzilla.redhat.com/show_bug.cgi?id=1698575 . Thus, voting -1.
openQA tests passed aside from known issues unrelated to this update, and upgrade test did not hit the bug, so this looks good.
The fix for the further issue @pwhalen saw is in anaconda, not in initial-setup; so I think we should push this, as it is still required to fix the initial bug and there is nothing wrong on this update's side AFAIK.