Hi,
Upstream isn't fixing this in the next minor release of Salt, so it looks like
we won't be able to ship Salt 2018.3 in Debian any time soon (unless we switch
back to making it use Py2 temporarily).
I'm sorry to be bringing the bad news, and I would suggest waiting for the
Fluorine release:
-
tag 904654 + upstream fixed-upstream
forward 904654 https://github.com/saltstack/salt/issues/48556
tag 893817 - fixed-upstream
forward 893817 https://github.com/saltstack/salt-jenkins/issues/995
thanks
Hi,
Just updating the bugs metadata ;)
#904654 is fixed in upstream's 2018.3.3, to be
Hokay, so,
Both #893817 and #896921 fall into the category "Tornado 5
incompatibility". Thomas's #893817 is specifically a ZeroMQ/Tornado 5
incompatibility which has since been fixed, but doing so revealed my #896921.
To explain:
* February 10: ZeroMQ release pyzmq 17.0.0 to PyPI
* March 22:
severity 896921 grave
severity 893817 grave
forwarded 893817 https://github.com/saltstack/salt/issues/45790
forwarded 896921 https://github.com/saltstack/salt/issues/45790
tag 896921 + upstream fixed-upstream
tag 893817 + upstream fixed-upstream
thanks
Hi,
I'm upgrading the severity of those
Discussed upstream at https://github.com/saltstack/salt/issues/45790 -
the temporary fix from upstream is to mark salt incompatible with
tornado 5, so that the packages won't install to start with
https://github.com/saltstack/salt/pull/47106 is a pull request which
works on updating the code to
I am experiencing the same bug.
Hello,
I've got the same problem
Package: salt-minion
Version: 2017.7.4+dfsg1-1
Severity: important
Dear Maintainer,
I tried to (re)start salt-minion and got:
● salt-minion.service - The Salt Minion
Loaded: loaded (/lib/systemd/system/salt-minion.service; enabled; vendor
preset: enabled)
Active: failed (Result:
8 matches
Mail list logo
