[MacPorts] #72215: curl-ca-bundle conflicts with certsync
MacPorts
noreply at macports.org
Wed Mar 19 11:31:22 UTC 2025
#72215: curl-ca-bundle conflicts with certsync
--------------------------+--------------------------------------
Reporter: barracuda156 | Owner: (none)
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.10.5
Keywords: | Port: certsync, curl-ca-bundle
--------------------------+--------------------------------------
{{{
---> Activating certsync @1.1.3_0
x ./
x ./+COMMENT
x ./+CONTENTS
x ./+DESC
x ./+PORTFILE
x ./+STATE
x ./Library/
x ./Library/LaunchDaemons/
x ./Library/LaunchDaemons/org.macports.certsync.plist
x ./opt/
x ./opt/local/
x ./opt/local/bin/
x ./opt/local/bin/update-ca-certificates
x ./opt/local/etc/
x ./opt/local/etc/LaunchDaemons/
x ./opt/local/etc/LaunchDaemons/org.macports.certsync/
x
./opt/local/etc/LaunchDaemons/org.macports.certsync/org.macports.certsync.plist
x ./opt/local/libexec/
x ./opt/local/libexec/certsync
x ./opt/local/share/
x ./opt/local/share/curl/
x ./opt/local/share/curl/curl-ca-bundle.crt
Error: Failed to activate certsync: The following ports have active files
that conflict with certsync's:
curl-ca-bundle @8.12.1_0
/opt/local/share/curl/curl-ca-bundle.crt
Image error: Conflicting file(s) present. Please deactivate the
conflicting port(s) first, or use 'port -f activate certsync' to force the
activation.
while executing
"throw registry::image-error $msg"
("foreach" body line 35)
invoked from within
"foreach file $imagefiles {
incr progress_step
_progress update $progress_step $progress_total_steps
se..."
invoked from within
"registry::write {
foreach file $imagefiles {
incr progress_step
_progress update $progress_step $progress_..."
Error: See
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_security_certsync/certsync/main.log
for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe
there
is a bug.
Error: Processing of port timescaledb failed
}}}
AFAICT, both ports are standard, not from my overlay, so the bug is in
MacPorts.
{{{
36-197:~ svacchanda\$ port file certsync
/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/security/certsync/Portfile
36-197:~ svacchanda\$ port file curl-ca-bundle
/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/net/curl/Portfile
}}}
--
Ticket URL: <https://trac.macports.org/ticket/72215>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list