Those _advisory_update module failed
errors in automated tests are not your fault, we're working on fixing them.
Those _advisory_update module failed
errors in automated tests are not your fault, we're working on fixing them.
Those _advisory_update module failed
errors in automated tests are not your fault, we're working on fixing them.
Those _advisory_update module failed
errors in automated tests are not your fault, we're working on fixing them.
We're looking at those _advisory_update module failed
errors in automated tests, they affect multiple updates, stay tuned.
We're looking at those _advisory_update module failed
errors in automated tests, they affect multiple updates, stay tuned.
We're looking at those _advisory_update module failed
errors in automated tests, they affect multiple updates, stay tuned.
We're looking at those _advisory_update module failed
errors in automated tests, they affect multiple updates, stay tuned.
We're looking at those _advisory_update module failed
errors in automated tests, they affect multiple updates, stay tuned.
I'm in the process of restarting update.* tests, there was another problem in shadow-utils
firewalld 2.2.0 was untagged from Rawhide today because it was broken, perhaps the issue is related to that
I can connect to my company's OpenVPN server through NetworkManager
I can connect to my company's OpenVPN server
I can see and add new transactions. The UI changed a bit.
no problems with a common usage
@jrische The update.upgrade_desktop_encrypted_64bit
automatic test is known to be broken (a race condition) at the moment, it's safe to waive the gating failure (if there's no other failure) and allow it to go stable.
no issues with Thinkpad P1 Gen4
tested a few commands, worked fine
Those
_advisory_update module failed
errors in automated tests are not your fault, we're working on fixing them.