Notiwithstanding that all versions below are ancient, is it really possible for any kdebase* package, or any of any DE's base packages, legitimately to depend on any particular rpm package? If so, how?
# cat /pub/Tmp/out # grep RETT /etc/*lease /etc/os-release:PRETTY_NAME="openSUSE Tumbleweed (20160605) (i586)" # zypper -v in rpm Verbosity: 1 Non-option program arguments: 'rpm' Initializing Target Checking whether to refresh ... Force resolution: No Selecting 'rpm-4.13.0.1-2.1.i586' from repository 'OSS' for installation. Resolving package dependencies... Force resolution: No
Problem: kdebase4-openSUSE-13.2-6.71.i586 requires librpm.so.3, but this requirement cannot be provided deleted providers: rpm-4.12.0.1-13.1.i586 Solution 1: Following actions will be done: remove lock to allow installation of breeze-5.9.4-1.1.i586[OSS] remove lock to allow installation of breeze5-decoration-5.9.4-1.1.i586[OSS] remove lock to allow installation of breeze5-style-5.9.4-1.1.i586[OSS] remove lock to allow installation of breeze5-cursors-5.9.4-1.1.noarch[OSS] remove lock to allow installation of breeze5-icons-5.32.0-1.1.noarch[OSS] remove lock to allow installation of breeze5-wallpapers-5.9.4-1.1.noarch[OSS] remove lock to allow installation of metatheme-breeze-common-5.9.4-1.1.i586[OSS] Solution 2: deinstallation of kdebase4-openSUSE-13.2-6.71.i586 Solution 3: do not install rpm-4.13.0.1-2.1.i586 Solution 4: break kdebase4-openSUSE-13.2-6.71.i586 by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/3/4/c] (c): 4 ...
(new Plasma session still starts and apparently works normally)
Hi,
Am Samstag, 15. April 2017, 05:38:56 CEST schrieb Felix Miata:
Notiwithstanding that all versions below are ancient, is it really possible for any kdebase* package, or any of any DE's base packages, legitimately to depend on any particular rpm package? If so, how?
# cat /pub/Tmp/out # grep RETT /etc/*lease /etc/os-release:PRETTY_NAME="openSUSE Tumbleweed (20160605) (i586)" # zypper -v in rpm Verbosity: 1 Non-option program arguments: 'rpm' Initializing Target Checking whether to refresh ... Force resolution: No Selecting 'rpm-4.13.0.1-2.1.i586' from repository 'OSS' for installation. Resolving package dependencies... Force resolution: No
Problem: kdebase4-openSUSE-13.2-6.71.i586 requires librpm.so.3, but this
that can easily be explained by kdebase4-openSUSE not actually existing for over a year now, it's provided by plasma5-workspace-branding-openSUSE now. I guess that it's been built back when librpm was still at SOVER 3 and some deps like those get added automatically for that during build time:
rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(PayloadIsLzma) <= 4.4.6-1
I don't know for sure whether that's the cause, but please "dupdate" your machine soon...
Cheers, Fabian
requirement cannot be provided deleted providers: rpm-4.12.0.1-13.1.i586 Solution 1: Following actions will be done: remove lock to allow installation of breeze-5.9.4-1.1.i586[OSS] remove lock to allow installation of breeze5-decoration-5.9.4-1.1.i586[OSS] remove lock to allow installation of breeze5-style-5.9.4-1.1.i586[OSS] remove lock to allow installation of breeze5-cursors-5.9.4-1.1.noarch[OSS] remove lock to allow installation of breeze5-icons-5.32.0-1.1.noarch[OSS] remove lock to allow installation of breeze5-wallpapers-5.9.4-1.1.noarch[OSS] remove lock to allow installation of metatheme-breeze-common-5.9.4-1.1.i586[OSS] Solution 2: deinstallation of kdebase4-openSUSE-13.2-6.71.i586 Solution 3: do not install rpm-4.13.0.1-2.1.i586 Solution 4: break kdebase4-openSUSE-13.2-6.71.i586 by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/3/4/c] (c): 4 ...
(new Plasma session still starts and apparently works normally)
On Sat, Apr 15, 2017 at 12:38 AM, Felix Miata mrmazda@earthlink.net wrote:
Notiwithstanding that all versions below are ancient, is it really possible for any kdebase* package, or any of any DE's base packages, legitimately to depend on any particular rpm package? If so, how?
You have to remove orphan packages.. probably running zypper dup is the best alternative.
-
Cristian Rodríguez -
Fabian Vogt -
Felix Miata