- Use zypper instead of yum

[sbernhard]

Use zypper library instead of yum on SUSE based distributions.
The zypper library transactions are running within a separate process as the zypper application would otherwise be blocked as long as the gofer process is running. Looks like that this is a issue in zypper / python swig implementation. Answer from zypper development mailing list:

Older libzypp versions are not able to drop the lock at runtime.
(and they also don't have 'zypp.ZYppFactory_instance().haveZYpp()'
to test whether the instance is present.)

On older distros you need to run zypp in a separate process,
so libzypp gets unloaded and releases the lock.

[pulpbot]

Can one of the admins verify this patch?

[pulpbot]

Can one of the admins verify this patch?

[sbernhard]

This PR does replace #1041 Sorry for that
It does fix https://pulp.plan.io/issues/2996

I guess, I have answered all questions with this PR. Please let me know.

[sbernhard]

Any update on this?

[sbernhard]

Update?

[dkliban]

Thank you for the PR! I am not a core developer on the RPM plugin, but I am interested in this PR.

The biggest obstacle for me to test this is getting a SUSE system provisioned. However, I believe I have found a volunteer to help me test this PR.

[bmbouter]

@sbernhard Sorry for the long delay. We don't have a good way to test this, but we think it's ok to merge because:

a) reading the code shows the patch is low risk to existing functionality
b) We can run pulp-smash afterwards and it will tell us if we regress. If so we can negative commit until it's resolved.