Hello Sam, Sam Hartman [2010-09-13 9:02 -0400]: > I'd like to understand how bad the Postgres issue is. Is it necessary > to have both 8.3 and 8.4 co-configured in order for the upgrade to > work?
Yes, it is. The packages are versioned because there is no (solid) automatic upgrade path between major versions (i. e. X.Y), so you need the old version to do the upgrade to the new one. So the idea is that the old postgresql-8.3 package stays as it is from Lenny, and the metapackage pulls in the 8.4 one. There's a debconf note that explains that 8.3 is outdated and how to upgrade. So you can attempt the upgrade to 8.4 after the distro dist-upgrade is done, run both instances in parallel, and only wipe 8.3 once you are satisfied (if not, you can wipe 8.4 and try again). We tried an in-place upgrade with a lot of hacks (copy the old binaries and libraries to a temp dir until woody, but introduced the multi-version packaging in sarge. http://people.debian.org/~mpitt/architecture.html has some details in case you are interested. So right now, it seems that reintroducing a transitional libkrb5 metapackage to pull in the others is a rather safe and robust way, and it should also help apt & friends. What do you think? Thank you, 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
