Description of problem: urpmi fails to update/install the latest version of google-chrome-stable(127.0.6533.72) with errors about missing libraries, but installing google-chrome with "dnf" works fine. There have been some changes in google chrome on how to handle system libraries that may have led to this situation( https://chromiumdash.appspot.com/commit/5ffd9a0862ed48589bc650a351aaae71e0914c64 ). Here is the link to a reported issue similar with this bug, but for yum rpm manager: https://issues.chromium.org/issues/355141776 Steps to Reproduce: The simple way: 1. Download google-chrome wrapper rpm from https://www.google.com/chrome/ 2. as root run $ urpmi ./google-chrome-stable_current_x86_64.rpm A requested package cannot be installed: google-chrome-stable-127.0.6533.72-1.x86_64 (due to unsatisfied (libgtk-3.so.0()(64bit) or libgtk-4.so.1()(64bit))) Continue installation anyway? (Y/n) y While some packages may have been installed, there were failures. A requested package cannot be installed: google-chrome-stable-127.0.6533.72-1.x86_64 (due to unsatisfied (libgtk-3.so.0()(64bit) or libgtk-4.so.1()(64bit))) Using google repository configuration( https://wiki.mageia.org/en/Installing_Google_Chrome_in_Mageia ), this way google-chrome updates are monitored/installed by mageia tools like drakrpm-update and so on. 1. use urpmi on the latest version directly $ urpmi google-chrome-stable A requested package cannot be installed: google-chrome-stable-127.0.6533.72-1.x86_64 (due to unsatisfied (libcurl.so()(64bit) or libcurl-gnutls.so.4()(64bit) or libcurl-nss.so.4()(64bit) or libcurl.so.4()(64bit))) Workaround: as root, use dnf to install the manually downloaded google-chrome wrapper rpm $ dnf install ./google-chrome-stable_current_x86_64.rpm Regards.
I think urpmi google-chrome-stable --allow-nodeps must works also
Thanks katnatek,:). Your workaround is much better than mine as I'm trying to avoid mixing dnf and urpmi Cheers.
It's happening because urpmi is missing boolean dependencies support (bug 17799). Dnf works OOTB because it has the support. https://rpm-software-management.github.io/rpm/manual/boolean_dependencies.html
I see, thanks for clarifying this.
(In reply to Jani Välimaa from comment #3) > It's happening because urpmi is missing boolean dependencies support (bug > 17799). Dnf works OOTB because it has the support. Thanks for the explanation. That bug is years old, and will clearly not be done. We can only document the fault, and the simple work-arounds in comment 0 or, better, comment 1. Noted for ERRATA9, but will be needed for 10 also.
Keywords: (none) => FOR_ERRATA9Assignee: bugsquad => mageiatoolsSource RPM: (none) => urpmi-8.131-1.mga9.src.rpm
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=17799
https://wiki.mageia.org/en/Mageia_9_Errata#External_software
CC: (none) => friKeywords: FOR_ERRATA9 => IN_ERRATA9
Depends on: (none) => 17799
Lately, I haven't had any issues with a few google-chrome updates, so something must have changed upstream such that the updates don't require a workaround anymore. Should this bug be closed?
(In reply to Aurelian R from comment #7) > Lately, I haven't had any issues with a few google-chrome updates, so > something must have changed upstream such that the updates don't require a > workaround anymore. > Should this bug be closed? I think It's duplicated of bug#17799 *** This bug has been marked as a duplicate of bug 17799 ***
Resolution: (none) => DUPLICATEStatus: NEW => RESOLVEDDepends on: 17799 => (none)