Jason Stubbs wrote: > Assuming that above two packages are all that're needed, you should be able > to > get it around it manually with the following commands. > > # emerge --oneshot --nodeps dev-db/libpq > # emerge --oneshot dev-db/postgresql > > However, I wouldn't do it while the server is running in production (even if > there was no block).
The upgrade should actually be possible with PostgreSQL running, as the blockers are there only to catch a little collision-protect problem (a binary was moved from postgresql to libpq) and to warn about the pg-hier USE flag disappearance. Pasting from a forums thread: "Well, the blocker was added for the simple reason of file-collisions. With the new libpq/postgresql versions we've moved a file from the postgresql package to the libpq package. Now, you have to emerge libpq BEFORE postgresql, so when Portage was installing libpq it would bail out with a "file collision found, blabla" error. The only way we have of notifying the user of this is by adding a blocker. The easiest and most correct way to upgrade would be this: Code: FEATURES="-collision-protect" emerge --nodeps libpq emerge postgresql The first one basically emerge libpq without checking for blockers and disables the file-collision check, so that the new libpq will install correctly, and then you can normally upgrade postgresql itself (which you MUST do, both really *must* be upgraded!). " That should work and update your PostgreSQL install correctly. -- Best regards, Luca Longinotti aka CHTEKK LongiTEKK Networks Admin: [EMAIL PROTECTED] Gentoo Dev: [EMAIL PROTECTED] SysCP Dev: [EMAIL PROTECTED] TILUG Supporter: [EMAIL PROTECTED]
signature.asc
Description: OpenPGP digital signature
