Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2017-5be1e0be10Please login to add feedback.
| 0 | 3 | Test Case firefox addons |
| 0 | 6 | Test Case firefox browse |
| 0 | 6 | Test Case firefox media |
| 0 | 0 | Test Case firefox screenshot |
| 0 | 0 | Test Case User:Sr02mu/Draft/firefox bookmark |
This update has been submitted for testing by stransky.
No regressions noted.
LGTM
Is this build progressing to testing? There's a previous 51.0 build that's also on the queue/not been unpushed.
I agree with dimitrisk. What would it take for Fedora to develop a policy (at least for security updates) that requires--
When bodhi says:
"This update has been submitted for testing by XXX."
then the following bodhi message must appear within 1 hour:
"This update has been pushed to testing."
Naturally a package must then wait for feedback and karma.........
But then, when bodhi says:
"This update has been submitted for stable by bodhi."
then the following bodhi message must appear within 1 hour:
"This update has been pushed to stable."
This update has been pushed to testing.
This update has been submitted for stable by bodhi.
LGTM
This update has been pushed to stable.