Hi Landry,
You can remove py-texscythe. I used to use it for generating Tex live plists, but no longer do.
The rest of your plan seems good to me too.
Thanks
31 Oct 2021 20:36:17 Landry Breuil <landry@openbsd.org>:
> Hi,
>
> long story short, i wanted to update buildbot to 3.4.0, which moved from
> sqlalchemy-migrate to alembic
> (https://github.com/buildbot/buildbot/issues/5872) so i started porting
> alembici (https://alembic.sqlalchemy.org), to find out our py-sqlalchemy
> was a bit dated (2+ years?).
>
> went on upgrading it to 1.4.26 (2.x claims only py3 support, but its not
> released yet), but after testing a bit it seems 1.4.26 doesnt really
> support py2 (default FLAVOR blows during fake for some py3-only async
> keywords ?) so i looked at what depends on sqlalchemy:
>
> databases/py-flask-sqlalchemy,python3
> databases/py-sqlalchemy-migrate,python3 (only used by buildbot, not much maintained, upstream advises to use alembic)
> devel/py-buildbot/buildbot (py3 only)
> devel/py-texscythe (used to generate PLISTs for texlive 2017 ??)
> games/childsplay (was removed)
> productivity/yokadi (py3 only)
>
> so, the 'easy' way is to just:
> - make sqlalchemy py3 only - almost all tests (but 5) of this new version passes
> - that allows to fold back -main and -docs (more or less reverting
> https://github.com/openbsd/ports/commit/156a9cbc117d47aa7353d91f392fa57cf308d798)
> - i think i got the pkgpath/conflict thing right, as running make update
> succeeds:
> py-sqlalchemy-1.2.19p2+py-sqlalchemy-docs-1.2.19p1+py3-sqlalchemy-1.2.19p2->py3-sqlalchemy-1.4.26: ok
> - drop py-texscythe (edd ? is this script still useful? needs porting to py3)
> - drop py-sqlalchemy-migrate ?
> - bump REVISION for all remaining ports depending on sqlalchemy (eg
> py-flask-sqlalchemy, buildbot, yokadi)
> - import alembic (tests: 1374 passed, 411 skipped in 86.65 seconds)
>
> feedback ? comments ?
>
> Landry
No comments:
Post a Comment