15.5, libzypp update, but nothing provides libsolv-tools
Opensuse, just right now firing up a 15.5, kde updater applet shows one update, but when trying to apply it fails. 15.5, libzypp update, but nothing provides libsolv-tools ---------------- nothing provides 'libsolv-tools = 0.7.24' needed by the to be installed libzypp-17.31.13-150400.3.30.1.x86_64 -------------------- what gives? ty
On Tue, Jun 13, 2023 at 6:17 PM cagsm <cumandgets0mem00f@gmail.com> wrote:
just right now firing up a 15.5, kde updater applet shows one update, but when trying to apply it fails. nothing provides 'libsolv-tools = 0.7.24' needed by the to be installed libzypp-17.31.13-150400.3.30.1.x86_64
thanks i see report on factory list. <https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/MQ7X3SHZ6R6YRTT3RQYUBVJHOGNLDSUF/> ty
Hi, Yes, it needs a release of libsolv-tools 0.7.24, this is in the queue. Ciao, Marcus On Tue, Jun 13, 2023 at 06:17:27PM +0200, cagsm wrote:
Opensuse,
just right now firing up a 15.5,
kde updater applet shows one update, but when trying to apply it fails.
15.5, libzypp update, but nothing provides libsolv-tools
----------------
nothing provides 'libsolv-tools = 0.7.24' needed by the to be installed libzypp-17.31.13-150400.3.30.1.x86_64
--------------------
what gives? ty
-- Marcus Meissner (he/him), Distinguished Engineer / Senior Project Manager Security SUSE Software Solutions Germany GmbH, Frankenstrasse 146, 90461 Nuernberg, Germany GF: Ivo Totev, Andrew Myers, Andrew McDonald, Martje Boudien Moerman, HRB 36809, AG Nuernberg
On Tue, Jun 13, 2023 at 6:22 PM Marcus Meissner <meissner@suse.de> wrote:
Yes, it needs a release of libsolv-tools 0.7.24, this is in the queue.
thanks for answering here as well. btw, why is the kde software updater applet so quickly to report an outstanding (pending ;) update, but zypper ref and zypper lu dont show anything, apparently zypper being more intelligent so not show anything as the dependencies are not yet satisfied i kind of reasoning? am i mistaken? thanks.
* cagsm <cumandgets0mem00f@gmail.com> [06-13-23 12:27]:
On Tue, Jun 13, 2023 at 6:22 PM Marcus Meissner <meissner@suse.de> wrote:
Yes, it needs a release of libsolv-tools 0.7.24, this is in the queue.
thanks for answering here as well. btw, why is the kde software updater applet so quickly to report an outstanding (pending ;) update, but zypper ref and zypper lu dont show anything, apparently zypper being more intelligent so not show anything as the dependencies are not yet satisfied i kind of reasoning?
am i mistaken? thanks.
how would zypper know that your particular mirrors had been updated? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
On Tue, Jun 13, 2023 at 7:03 PM Patrick Shanahan <paka@opensuse.org> wrote:
how would zypper know that your particular mirrors had been updated?
dont understand your reasoning. the zypper doesnt want to do zip. the kde updater applet wants to update one stuff which as dependencies but which are not yet released. weird? anyhow wondering about onlineupdate script in cron.daily, and this autoupdate settings in yast, which apparently install patches? but this is some scary stuff when i see the following: ----------- sudo zypper patch Loading repository data... Reading installed packages... Resolving package dependencies... Problem: nothing provides 'libsolv-tools = 0.7.24' needed by the to be installed libzypp-17.31.13-150400.3.30.1.x86 _64 Solution 1: Following actions will be done: deinstallation of libzypp-17.31.8-150400.3.14.1.x86_64 deinstallation of libzypp-plugin-appdata-1.0.1+git.20230117-150500.1.2.noarch deinstallation of snapper-zypp-plugin-0.8.16-150300.3.3.1.x86_64 deinstallation of yast2-pkg-bindings-4.5.2-150500.1.1.x86_64 deinstallation of zypper-1.14.59-150400.3.12.2.x86_64 deinstallation of libyui-qt-pkg16-4.5.2-150500.1.1.x86_64 deinstallation of libyui-ncurses-pkg16-4.5.2-150500.1.1.x86_64 deinstallation of btrfsmaintenance-0.4.2-3.3.1.noarch deinstallation of PackageKit-backend-zypp-1.2.4-150400.3.6.1.x86_64 deinstallation of discover-backend-packagekit-5.27.4-bp155.1.6.x86_64 deinstallation of yast2-packager-4.5.16-150500.1.1.x86_64 deinstallation of yast2-online-update-configuration-4.5.1-150500.1.1.noarch deinstallation of yast2-online-update-4.5.3-150500.1.1.noarch deinstallation of yast2-installation-4.5.16-150500.1.2.noarch deinstallation of yast2-country-4.5.5-150500.1.1.x86_64 deinstallation of yast2-bootloader-4.5.8-lp155.1.5.x86_64 deinstallation of yast2-add-on-4.5.4-150500.1.1.noarch deinstallation of yast2-4.5.25-150500.1.1.x86_64 deinstallation of autoyast2-installation-4.5.13-150500.1.1.noarch deinstallation of purge-kernels-service-0-150200.8.6.1.noarch deinstallation of patterns-base-sw_management-20200505-lp155.10.5.x86_64 deinstallation of patterns-base-base-20200505-lp155.10.5.x86_64 deinstallation of yast2-update-4.5.3-150500.1.1.x86_64 deinstallation of zypper-aptitude-1.14.59-150400.3.12.2.noarch deinstallation of zypper-lifecycle-plugin-0.6.1601367426.843fe7a-1.60.noarch deinstallation of zypper-needs-restarting-1.14.59-150400.3.12.2.noarch deinstallation of patterns-kde-kde_yast-20221001-lp155.2.4.noarch deinstallation of patterns-yast-yast2_basis-20220411-lp155.2.4.x86_64 deinstallation of yast2-network-4.5.20-150500.1.1.noarch deinstallation of yast2-metapackage-handler-4.5.0-150500.1.1.noarch deinstallation of yast2-iscsi-client-4.5.7-150500.1.1.noarch deinstallation of patterns-yast-yast2_desktop-20220411-lp155.2.4.x86_64 deinstallation of yast2-storage-ng-4.5.22-150500.1.1.x86_64 deinstallation of yast2-online-update-frontend-4.5.3-150500.1.1.noarch deinstallation of yast2-users-4.5.4-150500.1.1.x86_64 deinstallation of yast2-security-4.5.6-150500.1.1.noarch deinstallation of yast2-tune-4.5.1-150500.1.1.x86_64 deinstallation of yast2-vm-4.5.0-150500.1.1.x86_64 deinstallation of yast2-apparmor-4.5.0-150500.1.1.noarch deinstallation of yast2-auth-client-4.5.4-150500.1.1.noarch deinstallation of yast2-auth-server-4.5.1-150500.1.1.noarch deinstallation of yast2-control-center-4.5.0-150500.1.5.x86_64 deinstallation of yast2-firewall-4.5.0-150500.1.1.noarch deinstallation of yast2-journal-4.5.3-150500.1.1.noarch deinstallation of yast2-ldap-4.5.0-150500.1.3.x86_64 deinstallation of yast2-mail-4.5.0-150500.1.1.noarch deinstallation of yast2-nfs-client-4.5.2-150500.1.1.noarch deinstallation of yast2-nis-client-4.5.0-150500.1.2.x86_64 deinstallation of yast2-ntp-client-4.5.3-150500.1.2.noarch deinstallation of yast2-pam-4.5.0-150500.1.1.noarch deinstallation of yast2-printer-4.5.2-150500.1.2.x86_64 deinstallation of yast2-proxy-4.5.0-150500.1.1.noarch deinstallation of yast2-samba-client-4.5.3-150500.1.1.noarch deinstallation of yast2-samba-server-4.5.0-150500.1.1.noarch deinstallation of yast2-scanner-4.5.1-150500.1.2.x86_64 deinstallation of yast2-services-manager-4.5.1-150500.1.1.noarch deinstallation of yast2-slp-4.5.0-150500.1.2.x86_64 deinstallation of yast2-snapper-4.5.1-150500.1.1.x86_64 deinstallation of yast2-sound-4.5.0-150500.1.5.x86_64 deinstallation of yast2-squid-4.5.0-150500.1.2.x86_64 deinstallation of yast2-sudo-4.5.0-150500.1.1.noarch deinstallation of yast2-support-4.5.0-150500.1.1.noarch deinstallation of yast2-sysconfig-4.5.0-150500.1.1.noarch deinstallation of yast2-tftp-server-4.5.0-150500.1.1.noarch deinstallation of yast2-vpn-4.5.1-150500.1.1.noarch deinstallation of patterns-base-basesystem-20200505-lp155.10.5.x86_64 deinstallation of patterns-base-enhanced_base-20200505-lp155.10.5.x86_64 deinstallation of patterns-desktop-imaging_opt-20170319-5.17.x86_64 deinstallation of patterns-base-x11-20200505-lp155.10.5.x86_64 deinstallation of yast2-control-center-qt-4.5.0-150500.1.5.x86_64 deinstallation of patterns-fonts-fonts-20190130-lp155.2.4.x86_64 deinstallation of patterns-base-x11_enhanced-20200505-lp155.10.5.x86_64 deinstallation of patterns-desktop-imaging-20201106-lp155.2.4.x86_64 deinstallation of patterns-games-games-20220126-lp155.1.4.x86_64 deinstallation of patterns-kde-kde_plasma-20221001-lp155.2.4.noarch deinstallation of patterns-kde-kde_imaging-20221001-lp155.2.4.noarch deinstallation of patterns-kde-kde-20221001-lp155.2.4.noarch Solution 2: do not install patch:openSUSE-SLE-15.5-2023-2495-1.noarch Solution 3: break libzypp-17.31.13-150400.3.30.1.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/c/d/?] (c): -------------- eeek?! :(
* cagsm <cumandgets0mem00f@gmail.com> [06-13-23 15:27]:
On Tue, Jun 13, 2023 at 7:03 PM Patrick Shanahan <paka@opensuse.org> wrote:
how would zypper know that your particular mirrors had been updated?
dont understand your reasoning. the zypper doesnt want to do zip.
zypper cannot provide what is not available, zip has nothing to do with it.
the kde updater applet wants to update one stuff which as dependencies but which are not yet released. weird?
happens with some regularity
anyhow wondering about onlineupdate script in cron.daily, and this autoupdate settings in yast, which apparently install patches? but this is some scary stuff when i see the following:
scary ??? but I do not use "onlineupdate script". one gets similar responses from "zypper -v dup"
----------- sudo zypper patch Loading repository data... Reading installed packages... Resolving package dependencies...
Problem: nothing provides 'libsolv-tools = 0.7.24' needed by the to be installed libzypp-17.31.13-150400.3.30.1.x86 _64 Solution 1: Following actions will be done: deinstallation of libzypp-17.31.8-150400.3.14.1.x86_64 deinstallation of libzypp-plugin-appdata-1.0.1+git.20230117-150500.1.2.noarch [37.41 lines removed ] deinstallation of patterns-kde-kde_imaging-20221001-lp155.2.4.noarch deinstallation of patterns-kde-kde-20221001-lp155.2.4.noarch Solution 2: do not install patch:openSUSE-SLE-15.5-2023-2495-1.noarch Solution 3: break libzypp-17.31.13-150400.3.30.1.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/3/c/d/?] (c):
so one shows patience and waits for the app to become available, choose solution 2. it is a not uncommon occurance. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
On 2023-06-13 19:03, Patrick Shanahan wrote:
* cagsm <cumandgets0mem00f@gmail.com> [06-13-23 12:27]:
On Tue, Jun 13, 2023 at 6:22 PM Marcus Meissner <meissner@suse.de> wrote:
Yes, it needs a release of libsolv-tools 0.7.24, this is in the queue.
thanks for answering here as well. btw, why is the kde software updater applet so quickly to report an outstanding (pending ;) update, but zypper ref and zypper lu dont show anything, apparently zypper being more intelligent so not show anything as the dependencies are not yet satisfied i kind of reasoning?
am i mistaken? thanks.
how would zypper know that your particular mirrors had been updated?
All those tools are using the same database data, which at this point is local. No package it being downloaded, mirrors differences should not have effect. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 13.06.2023 19:25, cagsm wrote:
On Tue, Jun 13, 2023 at 6:22 PM Marcus Meissner <meissner@suse.de> wrote:
Yes, it needs a release of libsolv-tools 0.7.24, this is in the queue.
thanks for answering here as well. btw, why is the kde software updater applet so quickly to report an outstanding (pending ;) update, but zypper ref and zypper lu dont show anything, apparently zypper being more intelligent so not show anything as the dependencies are not yet satisfied i kind of reasoning?
It is questionable whether it is really "more intelligent", but yes, "zypper patch" (which is effectively what your software updater applet does) and "zypper update" apply different strategies for dependency conflict resolution.
On Tuesday 13 June 2023 21:21:25 Andrei Borzenkov wrote:
On 13.06.2023 19:25, cagsm wrote:
On Tue, Jun 13, 2023 at 6:22 PM Marcus Meissner <meissner@suse.de> wrote:
Yes, it needs a release of libsolv-tools 0.7.24, this is in the queue.
thanks for answering here as well. btw, why is the kde software updater applet so quickly to report an outstanding (pending ;) update, but zypper ref and zypper lu dont show anything, apparently zypper being more intelligent so not show anything as the dependencies are not yet satisfied i kind of reasoning?
It is questionable whether it is really "more intelligent", but yes, "zypper patch" (which is effectively what your software updater applet does) and "zypper update" apply different strategies for dependency conflict resolution.
Yes, 'update' simply skips not applicable package updates, while 'patch' implies the guarantee that a defect is either resolved or you are notified that your system is still affected and asked how to resolve this. We (zypp) decided to add an option to 'patch' in one of the next versions, which will allow to skip not applicable patches. This is something scripts could use to apply as many needed patches as possible. BUT: No matter if one uses 'update' or the new 'patch' option to keep the system unattended as up-to-date as possible, one should call 'zypper patch-check (pchk)' from time to time to check, whether patches are still needed. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres (he/him/his), Engineering & Innovation, ma@suse.com +------------------------------------------------------------------+ SUSE Software Solutions Germany GmbH www.suse.com Frankenstr. 146, 90461 Nuernberg, Germany Geschäftsführer: Ivo Totev, Andrew McDonald, Werner Knoblich (HRB 36809, AG Nürnberg) +------------------------------------------------------------------+
participants (7)
-
Andrei Borzenkov -
cagsm -
Carlos E. R. -
kschneider bout-tyme.net -
Marcus Meissner -
Michael Andres -
Patrick Shanahan