[MacPorts] #23544: curl-ca-bundle: can't activate

[MacPorts]

#23544: curl-ca-bundle: can't activate
----------------------------------+-----------------------------------------
  Reporter:  cozimlate@…          |       Owner:  ryandesign@…           
      Type:  defect               |      Status:  closed                 
  Priority:  Normal               |   Milestone:                         
 Component:  ports                |     Version:  1.8.2                  
Resolution:  invalid              |    Keywords:                         
      Port:  curl-ca-bundle       |  
----------------------------------+-----------------------------------------

Comment(by ryandesign@…):

 Replying to [comment:7 cozimlate@…]:
 > It worked for cyrus-sasl2. [[br]]
 > I applied the same recipe to all dependencies that gave me
 problems:libogg @1.1.4_0, flac @1.2.1_0+darwin_i386, mysql5-devel, taglib
 @1.6.1_1. to name a few,
 > after removing any file that did not belong in a registered port [...]
 All dependenties are installed

 It remains to understand why you had all those conflicting files on your
 system. That should not have been the case. One possible explanation for
 this is if you had MacPorts installed before, uninstalled the part of
 MacPorts that kept track of what was installed where, but did not actually
 uninstall the software installed by MacPorts, then reinstalled MacPorts.
 As a result, there may yet be other files in your MacPorts prefix that are
 not registered to an installed port. It may be cleanest to
 [http://guide.macports.org/chunked/installing.macports.uninstalling.html
 uninstall MacPorts properly], then reinstall the ports you want. If you
 decide that's too much work right now, be aware you may continue to run
 into the situation of conflicting files when installing other ports, and
 if so, it's not a bug you need to report, but a problem in your
 installation.

 > but amarok wont build, stop at 34%, added the debug version in third
 attachment.

 This is #23617.

 Let's leave this ticket now since it is closed as invalid. If you have
 further difficulties, please search the issue tracker for existing issues
 that match your situation, file a new ticket if you believe there is a
 specific bug in a specific port, or ask on the
 [http://lists.macosforge.org/mailman/listinfo.cgi/macports-users macports-
 users mailing list] if you need help.

-- 
Ticket URL: <http://trac.macports.org/ticket/23544#comment:9>
MacPorts <http://www.macports.org/>
Ports system for Mac OS