Hi, On Mon, 2022-12-05 at 09:59 -0500, Brian Reichert wrote:
On Mon, Dec 05, 2022 at 10:50:24AM +0000, Srinidhi B wrote:
Hello List,
We are trying to replace a package in our product that provides the same functionality. We have made changes to our package as documented at - https://en.opensuse.org/openSUSE:Upgrade_dependencies_explanation - but when "zypper patch" command is run, we are receiving a vendor conflict. If we run "zypper patch --allow-vendor-change" then the package dependencies are handled correctly.
Both the vendor names are set to be equivalent.
Changing repositories will trigger this logic. An RPM can have an 'vendor' associated with it, but if that RPM is coming from a different repo than initially installed from, then it's deemed a vendor change.
I'm not too sure of the recent changes in libzypp, and zypper, but I have always had problems if the "vendor" tag actually changed - irrespective of the repository - and if the installed and new vendor are not considered equivalent. That is, if there is no entry for the new vendor in /etc/zypp/vendors.d/ directory.
Mind you, this is based on my own experience, as opposed to having a direct understanding of how zypper is designed to work.
Hence my question is, how can we handle the vendor conflict when replacing a package? Any insights here would be greatly appreciated.
Doesn't '--allow-vendor-change' allow you to do this? Perhaps I'm misunderstanding your question.
Yes, but neither our customers, users, or the existing software management tools (YaST, SUSE Manager, etc.) will pass this option by default. This is why, I'm trying to find an alternate solution that is "clean" and does not prompt the user for interaction. Regards, Srinidhi.