This update drops NetworkManager-config-connectivity-fedora's dependency on NetworkManager, which produces a problematic dependency chain during image creation. See bug #1156198.
Please log in to add feedback.
| 0 | 0 | Test Case QA/TestCases/NM Mobile Broadband |
| 0 | 0 | Test Case QA/TestCases/NM VPN OpenVPN |
| 0 | 0 | Test Case QA/TestCases/NM VPN vpnc |
| 0 | 0 | Test Case QA/TestCases/NM WEP |
| 0 | 0 | Test Case QA/TestCases/NM WPA |
| 0 | 0 | Test Case QA/TestCases/NM Wifi |
| 0 | 0 | Test Case DNS-over-SSL |
| 0 | 0 | Test Case DNSSEC-trigger |
| 0 | 0 | Test Case NM Bonding |
| 0 | 0 | Test Case NM Ethernet |
| 0 | 0 | Test Case NM Gnome Hotspot |
| 0 | 0 | Test Case NM KDE Hotspot |
| 0 | 0 | Test Case NM Wireless |
| 0 | 0 | Test Case NM nmcli |
| 0 | 0 | Test Case NetworkManager assume |
| 0 | 0 | Test Case NetworkManager bt pan |
| 0 | 0 | Test Case NetworkManager celldata |
| 0 | 0 | Test Case NetworkManager ipv6 |
This update has been submitted for testing by adamwill.
Taskotron: depcheck test PASSED on i386. Result log: https://taskotron.fedoraproject.org/taskmaster//builders/x86_64/builds/4999/steps/runtask/logs/stdio (results are informative only)
Taskotron: depcheck test PASSED on x86_64. Result log: https://taskotron.fedoraproject.org/taskmaster//builders/x86_64/builds/4999/steps/runtask/logs/stdio (results are informative only)
This update has been obsoleted by https://admin.fedoraproject.org/updates/NetworkManager-0.9.10.0-10.git20140704.fc21
Taskotron: depcheck test FAILED on x86_64. Result log: https://taskotron.fedoraproject.org/taskmaster//builders/x86_64/builds/5288/steps/runtask/logs/stdio (results are informative only)
Automatic push to stable based on karma has been disabled for this update due to failure of an AutoQA test. Update submitter, please check the AutoQA test result and see if there is a valid problem to be fixed here, and fix it if so. If the failure is a mistake on AutoQA's part, you can re-enable the automatic push feature for this update if you like, or push it stable manually once it reaches the requirements under the Updates Policy.