Bug 1650708
Summary: | dnf - a case of a dependency mis-resolution | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Michal Jaegermann <michal.jnn> |
Component: | pywebkitgtk | Assignee: | Michael DePaulo <mikedep333> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 29 | CC: | dmach, ivazqueznet, mblaha, mhatina, mikedep333, packaging-team-maint, rpm-software-management, vmukhame, walters |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-11-27 19:59:39 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
Michal Jaegermann
2018-11-16 22:19:32 UTC
On a system updated to F29, i.e. dnf-4.0.4-2.fc29 and libsolv-0.7.1-1.fc29, and after 'rpm -i --nodeps pywebkitgtk-1.1.8-13.fc26.x86_64.rpm' (which is the last available version of this package) running 'dnf remove pywebkitgtk' does _not_ trigger an avalanche of attempted removals as in the original report. The bunch of removed packages are dependencies of gnucash (which package is also about to be removed), not pywebkitgtk. There probably are some packaging problems with pywebkitgtk - on my fully updated Fedora 29 I'm not able to even install it: [root@f29]# dnf install pywebkitgtk Error: Problem: conflicting requests - nothing provides libjavascriptcoregtk-1.0.so.0()(64bit) needed by pywebkitgtk-1.1.8-13.fc26.x86_64 - nothing provides libwebkitgtk-1.0.so.0()(64bit) needed by pywebkitgtk-1.1.8-13.fc26.x86_64 I'm reassigning this bug to libwebkitgtk. (In reply to Marek Blaha from comment #2) > The bunch of removed packages are dependencies of gnucash (which package is > also about to be removed), not pywebkitgtk That is the first problem. There is no good reason for gnucash to be removed in the first place. In an absence of pywebkitgtk 'dnf distro-sync ...' updates gnucash to gnucash-3.3-1.fc29 without any fuss. . > There probably are some packaging problems with pywebkitgtk - on my fully > updated Fedora 29 I'm not able to even install it: This is not surprising either. That is why when I was trying to see if a similar mess-up happens in F29, in comment #1, I was installing that with 'rpm -i --nodeps pywebkitgtk-1.1.8-13.fc26.x86_64.rpm' as libjavascriptcoregtk-1.0.so.0()(64bit) is not available in F29 while it was in F27. On F29 webkit2gtk3-js provides libjavascriptcoregtk-4.0.so.18()(64bit) and pywebkitgtk packages were NOT updated above F26. > I'm reassigning this bug to libwebkitgtk. It looks to me somewhat premature. Try on F29 installation 'dnf remove gnucash'. This attempt to remove, among other things, perl-Date-ISO8601 perl-DateTime perl-DateTime-Locale perl-DateTime-TimeZone perl-DateTime-TimeZone-SystemV perl-DateTime-TimeZone-Tzfile Are suggesting that these are dependent on gnucash? dnf does not seem to agree with you. After 'rpm -e gnucash' a check with 'dnf repoquery --unsatisfied' does not lodge any complaints. BTW - a list of packages slated for a removal in F29 after 'dnf remove gnucash' is _substantially_ shorter that the one quoted in the original report while these "missing" packages are still present in my installation. The problem is in pywebkitgtk. You can either remove it from system, or run 'dnf distro-sync --allowerasing' (which will allow solver to remove packages when solving problem). pywebkitgtk is not installable on F29 because of unmet dependencies libjavascriptcoregtk-1.0.so.0 and libwebkitgtk-1.0.so.0. This should be repaired in the first. Regarding gnucash dependencies. These packages are not dependent on gnucash. They are dependencies of gnucash: $ dnf repoquery --requires gnucash . . perl(Finance::Quote) . . $ dnf repoquery --requires perl-Finance-Quote . . perl(DateTime) . . $ dnf repoquery --requires perl-DateTime . . perl(DateTime::Locale) >= 1.06 perl(DateTime::TimeZone) >= 2.02 . . And so on. When you run 'dnf remove gnucash', these packages are removed as they were installed as dependencies and no other package on system requires them. (See https://dnf.readthedocs.io/en/latest/command_ref.html#remove-command and clean_requirements_on_remove option description here: https://dnf.readthedocs.io/en/latest/conf_ref.html) This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. 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 Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |