1 |
WARNING! |
2 |
I've broken my database with simply upgrading from 8.0.8 to 8.0.9-r1! |
3 |
|
4 |
This was due to having "pg-hier"-USE-flag defined, which patch and |
5 |
USE-flag was dropped for 8.0.9. |
6 |
If you have pg-hier set as USE flag you'll have to dump your database |
7 |
while still having 8.0.8, then emerge postgresql-8.0.9-r1 and restore |
8 |
your database from the dump! |
9 |
|
10 |
Christian |
11 |
|
12 |
|
13 |
Jason Stubbs schrieb: |
14 |
> On Saturday 16 December 2006 19:41, Ben Munat wrote: |
15 |
>> I have a script doing emerge --sync every night and I always update |
16 |
>> portage when I see there's an update. So I should have the latest stable. |
17 |
>> |
18 |
>> Just went and looked... I have portage-2.1.1-r2. |
19 |
>> |
20 |
>> What does this problem have to do with portage? |
21 |
> |
22 |
> On Saturday 16 December 2006 19:10, Ben Munat wrote: |
23 |
>> [blocks B ] <=dev-db/postgresql-8.0.8 (is blocking dev-db/libpq-8.0.9) |
24 |
>> [ebuild U ] dev-db/libpq-8.0.9 [8.0.8] USE="-pg-intdatetime% -threads%" |
25 |
>> [ebuild U ] dev-db/postgresql-8.0.9-r1 [8.0.8] USE="-test%" |
26 |
> |
27 |
> After both libpq and postgresql have been upgraded, the block from libpq-8.0.9 |
28 |
> on <=postgresql-8.0.8 is no longer relevant. Recent versions of portage |
29 |
> reckognise this and ignore the block. However, it seems that this has not |
30 |
> made it to stable yet. |
31 |
> |
32 |
> Assuming that above two packages are all that're needed, you should be able to |
33 |
> get it around it manually with the following commands. |
34 |
> |
35 |
> # emerge --oneshot --nodeps dev-db/libpq |
36 |
> # emerge --oneshot dev-db/postgresql |
37 |
> |
38 |
> However, I wouldn't do it while the server is running in production (even if |
39 |
> there was no block). |
40 |
> |
41 |
> -- |
42 |
> Jason Stubbs |
43 |
|
44 |
-- |
45 |
gentoo-server@g.o mailing list |