[opensuse-packaging] Salt wants to be removed due to missing python-PyYAML
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? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
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 ... -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
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
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
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. Cheers M 1. https://build.opensuse.org/request/show/471398
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
On 05.03.2017 17:01, Michael Calmer wrote:
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. Hello
it would be nice if you would have looked at link I sent before replying - https://build.opensuse.org/request/show/471398 where " Provides: python-yaml = %{version}" is being brought back again. Also I wonder what extra effort is needed to maintain backwards compatibility for SLE-11 and who is going to provide needed resources for such effort. Cheers Martin
On Sun, Mar 5, 2017 at 6:05 AM, Richard Brown
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?
The issue is "Requires: python-yaml". That was a legacy extra provides that disappeared when singlespec went into python-PyYAML. For one of my packages Dimstar had me do: -Requires: python-yaml +Requires: python-PyYAML Greg -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (5)
-
Bruno Friedmann -
Greg Freemyer -
Martin Pluskal -
Michael Calmer -
Richard Brown