| 1 |
Hi, |
| 2 |
|
| 3 |
Here's a problem I've seen twice now. I'm not sure if it's a problem |
| 4 |
with the ebuilds (although I can't see anything special in them) or in |
| 5 |
the ebuild system, so I thought I'd ask here before posting in bugzilla |
| 6 |
about it. |
| 7 |
|
| 8 |
In two cases, once when upgrading gtkhtml and once when upgrading gimp, |
| 9 |
the new version has had a new so-name for a library. For example, |
| 10 |
libgimpbase went from .so.13 to .so.14. When I upgraded, the compile |
| 11 |
linked against the old version, not the version being created by the new |
| 12 |
ebuild. So, naturally, when emerge finished by removing the older |
| 13 |
version, it left an unresolved link in the binary. |
| 14 |
|
| 15 |
I'm using portage-2.0.47-r10, if that's relevant |
| 16 |
|
| 17 |
|
| 18 |
-- |
| 19 |
gentoo-dev@g.o mailing list |
Archives