[MacPorts] #70335: x86_64-dragonfly-binutils @2.41_0 conflicts with x86_64-binutils @2.41_0

MacPorts noreply at macports.org
Sat Jul 6 20:37:26 UTC 2024


#70335: x86_64-dragonfly-binutils @2.41_0 conflicts with x86_64-binutils @2.41_0
-------------------------+-------------------------------------------------
 Reporter:  cooljeanius  |      Owner:  (none)
     Type:  defect       |     Status:  new
 Priority:  Normal       |  Milestone:
Component:  ports        |    Version:  2.9.3
 Keywords:               |       Port:  x86_64-binutils x86_64-dragonfly-
                         |  binutils
-------------------------+-------------------------------------------------
 They both try to install the same license file:
 {{{
 x ./opt/local/bin/x86_64-dragonfly-size
 Error: Failed to activate x86_64-dragonfly-binutils: Image error:
 /opt/local/share/doc/x86_64-binutils/COPYING is being used by the active
 x86_64-binutils port.  Please deactivate this port first, or use 'port -f
 activate x86_64-dragonfly-binutils' to force the activation.
     while executing
 "throw registry::image-error $msg"
     ("foreach" body line 47)
     invoked from within
 "foreach file $imagefiles {
                 set srcfile "${extracted_dir}${file}"

                 # To be able to install links, we test if we can lst..."
     invoked from within
 "registry::write {
             foreach file $imagefiles {
                 set srcfile "${extracted_dir}${file}"

                 # To be able to instal..."
 DEBUG: Error code: registry::image-error
 DEBUG: Backtrace: Image error:
 /opt/local/share/doc/x86_64-binutils/COPYING is being used by the active
 x86_64-binutils port.  Please deactivate this port first, or use 'port -f
 activate x86_64-dragonfly-binutils' to force the activation.
     while executing
 "throw registry::image-error $msg"
     ("foreach" body line 47)
     invoked from within
 "foreach file $imagefiles {
                 set srcfile "${extracted_dir}${file}"

                 # To be able to install links, we test if we can lst..."
     invoked from within
 "registry::write {
             foreach file $imagefiles {
                 set srcfile "${extracted_dir}${file}"

                 # To be able to instal..."
     while executing
 "throw [dict get $eOptions -errorcode] [dict get $eOptions -errorinfo]"
     (procedure "_activate_contents" line 200)
     invoked from within
 "_activate_contents $requested $rename_list"
     (procedure "portimage::activate" line 70)
     invoked from within
 "registry_activate $subport $_inregistry_version $_inregistry_revision
 $_inregistry_variants $optionlist"
     (procedure "portactivate::activate_main" line 20)
     invoked from within
 "$procedure $targetname"
 DEBUG: dropping privileges: euid changed to 502, egid changed to 20.
 }}}
 This seems to be a common issue with a lot of the cross-binutils ports;
 each one should probably have its own separate docdir.

-- 
Ticket URL: <https://trac.macports.org/ticket/70335>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list