Hi @marc,
I’ve seen it reported at least once before, but unless someone wants to come up with a PR for it, we’re unlikely to devote dev time to a fix; the 2.x to 3.x upgrade process has long been retired (and isn’t in any of our maintained branches). I know there are still folks out there using it – and I really encourage them to upgrade soon!
Regards,
Alec Smecher
Public Knowledge Project Team