** dnf 4.18.0 **
New features:
Bug fixes:
Others:
** libdnf 0.72.0 **
New features:
Bug fixes:
Others:
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-a066057708Please login 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 has been submitted for testing by bodhi.
This update's test gating status has been changed to 'failed'.
This is broken (it makes anaconda crash). I believe I've identified the reason, I am confirming it now.
OK, yes, it is what I thought. The problematic change is "Do not print details of verifying". anaconda relies on the
PKG_VERIFYmessages to detect when installation has completed successfully. If it doesn't see those messages, it kinda falls through to an assumption that the transaction ended unexpectedly.Rawhide anaconda has been patched to handle this change - see https://github.com/rhinstaller/anaconda/pull/5229 - but anaconda for F37, F38 and F39 have not.
We can either revert that change in dnf for stable releases (since clearly it relied on an incorrect assumption, that nothing else cared about those messages), or we can backport the anaconda patch, do anaconda builds, and add the anaconda builds to these updates.
This update has been pushed to testing.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
Works.
jkolarik edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by jkolarik.
This update's test gating status has been changed to 'waiting'.
Based on the feedback above, dnf was rebuilt without the change "Do not print details of verifying (RhBug:1908253)" which was breaking the Anaconda usage. Should be fine now.
This update's test gating status has been changed to 'failed'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
This update has been pushed to testing.
DNF is working fine, but it have again some regression that cause fedora-update-feedback to fail with this message:
I was looking into the new commits pushed since the previous dnf version and I don't see anything changed related to the repoquery output. I believe we are talking about this trigger from the fedora-update-feedback package: https://github.com/ironthree/fedora-update-feedback/blob/main/src/sysinfo.rs#L203.
And testing it locally on my installed packages set, I compared the dnf 4.16.2 output with dnf 4.18.0, apparently without any changes.
Please, if it is reproducible, file a bug against dnf in Bugzilla with specific input data. Thanks!
This update can be pushed to stable now if the maintainer wishes
looks good here.
This update has been submitted for stable by adamwill.
There is an ongoing freeze; this will be pushed to stable after the freeze is over.
This update has been pushed to stable.
It looks like bug https://bugzilla.redhat.com/show_bug.cgi?id=2245773 have a fix already. Will there be a new build with it?
Hi there, as the https://bugzilla.redhat.com/show_bug.cgi?id=2245773 was not marked as a severe issue, we are planning to do the next build in the standard manner, in a few weeks.