Thanks very much for that. I'm not sure what I could have done differently, though. I grabbed my packages and the snapshot all within an hour or two earlier today from the same mirror. So I don't think it was a terribly unreasonable assumption on my part that they were mutually compatible. Is there any way to know that the snapshot and packages are out-of-sync so I can avoid any problems like this in the future? I did notice that they were two days apart, but didn't know whether that ipso facto meant there was a problem.
I read the FAQ on this topic (5.1) and it is understandably vague on this point, but is it possible to determine when the next snapshot will be released? If tomorrow, I will wait. If not, then I will just go ahead and re-build the system from source. Thank you again for your response. On Sat, Jun 22, 2013 at 8:33 PM, Amit Kulkarni <amitk...@gmail.com> wrote: > > >> Can't install imap-uw-2.03p3v0 because of libraries >> |library heimntlm.0.0 not found >> | not found anywhere >> |library hx509.0.0 not found >> | not found anywhere >> Direct dependencies for imap-uw-2.03p3v0 resolve to libiconv-1.14p0 >> gettext-0.18.2p2 >> Full dependency tree is libiconv-1.14p0 gettext-0.18.2p2 >> # >> >> > > This shows that the package was compiled with old kerberos support. > > > >> ===> Verifying specs: asn1 c crypto gssapi krb5 ncurses ssl com_err >> heimbase roken wind intl>=5 iconv>=6 asn1 c crypto gssapi krb5 ncurses ssl >> com_err heimbase roken wind intl>=5 iconv>=6 com_err crypto pthread ssl >> asn1 c crypto gssapi krb5 ncurses ssl com_err heimbase roken wind intl>=5 >> iconv>=6 com_err crypto ssl asn1 c crypto gssapi krb5 ncurses ssl com_err >> heimbase roken wind intl>=5 iconv>=6 com_err crypto ssl asn1 c crypto >> gssapi krb5 ncurses ssl com_err heimbase roken wind intl>=5 iconv>=6 >> pthread asn1 c crypto gssapi krb5 ncurses ssl com_err heimbase roken wind >> intl>=5 iconv>=6 pthread >> ===> found asn1.19.0 c.68.4 crypto.22.0 gssapi.6.0 krb5.19.0 ncurses.12.1 >> ssl.19.0 com_err.19.0 heimbase.0.0 roken.0.0 wind.0.0 intl.6.0 iconv.6.0 >> pthread.17.3 >> > > heimbase com_err etc... this shows that you are trying to use old userland > and mixing it with current ports. solution is to wait for newer snaps or > compile kernel/userland/xenocara and then try to compile the port yourself. >
