Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#63258 closed defect (fixed)

usd @20.05_2+docs+examples+ptex+python+tutorials conflicts with spidermonkey @1.7.0_8

Reported by: cooljeanius (Eric Gallager) Owned by: Jason Liu <jasonliu--@…>
Priority: Normal Milestone:
Component: ports Version: 2.7.1
Keywords: Cc: jasonliu-- (Jason Liu)
Port: usd, spidermonkey

Description

They both try to install a libjs.dylib library:

x ./opt/local/bin/usdzip
Error: Failed to activate usd: Image error: /opt/local/lib/libjs.dylib is being used by the active spidermonkey port.  Please deactivate this port first, or use 'port -f activate usd' to force the activation.
DEBUG: Error code: registry::image-error
DEBUG: Backtrace: Image error: /opt/local/lib/libjs.dylib is being used by the active spidermonkey port.  Please deactivate this port first, or use 'port -f activate usd' to force the activation.
    invoked from within
"throw registry::image-error "Image error: $file is being used by the active [$owner name] port.  Please deactivate this port first, or use 'port -f ac..."
    ("foreach" body line 45)
    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..."
    invoked from within
"try {
        registry::write {
            foreach file $imagefiles {
                set srcfile "${extracted_dir}${file}"

                # To be ..."
    (procedure "_activate_contents" line 21)
    invoked from within
"_activate_contents $requested $rename_list"
    (procedure "portimage::activate" line 63)
    invoked from within
"registry_activate $subport $_inregistry_version $_inregistry_revision $_inregistry_variants $optionlist"
    (procedure "portactivate::activate_main" line 20)
    invoked from within
"$procedure $targetname"
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_usd/usd/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.
Error: Processing of port blender failed

This conflict should either be marked, or fixed. (Note that being unable to install usd blocks installation of blender for me)

Change History (5)

comment:1 Changed 3 years ago by jasonliu-- (Jason Liu)

I'll do some investigating to see whether the versions of libjs are different between USD and spidermonkey. If it turns out that the versions of libjs are the same, then I'll see whether I can add a check during the destroot phase to first try to detect whether libjs.dylib already exists, and if so, have USD prevent attempting to install libjs.dylib.

comment:2 Changed 3 years ago by jasonliu-- (Jason Liu)

comment:3 Changed 3 years ago by jasonliu-- (Jason Liu)

I will mark the two ports as conflicting, until a permanent fix is implemented upstream.

comment:4 Changed 3 years ago by Jason Liu <jasonliu--@…>

Owner: set to Jason Liu <jasonliu--@…>
Resolution: fixed
Status: newclosed

In 493ac072a0f87a11ed60ef4ca9abad5feae707d8/macports-ports (master):

usd: mark port as conflicting with spidermonkey

Closes: #63258

comment:5 in reply to:  3 Changed 3 years ago by cooljeanius (Eric Gallager)

Replying to jasonliu--:

I will mark the two ports as conflicting, until a permanent fix is implemented upstream.

Update: the upstream issue was fixed: https://github.com/PixarAnimationStudios/USD/issues/1615#issuecomment-956611229

Note: See TracTickets for help on using tickets.