On Mon, Sep 02, 2024 at 07:15:44PM +0200, Alexandre Detiste wrote: > Le lun. 2 sept. 2024 à 18:56, Colin Watson <cjwat...@debian.org> a écrit : > > On Thu, Jul 18, 2024 at 02:08:32PM +0200, Hans-Christoph Steiner wrote: > > > It is fixed upstream: > > > https://github.com/buildbot/buildbot/commit/291df50dc3f27adb47a001fc154cf4c55490687e > > > > Thanks. > > And then I noticed that Alexandre committed a new upstream release to > > the repository two months ago, but didn't upload it, and it's in this > > broken state so I don't know what to do with it. Alexandre, can you > > comment, and ideally fix it up? > > I was stuck really hard trying to make it work with SQLAlchemy 2.x > and dropped the ball. > > I refreshed the patches. I now guess you may want to remove > debian/patches/sqlalchemy2.0 really soon. The package is yours.
Thanks. I figured out a workable set of upstream patches to backport on top of 4.0.2 (it was rather more than the one patch above - it ended up being an 11-patch sequence for SQLAlchemy 2.0) and pushed that: https://salsa.debian.org/python-team/packages/buildbot/-/commit/85a3a35f865359c1f4c490e845469380202e7cfb Yes, one of the patches mostly reverts one of the others. But it was easier to keep track of things if I minimized how much editing I needed to do of the upstream patches. Do you want to review any of this, or shall I just go ahead and upload, maybe after dropping transitional packages per the four open bugs about that? Cheers, -- Colin Watson (he/him) [cjwat...@debian.org]
