Hi Am Sonntag, 5. März 2017, 16:26:41 CET schrieb Martin Pluskal:
On 05.03.2017 13:50, Martin Pluskal wrote:
On 05.03.2017 12:05, Richard Brown wrote:
When attempting to upgrade with dup --no-allow-vendor-change
Problem: salt-2016.3.4-1.1.x86_64 requires python-yaml, but this requirement cannot be provided
deleted providers: python-PyYAML-3.12-1.1.x86_64
Solution 1: Following actions will be done: deinstallation of salt-2016.3.4-1.1.x86_64 deinstallation of salt-zsh-completion-2016.3.4-1.1.noarch deinstallation of salt-minion-2016.3.4-1.1.x86_64
Solution 2: keep python-PyYAML-3.12-1.1.x86_64 Solution 3: break salt-2016.3.4-1.1.x86_64 by ignoring some of its dependencies>> Does salt need to be modified to work with the new singlespec paradigm?
It seems to be side effect of python singlespec effort - there is no python-PyYAML in Factory atm as it was replaced by python2-PyYAML
Cheers
M
There is sr [1] which might help.
What is however interesting is that python-yaml was last present in 12.1 yet salt is still requiring it.
python-yaml is still the name of the package in SLES11 and salt package was build for it. SLES11 is still maintained for several years. So please bring back the "Provides: python-yaml = %{version}" and all other old names these package(s) ever had. Thanks -- Regards Michael Calmer -------------------------------------------------------------------------- Michael Calmer SUSE LINUX GmbH, Maxfeldstr. 5, D-90409 Nuernberg T: +49 (0) 911 74053 0 F: +49 (0) 911 74053575 - e-mail: Michael.Calmer@suse.com -------------------------------------------------------------------------- SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org