Peter Eisentraut [2014-10-11 17:48 -0400]: > I think the mistake here was to upload postgresql-9.4 into unstable > before it was released.
I agree. We should have kept it in experimental until the release candidate and prepare the extensions there, like in earlier releases. This is a rather awkward position for upgraders to be in, as we essentially cannot automate this robustly. This is exactly the reason why we introduced the p-common infrastructure more than a decade ago, as trying to do the dumping/restoring in maintainer scripts led to an eternal stream of upgrade failures and some data loss. But pg_upgradecluster can't help us with this situation, as we cannot install beta 2 and 3 in parallel. So I think the best we can do here is to document how to do the upgrade, and then not repeat the premature release of betas to unstable? Thanks, Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
