| 1 |
On Saturday 16 December 2006 19:41, Ben Munat wrote: |
| 2 |
> I have a script doing emerge --sync every night and I always update |
| 3 |
> portage when I see there's an update. So I should have the latest stable. |
| 4 |
> |
| 5 |
> Just went and looked... I have portage-2.1.1-r2. |
| 6 |
> |
| 7 |
> What does this problem have to do with portage? |
| 8 |
|
| 9 |
On Saturday 16 December 2006 19:10, Ben Munat wrote: |
| 10 |
> [blocks B ] <=dev-db/postgresql-8.0.8 (is blocking dev-db/libpq-8.0.9) |
| 11 |
> [ebuild U ] dev-db/libpq-8.0.9 [8.0.8] USE="-pg-intdatetime% -threads%" |
| 12 |
> [ebuild U ] dev-db/postgresql-8.0.9-r1 [8.0.8] USE="-test%" |
| 13 |
|
| 14 |
After both libpq and postgresql have been upgraded, the block from libpq-8.0.9 |
| 15 |
on <=postgresql-8.0.8 is no longer relevant. Recent versions of portage |
| 16 |
reckognise this and ignore the block. However, it seems that this has not |
| 17 |
made it to stable yet. |
| 18 |
|
| 19 |
Assuming that above two packages are all that're needed, you should be able to |
| 20 |
get it around it manually with the following commands. |
| 21 |
|
| 22 |
# emerge --oneshot --nodeps dev-db/libpq |
| 23 |
# emerge --oneshot dev-db/postgresql |
| 24 |
|
| 25 |
However, I wouldn't do it while the server is running in production (even if |
| 26 |
there was no block). |
| 27 |
|
| 28 |
-- |
| 29 |
Jason Stubbs |
| 30 |
-- |
| 31 |
gentoo-server@g.o mailing list |
Archives