Hi!
I have updated the Python Azure SDK for devel:languages:python:azure in a branch of my home project. Before submitting the updated packages to d:l:p:azure, I wanted to perform a test installation.
For some reason, zypper is now declaring packages from my home repository as not installable when I try to install the SDK:
suse-laptop:~ # zypper in python3-azure-sdk Loading repository data... Reading installed packages... Resolving package dependencies...
Problem: python3-azure-sdk-4.0.0-4.1.noarch requires python3-azure-batch >= 5.0.0, but this requirement cannot be provided not installable providers: python3-azure-batch-5.0.0-4.1.noarch[home_glaubitz_branches_devel_languages_python_azure] Solution 1: do not install python3-azure-sdk-4.0.0-4.1.noarch Solution 2: break python3-azure-sdk-4.0.0-4.1.noarch by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/c] (c):
If I add python3-azure-batch-5.0.0-4.1.noarch to the zypper command line, it will complain about the next package. And I assume, if I manually pass all the 100+ packages to the command line, zypper will finally install them.
Does anyone know how to resolve the issue "not installable providers"?
Adrian
John Paul Adrian Glaubitz wrote:
If I add python3-azure-batch-5.0.0-4.1.noarch to the zypper command line, it will complain about the next package. And I assume, if I manually pass all the 100+ packages to the command line, zypper will finally install them.
Does anyone know how to resolve the issue "not installable providers"?
Do you have repo priorities defined?
Do you have any of the packages installed already from a different repo? If so, use --allow-vendor-change
On 09/06/2018 05:56 PM, Peter Suetterlin wrote:
Does anyone know how to resolve the issue "not installable providers"?
Do you have repo priorities defined?
Yes, using the default priorities
Do you have any of the packages installed already from a different repo? If so, use --allow-vendor-change
This doesn't help either. That particular flag would have just the overriden the question by zypper asking for a vendor change. But that question is not coming anymore as it used to be in the past. zypper is outright claiming that the package is not installable and doesn't offer a vendor change.
Adrian
* John Paul Adrian Glaubitz adrian.glaubitz@suse.com [09-06-18 12:52]:
On 09/06/2018 05:56 PM, Peter Suetterlin wrote:
Does anyone know how to resolve the issue "not installable providers"?
Do you have repo priorities defined?
Yes, using the default priorities
Do you have any of the packages installed already from a different repo? If so, use --allow-vendor-change
This doesn't help either. That particular flag would have just the overriden the question by zypper asking for a vendor change. But that question is not coming anymore as it used to be in the past. zypper is outright claiming that the package is not installable and doesn't offer a vendor change.
zypper in --force -repo <YourRepo> package
On 09/06/2018 07:24 PM, Patrick Shanahan wrote:
zypper in --force -repo <YourRepo> package
Ok, there was one bogus Requires in one of the meta-packages I created which seems to have confused zypper. Works now.
Adrian
-
John Paul Adrian Glaubitz -
Patrick Shanahan -
Peter Suetterlin