Bug 2185239
Summary: | dnf 4.15 broke repoquery's "%{INSTALLTIME}" queryformat | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Geraldo Simião <geraldo.simiao.kutz> |
Component: | dnf | Assignee: | Jan Kolarik <jkolarik> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 37 | CC: | daniel.mach, decathorpe, jkolarik, jmracek, jrohel, mblaha, packaging-team-maint, pkratoch, rpm-software-management, rust-sig, vmukhame |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | dnf-4.15.1-1.fc38 dnf-4.15.1-1.fc37 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-05-20 01:48:03 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Geraldo Simião
2023-04-07 13:50:13 UTC
Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.8 Kernel Version: 6.2.9-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-3632QM CPU @ 2.20GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4000 Manufacturer: Acer Product Name: Aspire V3-571 Parsing DNF output has nothing to do with the login. If the login failed, you would get a different error message. I an reproduce this issue on my local system, where I still have a valid session cookie. This error occurs later, where fedora-update-feedback queries dnf (as mentioned by the error message: "Failed to parse dnf output: input contains invalid characters".). It seems to be a regression in dnf 4.15, which broke the `%{INSTALLTIME}` option in "dnf repoquery": https://bodhi.fedoraproject.org/updates/FEDORA-2023-308ef1c754#comment-2979552 Oh, ok. Good that you get where the problem is. If there's a scratch build that someone wanna I test here, just let me know. It appears that the validation that was introduced with version 4.15 (to fix https://bugzilla.redhat.com/show_bug.cgi?id=2140884 ) excludes some valid identifiers that previously worked. Looking into it further, it appears that while %{INSTALLTIME} no longer works, %{installtime} *does*, so I will use this as a workaround. A fix from @jlebon was already merged in the upstream to fix this problem: https://github.com/rpm-software-management/dnf/pull/1922. FEDORA-2023-f418df9544 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-f418df9544 FEDORA-2023-7b8cb5535a has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-7b8cb5535a FEDORA-2023-7b8cb5535a has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-7b8cb5535a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-7b8cb5535a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2023-f418df9544 has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-f418df9544` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-f418df9544 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2023-f418df9544 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2023-7b8cb5535a has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. |