Page MenuHomePhabricator

Find or create .deb package for mwclient 0.11.0 (or mwclient 0.10.0 with writeapi dependency removed)
Closed, ResolvedPublicBUG REPORT

Description

In "fun" news, the wmfkeystoneauth and Bitu usage of mwclient is via the python3-mwclient Debian package, so it looks like we will probably need to build and host a .deb for the updated library when it is available.

If we’re going to be reinstating the writeapi removal in production soon-ish, I would guess that other users of the Debian package would also want a fixed version of the library so they don’t get an error when talking to Wikimedia wikis? (Easier said than done, of course. And I don’t know how many third-party users the Debian package actually has – I couldn’t find any other packages depending on it, at least, though that might just be me operating apt wrong.)

Yes. I created https://bugs.debian.org/1078421 to track this on the Debian side and am planning to fix it there.

Both Bitu and the wmfkeystoneauth package from ops/puppet.git depend on an mwclient deb for communicating with MediaWiki instances. https://github.com/mwclient/mwclient/commit/cd4830a5d10ea452af73a2c098f92222b8145df8 is the upstream change needed to unblock/avoid being broken by T294397: Drop writeapi MediaWiki right.

Event Timeline

Restricted Application edited subscribers, added: Aklapper; removed: taavi. · View Herald Transcript

I've uploaded 0.11.0 to Debian unstable.

I'd also like to update the 0.10.0 package in stable to have a fix, so I wrote a minimal patch and built a ~wmf1 package for testing. Next we could install that at, say, the codfw1dev cloudcontrols and see if it works fine there, and if it does I could propose that for bookworm-proposed-updates to be included in the next point release.

Let's say that this is done. If there's need to get this updated more quickly we can do internal backports for the packages, but trixie is close enough that it might not be necessary.