Raymond Wooninck composed on 2015-04-25 08:19 (UTC+0200):
Felix Miata wrote:
1) enable KDE:Frameworks5 repository (holding Frameworks 5.9.0 + Plasma 5.3 beta)
5 problems:
Nothing provides: libxcb-dpms.so.0 needed by powerdevil5 libxcb-record.so.0 needed by plasma5-desktop libQt5Core.so.5 needed by kwin5 libxcb-cursor.so.0 needed by kwin5
All these ones are present in Factory/Tumbleweed. did you use YaST or Zypper ?
Requires cannot be provided: plasma5-session req powerdevil5
This is caused by the fact that powerdevil5 requires libxcb-dpms.so.0 (from above).
# zypper -v ref Verbosity: 1 Initializing Target Specified repositories: Checking whether to refresh metadata for KDEfw5 Retrieving: repomd.xml ...........................................................................................[done] Repository 'KDEfw5' is up to date. ... Repository 'Update' is up to date. All repositories have been refreshed. # cat /etc/zypp/repos.d/KDEfw5.repo [KDEfw5] autorefresh=0 baseurl=http://download.opensuse.org/repositories/KDE:/Frameworks5/openSUSE_Factory/ enabled=1 gpgcheck=1 gpgkey=http://download.opensuse.org/repositories/KDE:/Frameworks5/openSUSE_Factory/... name=KDEfw5 type=rpm-md # zypper -v dup -r KDEfw5 Verbosity: 1 Initializing Target Loading repository data... Reading installed packages... Computing distribution upgrade... Force resolution: No Computing upgrade... 5 Problems: Problem: nothing provides libxcb-dpms.so.0()(64bit) needed by powerdevil5-5.2.95-35.4.x86_64 Problem: nothing provides libxcb-record.so.0()(64bit) needed by plasma5-desktop-5.2.95-61.4.x86_64 Problem: plasma5-session-5.2.95-19.1.noarch requires powerdevil5 >= 5.2.95, but this requirement cannot be provided Problem: nothing provides libQt5Core.so.5 needed by kwin5-5.2.95-67.1.i586 Problem: nothing provides libxcb-cursor.so.0()(64bit) needed by kwin5-5.2.95-67.1.x86_64 Problem: nothing provides libxcb-dpms.so.0()(64bit) needed by powerdevil5-5.2.95-35.4.x86_64 Solution 1: keep obsolete powerdevil5-5.2.2-1.1.x86_64 Solution 2: break powerdevil5-5.2.95-35.4.x86_64 by ignoring some of its dependencies Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c] (c): 2 Applying solution 2 Problem: nothing provides libxcb-record.so.0()(64bit) needed by plasma5-desktop-5.2.95-61.4.x86_64 Solution 1: Following actions will be done: keep obsolete plasma5-desktop-5.2.2-1.1.x86_64 keep obsolete libksysguard5-5.2.2-1.1.x86_64 keep obsolete plasma5-workspace-libs-5.2.2-3.1.x86_64 Solution 2: break plasma5-desktop-5.2.95-61.4.x86_64 by ignoring some of its dependencies Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c] (c): 2 Applying solution 2 Problem: plasma5-session-5.2.95-19.1.noarch requires powerdevil5 >= 5.2.95, but this requirement cannot be provided uninstallable providers: powerdevil5-5.2.95-35.4.x86_64[KDEfw5] powerdevil5-5.2.95-35.4.i586[KDEfw5] Solution 1: Following actions will be done: keep obsolete plasma5-session-5.2.2-1.1.noarch keep obsolete libksysguard5-5.2.2-1.1.x86_64 keep obsolete plasma5-workspace-libs-5.2.2-3.1.x86_64 Solution 2: break plasma5-session-5.2.95-19.1.noarch by ignoring some of its dependencies Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c] (c): 2 Applying solution 2 Problem: nothing provides libQt5Core.so.5 needed by kwin5-5.2.95-67.1.i586 Solution 1: keep obsolete kwin5-5.2.2-2.1.x86_64 Solution 2: break kwin5-5.2.95-67.1.i586 by ignoring some of its dependencies Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c] (c): 2 Applying solution 2 Problem: nothing provides libxcb-cursor.so.0()(64bit) needed by kwin5-5.2.95-67.1.x86_64 Solution 1: Following actions will be done: keep obsolete plasma5-workspace-5.2.2-3.1.x86_64 keep obsolete libksysguard5-5.2.2-1.1.x86_64 keep obsolete plasma5-workspace-libs-5.2.2-3.1.x86_64 Solution 2: break kwin5-5.2.95-67.1.x86_64 by ignoring some of its dependencies Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c] (c): 2 Applying solution 2 Resolving dependencies... Computing distribution upgrade... Force resolution: No Computing upgrade... The following 2 NEW packages are going to be installed: kpeople5 5.9.0-13.1 libKF5XmlRpcClient5 5.9.0-10.1 The following 118 packages are going to be upgraded: breeze 5.2.2-1.1 -> 5.2.95-46.1 ... systemsettings5 5.2.2-1.1 -> 5.2.95-39.1 The following 118 packages are going to change vendor: breeze 5.2.2-1.1 -> 5.2.95-46.1 openSUSE -> obs://build.opensuse.org/KDE ... systemsettings5 5.2.2-1.1 -> 5.2.95-39.1 openSUSE -> obs://build.opensuse.org/KDE 118 packages to upgrade, 2 new, 118 to change vendor. Overall download size: 65.0 MiB. Already cached: 0 B After the operation, additional 12.6 MiB will be used. Continue? [y/n/? shows all options] (y): n
3) try the live ISO:
5.3 still hasn't found its way into Rawhide, and 346059 is still happening in it.
We are NOT Fedora, so we do not have Rawhide.
And we no longer have a development release. Instead we have a rolling release, which means longer waiting to see upstream developments and bug fixes show up unless adding optional repos, which I do on a limited basis for specific reasons at suggestion or direction of others, or by employing BS directly or building locally, neither of which I do.
I don't know what you are trying to test or how to test it, but you seem to be reporting bugs based on Fedora installations. So is the above attempts really on an openSUSE installation ??? Or are you trying to install openSUSE packages on top of a Fedora system ? If the latter, then you would indeed have some dependency issues.
I use openSUSE. This system, used for normal everyday activities, is multiboot, as are all my machines, but with only openSUSE releases. I test TW, Rawhide, Cauldron and on rare occasions others, Kubuntu mostly. Testing on multiple distros and on multiple hardware combinations is necessary to figure out where to point blame when a problem is found, and often to determine if there even is a problem. The KDE3 transition to KDE4 legacy remains a painful but strong memory. So does dealing with too many upstream KDE people in discussing loss of functionality in their recreations, and kde.org web site shortcomings. Consequently, I avoided dipping my toes in v5 except where forced by lack of choice (Rawhide), until 3 weeks ago when I did my first v5 to a fresh TW, so that I could determine whether Breeze in particular and v5 in general was equally bad in TW, in anticipation of filing one or more A11Y bugs against Breeze as a default theme. Without replication in more than one distro's implementation, I have no way to tell whether problems are inherited from upstream. If I file a bug upstream, it is because I believe it was caused by upstream, in most cases based upon replicating it in more than one distro. Same goes for Xorg, driver and other foundational bugs. I try hard to limit reports I file to things that are real problems that should be fixable, and have not already been reported, avoiding littering bug trackers with things that clutter search results and waste QA and owner time. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org