I am a relatively new user of Tumbleweed so I am unfamiliar with the best course in this update problem. zypper dup gives me this: Computing distribution upgrade... Problem: the to be installed imlib2-devel-1.11.0-80.1.x86_64 requires 'libImlib2-1 = 1.11.0', but this requirement cannot be provided not installable providers: libImlib2-1-1.11.0-80.1.i586[https-download.opensuse.org-6a0df1c6] libImlib2-1-1.11.0-80.1.x86_64[https-download.opensuse.org-6a0df1c6] Solution 1: install imlib2-devel-1.10.0-1.3.x86_64 from vendor openSUSE replacing imlib2-devel-1.10.0-79.9.x86_64 from vendor obs://build.opensuse.org/graphics Solution 2: install libImlib2-1-1.11.0-80.1.x86_64 from vendor obs://build.opensuse.org/graphics replacing libImlib2-1-1.10.0-1.3.x86_64 from vendor openSUSE Solution 3: keep obsolete imlib2-devel-1.10.0-79.9.x86_64 Solution 4: break imlib2-devel-1.11.0-80.1.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/4/c/d/?] (c): What's the best move in this situation. I had the same problem earlier but forget what I chose and as a result my taskbar tint2 started showing blank squares instead of the proper icons and the .xsession-errors file was filled with errors. Thank for any help Frank
On 18.03.2023 17:05, Frank McCormick wrote:
I am a relatively new user of Tumbleweed so I am unfamiliar with the best course in this update problem.
zypper dup gives me this:
Computing distribution upgrade...
Problem: the to be installed imlib2-devel-1.11.0-80.1.x86_64 requires 'libImlib2-1 = 1.11.0', but this requirement cannot be provided not installable providers: libImlib2-1-1.11.0-80.1.i586[https-download.opensuse.org-6a0df1c6]
libImlib2-1-1.11.0-80.1.x86_64[https-download.opensuse.org-6a0df1c6] Solution 1: install imlib2-devel-1.10.0-1.3.x86_64 from vendor openSUSE replacing imlib2-devel-1.10.0-79.9.x86_64 from vendor obs://build.opensuse.org/graphics Solution 2: install libImlib2-1-1.11.0-80.1.x86_64 from vendor obs://build.opensuse.org/graphics replacing libImlib2-1-1.10.0-1.3.x86_64 from vendor openSUSE
It is up to you to decide whether you want packages from openSUSE or whether you want packages from third-party repository, but at least keep it consistent. Unless you are building software locally you also do not need any -devel package at all, so one possibility is to simple remove them.
Solution 3: keep obsolete imlib2-devel-1.10.0-79.9.x86_64 Solution 4: break imlib2-devel-1.11.0-80.1.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/3/4/c/d/?] (c):
What's the best move in this situation. I had the same problem earlier but forget what I chose and as a result my taskbar tint2 started showing blank squares instead of the proper icons and the .xsession-errors file was filled with errors.
Thank for any help
Frank
On 3/18/23 10:26, Andrei Borzenkov wrote:
Computing distribution upgrade...
Problem: the to be installed imlib2-devel-1.11.0-80.1.x86_64 requires 'libImlib2-1 = 1.11.0', but this requirement cannot be provided not installable providers: libImlib2-1-1.11.0-80.1.i586[https-download.opensuse.org-6a0df1c6] libImlib2-1-1.11.0-80.1.x86_64[https-download.opensuse.org-6a0df1c6] Solution 1: install imlib2-devel-1.10.0-1.3.x86_64 from vendor openSUSE replacing imlib2-devel-1.10.0-79.9.x86_64 from vendor obs://build.opensuse.org/graphics Solution 2: install libImlib2-1-1.11.0-80.1.x86_64 from vendor obs://build.opensuse.org/graphics replacing libImlib2-1-1.10.0-1.3.x86_64 from vendor openSUSE
It is up to you to decide whether you want packages from openSUSE or whether you want packages from third-party repository, but at least keep it consistent.
Unless you are building software locally you also do not need any -devel package at all, so one possibility is to simple remove them.
What I do not understand is why the devel package is not available from the same source as the library. I have temporarily solved the problem by rolling back to a previous snapshot, but would really like to understand what is going on. What is the difference between vendor openSUSE and vendor obs://build.opensuse.org/graphics...which one should be picked ? Thanks Frank
On 18.03.2023 18:07, Frank McCormick wrote:
On 3/18/23 10:26, Andrei Borzenkov wrote:
Computing distribution upgrade...
Problem: the to be installed imlib2-devel-1.11.0-80.1.x86_64 requires 'libImlib2-1 = 1.11.0', but this requirement cannot be provided not installable providers: libImlib2-1-1.11.0-80.1.i586[https-download.opensuse.org-6a0df1c6] libImlib2-1-1.11.0-80.1.x86_64[https-download.opensuse.org-6a0df1c6] Solution 1: install imlib2-devel-1.10.0-1.3.x86_64 from vendor openSUSE replacing imlib2-devel-1.10.0-79.9.x86_64 from vendor obs://build.opensuse.org/graphics Solution 2: install libImlib2-1-1.11.0-80.1.x86_64 from vendor obs://build.opensuse.org/graphics replacing libImlib2-1-1.10.0-1.3.x86_64 from vendor openSUSE
It is up to you to decide whether you want packages from openSUSE or whether you want packages from third-party repository, but at least keep it consistent.
Unless you are building software locally you also do not need any -devel package at all, so one possibility is to simple remove them.
What I do not understand is why the devel package is not available from the same source as the library.
What makes you think so? Of course it is. Why you have run-time library from one repository and devel package for this library from another repository we have no way to answer - it is your system, only you can answer what and why you installed.
I have temporarily solved the problem by rolling back to a previous snapshot, but would really like to understand what is going on.
You have libImlib2 package from openSUSE and imlib2-devel from graphics project. Now graphics project has updated imlib2 to version 1.11, both libImlib2 and imlib2-devel. Tumbleweed is still on version 1.10. Because imlib2-devel is from graphics project, zypper wants to update it from 1.10 to 1.11. To do it zypper also must update libImlib2 from 1.10 to 1.11. But Tumbleweed does not have version 1.11 and zypper by default does not switch vendor automatically. Hence it asks you whether you want to switch both packages to Tumbleweed version or to graphics project version.
What is the difference between vendor openSUSE and vendor obs://build.opensuse.org/graphics...
Packages from "vendor openSUSE" are packages "officially" built and published as part of openSUSE distributions, in this case Tumbleweed. obs://build.opensuse.org/graphics is project on build.opensuse.org; b.o.o is hosting platform to automate building of packages. These packages are not part of openSUSE distribu(even if they are built *for* openSUSE). They can be used as development/test bed before packages are submitted to "official" distribution or they can be used to build anything that is not part of "official" distribution.
which one should be picked ?
It is entirely up to you. As I already said, it is your system, you must have some reasons to add this repository in the first place. Usually the reason to use these repositories is either "latest and greatest" that is not (yet) available from "official" openSUSE or packages that are not included in openSUSE at all for whatever reason.
On 3/18/23 11:28, Andrei Borzenkov wrote:
You have libImlib2 package from openSUSE and imlib2-devel from graphics project. Now graphics project has updated imlib2 to version 1.11, both libImlib2 and imlib2-devel. Tumbleweed is still on version 1.10. Because imlib2-devel is from graphics project, zypper wants to update it from 1.10 to 1.11. To do it zypper also must update libImlib2 from 1.10 to 1.11. But Tumbleweed does not have version 1.11 and zypper by default does not switch vendor automatically. Hence it asks you whether you want to switch both packages to Tumbleweed version or to graphics project version.
I reverted the dev package to Tumbleweed and that has solved the problem.
Packages from "vendor openSUSE" are packages "officially" built and published as part of openSUSE distributions, in this case Tumbleweed. obs://build.opensuse.org/graphics is project on build.opensuse.org; b.o.o is hosting platform to automate building of packages. These packages are not part of openSUSE distribu(even if they are built *for* openSUSE). They can be used as development/test bed before packages are submitted to "official" distribution or they can be used to build anything that is not part of "official" distribution.
OK. Now I understand. I have no idea how the dev package was installed from the graphics repository. User error I guess :) Thank you.
Frank McCormick composed on 2023-03-18 13:45 (UTC-0400):
OK. Now I understand. I have no idea how the dev package was installed from the graphics repository. User error I guess :)
Optional repos only get enabled because of your action of installing software you didn't find in standard repos. Typically this action ensues from using a 1-click installation from https://software.opensuse.org/search. Once enabled, optional repos produce risk of "upgrading" other software available from that repo. 1-clicks are best avoided. Once used, the repos they enable need to be disabled or removed, or at least their use closely monitored. To install software found via https://software.opensuse.org/search you can use the opi command to install with less resulting danger. Opi can also find software. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
* Felix Miata <mrmazda@earthlink.net> [03-18-23 14:43]:
Frank McCormick composed on 2023-03-18 13:45 (UTC-0400):
OK. Now I understand. I have no idea how the dev package was installed from the graphics repository. User error I guess :)
Optional repos only get enabled because of your action of installing software you didn't find in standard repos. Typically this action ensues from using a 1-click installation from https://software.opensuse.org/search. Once enabled, optional repos produce risk of "upgrading" other software available from that repo. 1-clicks are best avoided. Once used, the repos they enable need to be disabled or removed, or at least their use closely monitored. To install software found via https://software.opensuse.org/search you can use the opi command to install with less resulting danger. Opi can also find software.
opi is great but would not have prevented installing packages from wrong repo. <user> is always the greatest risk to a system. -- (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 3/18/23 15:03, Patrick Shanahan wrote:
* Felix Miata <mrmazda@earthlink.net> [03-18-23 14:43]:
Frank McCormick composed on 2023-03-18 13:45 (UTC-0400):
OK. Now I understand. I have no idea how the dev package was installed from the graphics repository. User error I guess :)
Optional repos only get enabled because of your action of installing software you didn't find in standard repos. Typically this action ensues from using a 1-click installation from https://software.opensuse.org/search. Once enabled, optional repos produce risk of "upgrading" other software available from that repo. 1-clicks are best avoided. Once used, the repos they enable need to be disabled or removed, or at least their use closely monitored. To install software found via https://software.opensuse.org/search you can use the opi command to install with less resulting danger. Opi can also find software.
opi is great but would not have prevented installing packages from wrong repo. <user> is always the greatest risk to a system.
Yes indeed. I am living proof of that :)
Patrick Shanahan composed on 2023-03-18 15:03 (UTC-0400):
* Felix Miata composed:
Frank McCormick composed on 2023-03-18 13:45 (UTC-0400):
OK. Now I understand. I have no idea how the dev package was installed from the graphics repository. User error I guess :)
Optional repos only get enabled because of your action of installing software you didn't find in standard repos. Typically this action ensues from using a 1-click installation from https://software.opensuse.org/search. Once enabled, optional repos produce risk of "upgrading" other software available from that repo. 1-clicks are best avoided. Once used, the repos they enable need to be disabled or removed, or at least their use closely monitored. To install software found via https://software.opensuse.org/search you can use the opi command to install with less resulting danger. Opi can also find software.
opi is great but would not have prevented installing packages from wrong repo. <user> is always the greatest risk to a system.
Indeed. OTOH, "Less resulting danger" is key. IME, opi asks whether to keep the new repo(s) enabled. Answer no, and the risk may be zero unless and until such time as admin re-enables non-standard repo(s); "may be" because *admin/user* possibly shouldn't be installing what he has selected for installation using opi. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 3/18/23 14:40, Felix Miata wrote:
Frank McCormick composed on 2023-03-18 13:45 (UTC-0400):
OK. Now I understand. I have no idea how the dev package was installed from the graphics repository. User error I guess :)
Optional repos only get enabled because of your action of installing software you didn't find in standard repos. Typically this action ensues from using a 1-click installation from https://software.opensuse.org/search. Once enabled, optional repos produce risk of "upgrading" other software available from that repo. 1-clicks are best avoided. Once used, the repos they enable need to be disabled or removed, or at least their use closely monitored. To install software found via https://software.opensuse.org/search you can use the opi command to install with less resulting danger. Opi can also find software.
I've used OPI on a couple of occasions...the last one I recall was codecs from Packman. But normally I don't useit.
participants (4)
-
Andrei Borzenkov -
Felix Miata -
Frank McCormick -
Patrick Shanahan