Bug 1640781
| Summary: | package xfce-theme-manager-0.3.6-3.fc26.x86_64 requires libxfconf-0.so.2()(64bit), but none of the providers ca n be installed | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Villy Kruse <ppywlkiqletw> |
| Component: | xfce-theme-manager | Assignee: | Eduardo Echeverria <echevemaster> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 30 | CC: | echevemaster, musmeh55, rosset.filipe |
| 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-07-16 19:40:22 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
Villy Kruse
2018-10-18 18:19:38 UTC
Shall we consider this package dead? [root@mybox ~]# dnf install xfce-theme-manager Last metadata expiration check: 2:20:46 ago on Fri 28 Jun 2019 07:15:11 CEST. Error: Problem: conflicting requests - nothing provides libxfconf-0.so.2()(64bit) needed by xfce-theme-manager-0.3.6-3.fc26.x86_64 (try to add '--skip-broken' to skip uninstallable packages) (In reply to Villy Kruse from comment #1) > Shall we consider this package dead? > > > [root@mybox ~]# dnf install xfce-theme-manager > Last metadata expiration check: 2:20:46 ago on Fri 28 Jun 2019 07:15:11 CEST. > Error: > Problem: conflicting requests > - nothing provides libxfconf-0.so.2()(64bit) needed by > xfce-theme-manager-0.3.6-3.fc26.x86_64 > (try to add '--skip-broken' to skip uninstallable packages) thanks for the report, we are working to bring 0.3.8 to latest Fedora releases. *** This bug has been marked as a duplicate of bug 1676230 *** |