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:
- switching back and forth between py2 and py3 would likely break things,
- the ones who absolutely need Salt in buster or sid are likely using the
vendor's repository (as Salt has been broken in Debian for ~half a year)
Of course, as I'm not in the Salt team, my opinion should likely be taken
with... a grain of salt ;)
Best,
nicoo
----- Forwarded message from Daniel Wallace <notificati...@github.com> -----
Date: Tue, 28 Aug 2018 05:46:22 -0700
From: Daniel Wallace <notificati...@github.com>
To: saltstack/salt-jenkins <salt-jenk...@noreply.github.com>
Cc: Nicolas Braud-Santoni <nico...@braud-santoni.eu>, Comment
<comm...@noreply.github.com>
Subject: Re: [saltstack/salt-jenkins] [Py3][Tornado 5.0] IOLoop tests failing
with asyncio
(#995)
This is not going to be fixed in 2018.3.3, you will have to stick with salt
with python2 for versions where python-tornado is already upgraded.
This is will be fixed in Fluorine for python3 and if it is not too complicated
it may be backported to 2018.3 once it has finished, but it is not holding up
the 2018.3.3 release.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/saltstack/salt-jenkins/issues/995#issuecomment-416570266
----- End forwarded message -----
signature.asc
Description: PGP signature
