Alpine 2.00_1+passfile+without_tcl fails to start after openldap upgrade

[bitmail@…]

Hello,

I use alpine once in a while, but recently I noticed that apparently an openldap update broke it. My system info: OSX 10.5.8 PPC, Macports 1.8.2 Alpine: alpine @2.00_1+passfile+without_tcl (active) Openldap: openldap @2.4.21_0 (active) Error message when starting alpine:

dyld: Library not loaded: /opt/local/lib/libldap-2.3.0.dylib
  Referenced from: /opt/local/bin/alpine
  Reason: image not found
Trace/BPT trap

List of libldap files present:

ls -al /opt/local/lib/libldap*
-rw-r--r--  2 root  admin  252452 Jan 22 17:24 /opt/local/lib/libldap-2.4.2.5.4.dylib
lrwxr-xr-x  1 root  admin      23 Jan 22 17:27 /opt/local/lib/libldap-2.4.2.dylib -> libldap-2.4.2.5.4.dylib
-rw-r--r--  2 root  admin  478712 Jan 22 17:24 /opt/local/lib/libldap.a
lrwxr-xr-x  1 root  admin      23 Jan 22 17:27 /opt/local/lib/libldap.dylib -> libldap-2.4.2.5.4.dylib
-rw-r--r--  2 root  admin     952 Jan 22 17:24 /opt/local/lib/libldap.la
-rw-r--r--  2 root  admin  275848 Jan 22 17:24 /opt/local/lib/libldap_r-2.4.2.5.4.dylib
lrwxr-xr-x  1 root  admin      25 Jan 22 17:27 /opt/local/lib/libldap_r-2.4.2.dylib -> libldap_r-2.4.2.5.4.dylib
-rw-r--r--  2 root  admin  528256 Jan 22 17:25 /opt/local/lib/libldap_r.a
lrwxr-xr-x  1 root  admin      25 Jan 22 17:27 /opt/local/lib/libldap_r.dylib -> libldap_r-2.4.2.5.4.dylib
-rw-r--r--  2 root  admin     966 Jan 22 17:24 /opt/local/lib/libldap_r.la

[todmorrison (Tod Morrison)]

My guess is that you have upgraded openldap since the last time you built alpine. Try rebuilding alpine with:

port -vn upgrade --force alpine

and see if that doesn't solve the problem.

[bitmail@…]

Replying to todmorrison@…:

My guess is that you have upgraded openldap since the last time you built alpine. Try rebuilding alpine with:

port -vn upgrade --force alpine

and see if that doesn't solve the problem.

Well,

I thought so too. Fortunately rebuilding like you suggested worked, alpine is working fine. I was just surprised that ports don't get automatically rebuild, if dependents are upgraded. Or do I need to add some options while doing an upgrade, atm I'm using

sudo port -u -p upgrade outdated

Thanks anyway!

[todmorrison (Tod Morrison)]

Unfortunately it does not automatically rebuild dependents, and having it do so could cause more problems than it solves. Probably, what we need is something like Gentoo's "revdep-rebuild" (​http://www.gentoo.org/doc/en/gentoolkit.xml).[[BR]]
As it is, though, I guess this ticket should be marked close

[bitmail@…]

Replying to todmorrison@…:

Unfortunately it does not automatically rebuild dependents, and having it do so could cause more problems than it solves. Probably, what we need is something like Gentoo's "revdep-rebuild" (​http://www.gentoo.org/doc/en/gentoolkit.xml).[[BR]]

After having a short glance at the details provided about the ​gentoolkit, I have to say that this looks really good. And the "revdep-rebuild" would indeed suited this situation perfect:

It will scan your installed ebuilds to find packages that have become broken as a result of an upgrade of a package they depend on. It can emerge those packages for you but it can also happen that a given package does not work anymore with the currently installed dependencies, in which case you should upgrade the broken package to a more recent version.

Tempting!