@GrahamcOfBorg eval

cc @Nadrieril

Ah well, that's sad :( But if it's broken and upstream is not working on Python3, then I guess we have no choice

Well there is the possibility of introducing older versions of those packages, so we're not choiceless, but not sure how good that choice would be.

This package was up for removal several times. @Nadrieril then took up maintainership and kept it working. If you're also willing to maintain the Python 2 packages it depends upon, I suppose it could stay (though Python2 may eventually get marked as insecure).

No, as much as I would like to, I don't have the bandwith to maintain a couple of outdated python libraries and all of their dependencies

Since it is probably relevant: What are you migrating to if you are no longer using the synserver module? I guess moving to the mozilla provided service is not an option as otherwise we would never have considered self-hosting?

Mozilla's new implementation could not be build yet a few months ago. There was one rust library not yet opensourced by google. This could be different now. Apart from that this would be the way to go in future.

I tried to make it build by rolling back a bunch of python module versions, but I hit #71824 that I have no clue how to fix. I'm ok with removing syncserver altogether, and waiting for the new rust implementation to be usable :(

@Nadrieril could we get the progress you made? I have also tried something and hit the webtest issue. But I'm willing to give a second shot at it.

What I did is I tried to build syncserver on the latest 20.03, and whenever there was a dependency issue I rolled back that dependency to a commit where syncserver used to build. After 4-5 deps I hit #71824, but not just in webtest. A few other packages had issues importing paste.deploy.
Sadly I did not keep this around but it shouldn't be too hard to get to the same state yourself

I marked this as stale due to inactivity. → More info

Too lazy to rebase this another time...