[MacPorts] #72215: curl-ca-bundle conflicts with certsync

MacPorts noreply at macports.org
Thu Mar 20 04:25:04 UTC 2025


#72215: curl-ca-bundle conflicts with certsync
-------------------------------------------------+-------------------------
  Reporter:  barracuda156                        |      Owner:  dgilman
      Type:  defect                              |     Status:  assigned
  Priority:  Normal                              |  Milestone:
 Component:  ports                               |    Version:  2.10.5
Resolution:                                      |   Keywords:
      Port:  certsync, curl-ca-bundle,           |
  postgresql17                                   |
-------------------------------------------------+-------------------------

Comment (by ryandesign):

 It should not have been possible to get to the activation failure message
 that was reported. MacPorts base should have detected the conflict
 earlier, before the installation took place, and alerted the user of the
 conflict. The fact that this didn't happen suggests a bug in MacPorts
 base, possibly in the scenario David described, where neither curl-ca-
 bundle nor certsync was installed beforehand, and a user attempted to
 install postgresql16 or postgresql17. MacPorts base presumably walked the
 dependency tree and, since at that time ${prefix}/share/curl/curl-ca-
 bundle.crt was not present on disk, it added the default port to the list
 of dependencies to install.

 The MacPorts base bug should be fixed. But also, all ports that depend on
 curl-ca-bundle or certsync, except postgresql16 and postgresql17, depend
 on curl-ca-bundle:

 {{{
 % port -qv deps depends:':(curl-ca-bundle|certsync)\y' | grep -Eo '([^:
 ]+:)+(curl-ca-bundle|certsync)\b' | sort | uniq -c
    1 path:etc/openssl/cert.pem:curl-ca-bundle
    2 path:share/curl/curl-ca-bundle.crt:certsync
   15 path:share/curl/curl-ca-bundle.crt:curl-ca-bundle
 % port echo depends:path:share/curl/curl-ca-bundle.crt:certsync
 postgresql16
 postgresql17
 }}}

 Therefore yes, it would also be a good idea to change postgresql16 and
 postgresql17 to match the other ports and to avoid the base bug.

-- 
Ticket URL: <https://trac.macports.org/ticket/72215#comment:9>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list