some problems after upgrading to 7.0-RELEASE

Novembre novembre at gmail.com
Sun Mar 23 16:18:39 PDT 2008


On Thu, Mar 20, 2008 at 10:34 PM, Peter Boosten <peter at boosten.org> wrote:
>
>
>  Novembre wrote:
>  >
>  > Anyhow, smbd was looking for libgnutls.so.13 which I don't have, but I
>  > do have a libgnutls.so.26 and libgnutls.so in /usr/local/lib/ (the
>  > latter is a symlink to the former). Also, libgnutls.so.15 exists in
>  > /usr/local/lib/compat/pkg/. So what I did was creating a symlink to
>  > libgnutls.so.26 and called it libgnutls.so.13, and after rebooting,
>  > smbd starts just fine. I don't know whether I'm allowed to do such a
>  > thing or not, but since I didn't get any error message while upgrading
>  > samba, I don't know what could have gone wrong...
>  >
>  > Any ideas? :)
>  >
>
>  You probably missed this one (from UPDATING):
>
>  20080303:
>    AFFECTS: users of security/gnutls and any port that depends on it
>    AUTHOR: novel at FreeBSD.org
>
>    gnutls has been updated to 2.2.2 and all shared libraries' versions
>    have been bumped. So you need to rebuild all applications that
>    depend on gnutls. Do something like:
>
>          portupgrade -rf gnutls
>
>  Peter
>
>  --
>  http://www.boosten.org
>


I did a " portupgrade -rf gnutls " and it compiled a lot of the ports
and finally fixed the problem. However, I'm wondering why the release
notes suggest doing a " portupgrade -faP " if it's not going to
upgrade the installed ports in the correct way?

Thanks anyway :)


More information about the freebsd-questions mailing list