Re: Having a problem with security/libassuan-1 when compiling gnupg.

> Date: Thu, 17 Jun 2010 13:00:42 -0500
> From: eculp <eculp_at_encontacto.net>
> 
> Quoting Kevin Oberman <oberman_at_es.net>:
> 
> >> Date: Thu, 17 Jun 2010 12:03:48 -0500
> >> From: eculp <eculp_at_encontacto.net>
> >> Sender: owner-freebsd-current_at_freebsd.org
> >>
> >> Having a problem with security/libassuan-1 when compiling gnupg.  I
> >> did the upgrade to libassuan-2.0.0 following the instructions in
> >> UPDATING and this is the first problem that I have seen.
> >>
> >> ===>   gnupg-2.0.14_3 depends on package: libassuan-1>=1.0.5 - not found
> >> ===>    Verifying install for libassuan-1>=1.0.5 in
> >> /usr/ports/security/libassua
> >> n-1
> >>
> >> ===>  libassuan-1-1.0.5 conflicts with installed package(s):
> >>        libassuan-2.0.0
> >>
> >>        They install files into the same place.
> >>        Please remove them first with pkg_delete(1).
> >> *** Error code 1
> >>
> >> Stop in /usr/ports/security/libassuan-1.
> >> *** Error code 1
> >>
> >> Stop in /usr/ports/security/gnupg.
> >>
> >> ===>>> make failed for security/gnupg
> >> ===>>> Aborting update
> >>
> >> Any suggestions will be appreciated.
> >
> > Sorry. Just re-read the message.
> >
> > Since you already have libassuan-2.0.0 installed, you will probably need
> > to:
> > pkg_delete -f libassuan-2.0.0
> > portinstall libassuan-1
> > or
> > portmaster security/libassuan-1
> 
> 
> Thanks a lot, Kevin.  It is now working fin as far as I can tell.  I  
> was confused as to which was the prefered version for Current and was  
> sure that I had seen somewhere that is was 2.x but was probably  
> confused with another port.

2.0.0 should be the preferred version, but its API is incompatible with
the old one. Many ports using libassuan (listed in UPDATING) have not
been updated to support V2, so the libassuan-1 port was created. 

As soon as deskutils/kdepim4 and security/{dirmngr|gnupg|gpa|opensc} are
updated, there will be a need to move to 2.0.0. I am unsure what happens
when some ports want v1 and others want v2. This may not be an issue if
the updated ports can be deal with either API, but I have no idea
whether that is the case.
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman_at_es.net			Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4  EADA 927D EBB3 987B 3751