| 1 |
Dale writes: |
| 2 |
|
| 3 |
> I'm no expert on this package so take this with a grain of salt. Mine |
| 4 |
> just updated and portage said to run "emerge @preserved-rebuild" which |
| 5 |
> I did. Thing is, one of the packages failed to emerge so here I sit. |
| 6 |
> The error says something is missing which is the same reason the |
| 7 |
> "emerge @preserved-rebuild" won't finish. |
| 8 |
> |
| 9 |
> So, looks like you need to rebuild some stuff but don't hold your |
| 10 |
> breath on being able to. There is a thread on the forums already if |
| 11 |
> you want to monitor it. |
| 12 |
|
| 13 |
I think it's not an urgent problem when this happens. With portage 2.2 and |
| 14 |
the preserve-libs FEATURE, old libraries are not deleted when an update |
| 15 |
installs new, incompatible library. This happens when emerge @preserved- |
| 16 |
rebuild has finished rebuilding all packages using the old library, so |
| 17 |
they now use the new one. |
| 18 |
|
| 19 |
Without this feature, the old library is deleted after the update, and you |
| 20 |
need to use revdep-rebuild to rebuild all the stuff that uses the no |
| 21 |
longer existing library. I always thought of this as a big problem with |
| 22 |
Gentoo, and it's great that it no lonoger is. |
| 23 |
|
| 24 |
Wonko |
Archives