Comments

261 Comments

This update has been unpushed.

@msuchy yes, I realized that and modified our scripts to pass config_opts['use_bootstrap_container'] = False, but it is still a change in expected behavior. If nothing else, it should probably fall back to using the non-bootstrap version if the packages needed for bootstrap are not present.

karma

This version of mock attempts to enforce the presence of dnf dnf-plugins-core distribution-gpg-keys in the chroot, which breaks builds of minimized environments (such as those using only microdnf). Version 1.3.4 worked properly.

karma

This resolves the issues I was seeing with enrolling with Active Directory. I also confirmed that this does not regress enrollment with FreeIPA.

BZ#1445017 After enrolling in an AD domain with realmd, no responders are started

Correction to my note above, I had reported the upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=781217 rather than the downstream bug.

BZ#1444669 [abrt] gnome-software: gs_page_reload(): gnome-software killed by SIGABRT

This update fixes the crash I was seeing in BZ 1444669

BZ#1444669 [abrt] gnome-software: gs_page_reload(): gnome-software killed by SIGABRT
karma

No regressions noted

@anonymous: Can you log in and give karma again? Unless you do, this will remain in testing for another week.

1393373 appears to be fixed by this update.

BZ#1393373 selinux causes certain gnome-disks operations to be 25 seconds delayed
karma

Fixes 1393379 and doesn't introduce any other obvious issues.

BZ#1393379 partitions can't be created nor removed in gnome-disks, cockpit

This update fixes BZ #1391522

BZ#1391522 unknown input device type 'virtio1.0-input'

Apologies for the churn here, folks. I think it's in good order now, so if you wouldn't mind re-testing, that would be much appreciated.

Thanks for the feedback. You're right, I typoed the release field in the dependency. I've got a new build running now that should resolve this. I'll amend this update as soon as it's finished.

This update introduces a bug that has been accepted as a 0day blocker for F25 beta. Please unpush this from updates-testing before Beta release. Adding a fix to https://bugzilla.redhat.com/show_bug.cgi?id=1381045 is also acceptable.

Appears to be working properly for me.

@fredlima: Did the previous version work through a proxy? If not, please don't give negative karma. This update isn't listed as attempting to fix that bug.

  Upgrading   : selinux-policy-3.13.1-214.fc25.noarch                                             18/433 
/etc/selinux/targeted/contexts/files/file_contexts: Multiple different specifications for /var/lib/kubelet(/.*)?  (system_u:object_r:svirt_sandbox_file_t:s0 and system_u:object_r:docker_var_lib_t:s0).
/etc/selinux/targeted/contexts/files/file_contexts: Invalid argument
libsemanage.semanage_install_final_tmp: setfiles returned error code 1. (No such file or directory).
/etc/selinux/targeted/contexts/files/file_contexts: Multiple different specifications for /var/lib/kubelet(/.*)?  (system_u:object_r:svirt_sandbox_file_t:s0 and system_u:object_r:docker_var_lib_t:s0).
/etc/selinux/targeted/contexts/files/file_contexts: Invalid argument
libsemanage.semanage_install_final_tmp: setfiles returned error code 1. (No such file or directory).
semodule:  Failed!
  Upgrading   : selinux-policy-targeted-3.13.1-214.fc25.noarch                                    19/433 
Re-declaration of type udisks2_t
Failed to create node
Bad type declaration at /var/lib/selinux/targeted/tmp/modules/100/udisks2/cil:1
/usr/sbin/semodule:  Failed!
  Upgrading   : libwinpr-2:2.0.0-12.20160909git1855e36.fc25.x86_64                                20/433 
  Installing  : python2-lxml-3.6.4-1.fc25.x86_64                                                  21/433 
  Upgrading   : docker-selinux-2:1.12.1-13.git9a3752d.fc25.x86_64                                 22/433 
Re-declaration of type udisks2_t
Failed to create node
Bad type declaration at /var/lib/selinux/targeted/tmp/modules/100/udisks2/cil:1
/usr/sbin/semodule:  Failed!

@anonymous: please log in with a FAS account if you want your karma to count.

Fixes for me:

  • 768808 identity: Clean up the credential cache and don't keep trying to sign in if we encounter a failure

Application launches and appears to function more or less as advertised.

karma

Basic smoke-testing looks good to me.