Opened 11 months ago

Last modified 11 months ago

#68832 assigned defect

py311-future: fails to install on M3 MacBook Pro (2023) Sonoma 14.1.2

Reported by: shigemiohta Owned by: petrrr
Priority: Normal Milestone:
Component: ports Version: 2.8.1
Keywords: Cc:
Port: py-future

Description (last modified by reneeotten (Renee Otten))

--->  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

Attachments (1)

macports_py311-future_main.log (225.8 KB) - added by shigemiohta 11 months ago.

Download all attachments as: .zip

Change History (3)

Changed 11 months ago by shigemiohta

comment:1 Changed 11 months ago by reneeotten (Renee Otten)

Description: modified (diff)
Port: py-future added
Summary: py311-future-0.18.2_0.darwin_any.noarch fails to install on M3 MacBook Pro (2023) Sonoma 14.1.2py311-future: fails to install on M3 MacBook Pro (2023) Sonoma 14.1.2

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 Migration?

comment:2 Changed 11 months ago by jmroot (Joshua Root)

Owner: set to petrrr
Status: newassigned
Note: See TracTickets for help on using tickets.