dnf
dnf5
dnf5daemon-server introspection xml for Advisory interface dnf5daemon-client advisory info command dnf5daemon-client advisory list command dnf5daemon-server advisory service dnf5daemon-client --help --repofrompath repos by default 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-2023-d454c6f8c5Please log in to add feedback.
| 0 | 0 | Test Case base update cli |
| 0 | 0 | Test Case createrepo c dnf |
| 0 | 0 | Test Case default font installation |
| 0 | 0 | Test Case langpacks packages |
| 0 | 0 | Test Case package install remove |
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
This update's test gating status has been changed to 'waiting'.
@adamwill Please do you know what is the problem with the remaining "running" test? When I open the details, it states "Result: passed" ...
This update's test gating status has been changed to 'passed'.
This update has been submitted for stable by bodhi
Huummm. It seems to be a blip of some kind: the result for the completed test was not reported to resultsdb. This is the second time I've seen that in the last couple of weeks, a bit worrying. I'm not sure if this is because no message was published for the job completion, or the consumer didn't read it, or something else. (It's a bit hard to tell because it means paging through four days of job done messages in datagrepper, which would take a while).
Sorry for the inconvenience, I've kicked the reporter and it's now fixed.