Bug 2051019
Summary: | dnf update fails on systemd-udev | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | piero ds <dslpiero> |
Component: | systemd | Assignee: | systemd-maint |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 34 | CC: | daniel.mach, fedoraproject, filbranden, flepied, jmracek, jrohel, lnykryn, mblaha, mhatina, msekleta, packaging-team-maint, pkratoch, rpm-software-management, ryncsn, ssahani, s, systemd-maint, vmukhame, yuwatana, zbyszek |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | systemd-250.6-1.fc36 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-05-27 01:10:02 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
piero ds
2022-02-05 20:16:08 UTC
Thank you very much for the report. It looks like a problem between systemd-udev and systemd. They provides the same file therefore they must ansure that they will be installed in the same version. It can be achieved by adding a conflict in spec file. It requires modification in both rpm: systemd Conflicts: systemd-udev < %{version}-%{release} systemd-udev Conflicts: systemd < %{version}-%{release} Oops. I just moved some files between the subpackages, and didn't think that this would cause problems. I added the Conflicts as suggested now, fingers crossed. This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed. FEDORA-2022-3ca356cd2e has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-3ca356cd2e FEDORA-2022-3ca356cd2e has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-3ca356cd2e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-3ca356cd2e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-3ca356cd2e has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. |