Hey Christoph, Christoph Berg [2014-08-10 23:28 +0200]: > Anyway, I used the opportunity to dig through > https://wiki.ubuntu.com/MultiarchSpec again, and I believe I found a > set of packages that we can mark "Multi-Arch: foreign" without > breaking anything. There's even a picture about it: > > https://alioth.debian.org/scm/loggerhead/pkg-postgresql/postgresql-common/trunk/download/head:/dependencies.png-20140810210718-qrxnqfvfo0ha0zcu-3/dependencies.png > > Martin, could you check if that makes sense?
As for the CLI programs (and surely for the -docs) your changes look ok to me. As long as you only have -client installed to talk to remote DBs, the M-A: same for libpq5 will ensure that the correct ABI <-> protocol will be used. If you try cross-grades like Torsten: The server is currently not M-A, i. e. you can only have one architecture installed at a time. Then you would have e. g. an i386 "psql" client program talking to an amd64/x32/etc. server. The client side doesn't access the on-disk files but only talk the "wire format" through libpq5 it's at least a plausible expecation that this actually works. I tested this shallowly with a simple DB and server amd64 plus -client i386 (with some dpkg --force-all hammer), and it seems to work fine in that simple case at least. > I thought about "Multi-Arch: allowed" for "postgresql", but refrained > because I didn't want to invoke too much magic at once. Agreed. Multi-Arch'ing the server sounds like a huge and complex task, and I don't think it's worth the trouble. Thanks for fixing this! Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: Digital signature
_______________________________________________ Pkg-postgresql-public mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
