Bug 1291506
Summary: | "dnf reinstall kernel-headers" first reinstalls and then erases same version | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | windchine |
Component: | dnf | Assignee: | Packaging Maintenance Team <packaging-team-maint> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 22 | CC: | jsilhan, mdomonko, mluscon, packaging-team-maint, pnemade, vmukhame, windchine |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-01-04 15:04:06 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
windchine
2015-12-15 01:37:32 UTC
(In reply to windchine from comment #0) > ... > Running transaction > Reinstalling: kernel-headers-4.2.6-201.fc22.x86_64 1/2 > Erasing : kernel-headers-4.2.6-201.fc22.x86_64 2/2 > Verifying : kernel-headers-4.2.6-201.fc22.x86_64 1/2 > Verifying : kernel-headers-4.2.6-201.fc22.x86_64 2/2 We should investigate how the DNF transaction set looks after resolution. If into rpm transaction goes just reinstall demand then rpm is on blame. The total summary does not mention the Erase package. I don't see any file inside /usr/src/kernels/ dir: `sudo dnf repoquery --releasever=22 kernel-headers -l | grep src` Do you have kernel-headers on the system after dnf command execution? Can you send output of `rpm -q kernel-headers`, please? I realize now that the package I needed to install the kernel headers into /usr/src/kernels/ was actually "kernel-devel", not "kernel-headers", so that part of the bug report is spurious. The misleading transaction report however led me to think that the package was being installed and then removed. Without that report I would likely have reached the correct conclusion and found the correct package to install rather than concluding that dnf or the package metadata were faulty. I think it would be of value if dnf (etc.) could be modified to not issue the spurious "Erasing" message under these conditions. Thanks. As requested: # rpm -q kernel-headers kernel-headers-4.2.7-300.fc23.x86_64 # rpm -q kernel-devel kernel-devel-4.2.7-300.fc23.x86_64 (In reply to windchine from comment #2) > I realize now that the package I needed to install the kernel headers into > /usr/src/kernels/ was actually "kernel-devel", not "kernel-headers", so that > part of the bug report is spurious. Great, thanks! > The misleading transaction report however led me to think that the package > was being installed and then removed. Without that report I would likely > have reached the correct conclusion and found the correct package to install > rather than concluding that dnf or the package metadata were faulty. I think > it would be of value if dnf (etc.) could be modified to not issue the > spurious "Erasing" message under these conditions. The "Erasing" message indeed comes from the rpm transaction set which contains an install element (shown as "Reinstalling") and an erase element (shown as "Erasing") for each reinstall operation. I do agree that this is confusing to the user, though. However, as Jan mentioned, the only conclusive message is the transaction summary towards the end ("Reinstalled:") which works correctly. Closing now. |