WARNING! I've broken my database with simply upgrading from 8.0.8 to 8.0.9-r1!
This was due to having "pg-hier"-USE-flag defined, which patch and USE-flag was dropped for 8.0.9. If you have pg-hier set as USE flag you'll have to dump your database while still having 8.0.8, then emerge postgresql-8.0.9-r1 and restore your database from the dump! Christian Jason Stubbs schrieb: > On Saturday 16 December 2006 19:41, Ben Munat wrote: >> I have a script doing emerge --sync every night and I always update >> portage when I see there's an update. So I should have the latest stable. >> >> Just went and looked... I have portage-2.1.1-r2. >> >> What does this problem have to do with portage? > > On Saturday 16 December 2006 19:10, Ben Munat wrote: >> [blocks B ] <=dev-db/postgresql-8.0.8 (is blocking dev-db/libpq-8.0.9) >> [ebuild U ] dev-db/libpq-8.0.9 [8.0.8] USE="-pg-intdatetime% -threads%" >> [ebuild U ] dev-db/postgresql-8.0.9-r1 [8.0.8] USE="-test%" > > After both libpq and postgresql have been upgraded, the block from > libpq-8.0.9 > on <=postgresql-8.0.8 is no longer relevant. Recent versions of portage > reckognise this and ignore the block. However, it seems that this has not > made it to stable yet. > > 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). > > -- > Jason Stubbs -- [email protected] mailing list
