<rjarry>
v58.0.0 Breaking Changes " Removed support for 2to3 during builds. "
<rjarry>
and Tempita 0.5.2 has use_2to3=True in setup.py
gmcdonald has joined #buildbot
<felixfontein>
ah, that's a good hint why something else (completely unrelated to this) started failing for me yesterday; the error message involved pip and something with 2to3 :)
<cmouse>
"
<cmouse>
#2769: Build now fails fast when use_2to3 is supplied.
<cmouse>
"
<cmouse>
=)
<rjarry>
we need to remove the dependency to sqlalchemy-migrate
<rjarry>
and use alembic instead
<rjarry>
I'm not sure there is another option
<rjarry>
tardyp, p12tic any thoughts about this?
<felixfontein>
cmouse: exactly ;)
<rjarry>
in the meantime, I have frozen setuptools<58
<p12tic>
rjarry: Could you please file a short bug report on github so that people see?
<rjarry>
sure
<p12tic>
I agree that move to alembic is the best solution
<rjarry>
it looks like I have no other choice but to fix it
<rjarry>
:)
<p12tic>
I think let's move to svg
<rjarry>
yes
<rjarry>
I had completely set this aside
<rjarry>
I'm looking for a migration guide: sqlalchemy-migrate -> alembic
<rjarry>
it does not look seamless
<rjarry>
unfortunately
<p12tic>
i've been thinking about alembic for a long time
<p12tic>
don't worry about it :) it's time to fix this, i've already started
<rjarry>
ah, that's good news !
<p12tic>
what makes sense to do in this case is to force user to be upgraded to the latest sqlalchemy-migrate version
<rjarry>
what do you mean ?
<p12tic>
then we know the state of the database, dump the sqlalchemy-migrate table, create what's needed for alembic and then can start upgrading alembic
<rjarry>
ah ok
<p12tic>
sqlalchemy-migrate version == the version of buildbot DB in sqlalchemy terms
<p12tic>
*sqlalchemy-migrate terms
<rjarry>
I'll take care of blockdiag removal first
<rjarry>
since this is trivial
bdbaddog has joined #buildbot
bdbaddog has quit [Quit: Leaving.]
tgamblin_ has quit [Quit: Leaving]
tgamblin has joined #buildbot
<rjarry>
p12tic: argl, CI fails because of tempita :)