Bugzilla – Bug 953070
zypper verify does not act satisfactory
Last modified: 2015-11-11 08:24:35 UTC
Verifying dependencies... 2 Problems: Problem: nothing provides appdata(org.kde.ark.appdata.xml) needed by application:Ark-.noarch Problem: nothing provides appdata(org.kde.dolphin.appdata.xml) needed by application:Dolphin-.noarch Problem: nothing provides appdata(org.kde.ark.appdata.xml) needed by application:Ark-.noarch Solution 1: deinstallation of application:Ark-.noarch Solution 2: break application:Ark-.noarch by ignoring some of its dependencies Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c] (c): 1 Applying solution 1 Problem: nothing provides appdata(org.kde.dolphin.appdata.xml) needed by application:Dolphin-.noarch Solution 1: deinstallation of application:Dolphin-.noarch Solution 2: break application:Dolphin-.noarch by ignoring some of its dependencies Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c] (c): 1 Applying solution 1 Resolving dependencies... Force resolution: No Verifying dependencies... The following 2 applications are going to be REMOVED: Ark noarch Dolphin noarch No additional space will be used or freed after the operation. Dependencies of all installed packages are satisfied. ------------ so no removal and additional free space freed.
The issue looks similar, IMO, to these two: Bug 952325 - nothing provides appdata(thunderbird.appdata.xml) needed by application:Thunderbird-.noarch Bug 952325 - nothing provides appdata(thunderbird.appdata.xml) needed by application:Thunderbird-.noarch reported on Leap 42.1 RC.
=== Please create and attach a solver testcase: > # zypper in --debug-solver nopackage > ... > Generating solver test case... > Solver test case generated successfully at /var/log/zypper.solverTestCase. Then pack the output directory together with /var/log/zypper.log and attach it to the bugreport. In case the testcase exceeds the 10MB limit for bugzilla uploads, you can use 'split' to divide the file into smaller pieces: > $ cd /tmp > $ tar cvjf zypper.solverTestCase.tar.bz2 /var/log/zypper.solverTestCase/ > $ split -b 9M --additional-suffix=-zypper.solverTestCase.tar.bz2 \ > zypper.solverTestCase.tar.bz2 The created pieces will be named like this: > xaa-zypper.solverTestCase.tar.bz2 > xab-zypper.solverTestCase.tar.bz2 > xac-zypper.solverTestCase.tar.bz2 > ...
@Constant: There seems to be a problem connecting the (virtual) application and the (physical) package. Without the requested solver testcase (comment #2) it's hard to say whether this is a packaging problem or something zypper should be able to handle...
Created attachment 655463 [details] /var/log/zypper.solverTestCase.
Thanks. As Carlos suspected in comment #2, the issue is caused by the way the packages were built. The packages are not really malformed, it's more like a dialect zypp does not understand. We'll head for a generic fix, rather than approaching all package maintainers. *** This bug has been marked as a duplicate of bug 952324 ***