On 5 March 2017 at 12:18, Bruno Friedmann
On dimanche, 5 mars 2017 12.05:44 h CET 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?
I've seen some package behaving like this. As I'm updating my TW by hands when I know I have to do it, in yast2 single_sw, if I choose to remove python-YAML, then automa(gi)cally python2-YAML is selected ?
I've not been able to retrace the why ...
I'm pretty sure salt wants python3-YAML, but trying to hack things around manually just leads to more dependency quirks..would really appreiciate a python expert having a look at this specific issue with salt for me, I use it a lot and every single one of my TW systems are either unpatchable or unmanageable until we figure out what's wrong :) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org