In reply to @dilinger:queued.net
uhoreg: mind looking over my last libquotient commit on salsa before I upload to make sure you're happy with it?

In reply to @dilinger:queued.net
Yeah, I thought about that a bit. That's the standard way to do a dummy package so that you don't keep the old pre-rename version and the new version instaled in parallel, but you're right there's no files in common. The only scenario I could think of where it would be undesirable would be a developer trying to keep both installed in order to build older quaternion or something at the same time you're trying to build newer spectral, and I thought that was highly unlikely. So I stuck w/ the standard way.

In reply to @dilinger:queued.net
The only other thing I worried about was the 0.6 vs 0.6.4 ABI. I know upstream is trying not to break API with 0.6, but I'm not certain about ABI. In the end, knowing that 0.7 is just around the corner, I went with 0.6 because I figure there likely won't even be a 0.6.5

In reply to @hubert:uhoreg.ca
Yeah. The problem is that if you build a libqmatrixclient-dev package, then if someone tries to build older quaternion and has that package installed, it will fail because it doesn't provide the same files. And we couldn't have both libqmatrixclient and libquotient in sid at the same time since they both provide libqmatrixclient-dev. Which means that this will be a library transition, and library transitions are blocked now. So I think it's best to drop the libqmatrixclient-dev package from libquotient, and drop the breaks/conflicts.

In reply to @hubert:uhoreg.ca
I think upstream is pretty careful about keeping the ABI, so 0.6 should be fine.

In reply to @hubert:uhoreg.ca
Just noticed that libquotient isn't built with encryption enabled. I guess we need to package libqtolm for that to happen.

In reply to @hubert:uhoreg.ca
andrewsh: I don't know if you saw this: https://github.com/matrix-org/synapse/issues/9187 The next version of Synapse (1.26.0) will depend on psycopg2 >= 2.8, while buster only has 2.7.7. So you'll probably need to upload a new psycopg2 to backports before Synapse 1.26.0 goes into backports.

In reply to @hubert:uhoreg.ca
andrewsh: I don't know if you saw this: https://github.com/matrix-org/synapse/issues/9187 The next version of Synapse (1.26.0) will depend on psycopg2 >= 2.8, while buster only has 2.7.7. So you'll probably need to upload a new psycopg2 to backports before Synapse 1.26.0 goes into backports.

Debian 10 (buster) and Ubuntu 18.05 (bionic) do not provide a suitable version of psycopg2 in their own repositories

That is, however, an uncommon configuration.

reading that makes me angry

or the other way to put it:

users who rely on Python modules which are globally installed by their distribution's package manager.

That is, however, an uncommon configuration.