[MacPorts] #68832: py311-future: fails to install on M3 MacBook Pro (2023) Sonoma 14.1.2 (was: py311-future-0.18.2_0.darwin_any.noarch fails to install on M3 MacBook Pro (2023) Sonoma 14.1.2)

MacPorts noreply at macports.org
Mon Dec 4 02:44:27 UTC 2023


#68832: py311-future: fails to install on M3 MacBook Pro (2023) Sonoma 14.1.2
--------------------------+--------------------
  Reporter:  shigemiohta  |      Owner:  (none)
      Type:  defect       |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:  2.8.1
Resolution:               |   Keywords:
      Port:  py-future    |
--------------------------+--------------------
Changes (by reneeotten):

 * port:   => py-future


Old description:

> {{{--->  Attempting to fetch
> py311-future-0.18.2_0.darwin_any.noarch.tbz2.rmd160 from
> https://kmq.jp.packages.macports.org/py311-future
> --->  Installing py311-future @0.18.2_0
> --->  Activating py311-future @0.18.2_0
> Error: Failed to activate py311-future: Image error:
> /opt/local/Library/Frameworks/Python.framework/Versions/3.11/bin/futurize
> already exists and does not belong to a registered port.  Unable to
> activate port py311-future. Use 'port -f activate py311-future' to force
> the activation.
>     while executing
> "throw registry::image-error $msg"
>     ("foreach" body line 50)
>     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..."
> Error: See
> /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports
> .org_macports_release_tarballs_ports_python_py-
> future/py311-future/main.log for details.
> Error: Follow https://guide.macports.org/#project.tickets if you believe
> there
> is a bug.
> Error: Processing of port py-lmfit failed
> }}}

New description:

 {{{
 --->  Attempting to fetch
 py311-future-0.18.2_0.darwin_any.noarch.tbz2.rmd160 from
 https://kmq.jp.packages.macports.org/py311-future
 --->  Installing py311-future @0.18.2_0
 --->  Activating py311-future @0.18.2_0
 Error: Failed to activate py311-future: Image error:
 /opt/local/Library/Frameworks/Python.framework/Versions/3.11/bin/futurize
 already exists and does not belong to a registered port.  Unable to
 activate port py311-future. Use 'port -f activate py311-future' to force
 the activation.
     while executing
 "throw registry::image-error $msg"
     ("foreach" body line 50)
     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..."
 Error: See
 /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports
 .org_macports_release_tarballs_ports_python_py-
 future/py311-future/main.log for details.
 Error: Follow https://guide.macports.org/#project.tickets if you believe
 there
 is a bug.
 Error: Processing of port py-lmfit failed
 }}}

--

Comment:

 That shouldn't happen... unless you have tried to install ports with
 {{{pip}}} or other ways into the MacPorts prefix, which we strongly
 recommend against.

 Just to make sure, is this on a clean macOS Sonoma installation or did you
 do an upgrade? If the latter, did you follow the instructions listed in
 [wiki:Migration]?

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


More information about the macports-tickets mailing list