Opened 2 years ago

Last modified 2 years ago

#65665 assigned defect

SilentKnight @1.21: broken linking on Big Sur

Reported by: cooljeanius (Eric Gallager) Owned by: lhaeger (Lothar Haeger)
Priority: Normal Milestone:
Component: ports Version: 2.7.2
Keywords: Cc:
Port: SilentKnight

Description

rev-upgrade currently fails for me with this: 

Could not open /usr/lib/swift/libswiftQuickLookUI.dylib: Error opening or reading file (referenced from /Applications/MacPorts/SilentKnight.app/Contents/MacOS/SilentKnight)
DEBUG: Marking /Applications/MacPorts/SilentKnight.app/Contents/MacOS/SilentKnight as broken
Could not open /opt/local/libexec/boost/1.71/lib/libboost_python39-mt.dylib: Error opening or reading file (referenced from /opt/local/libexec/boost/1.71/lib/libboost_numpy39-mt.dylib)
DEBUG: Marking /opt/local/libexec/boost/1.71/lib/libboost_numpy39-mt.dylib as broken
--->  Found 2 broken files, matching files to ports
Error: Port SilentKnight is still broken after rebuilding it more than 3 times.
DEBUG: rev-upgrade failed: Port SilentKnight still broken after rebuilding 3 times
    while executing
"error "Port $portname still broken after rebuilding $rebuild_tries time${s}""
    (procedure "revupgrade_scanandrebuild" line 310)
    invoked from within
"revupgrade_scanandrebuild broken_port_counts $opts"
    ("uplevel" body line 3)
    invoked from within
"uplevel 1 $body"
Error: rev-upgrade failed: Port SilentKnight still broken after rebuilding 3 times
Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.

I'm on Big Sur with Xcode 13.

Change History (2)

comment:1 Changed 2 years ago by jmroot (Joshua Root)

Cc: lhaeger removed
Owner: set to lhaeger
Status: new → assigned
Summary: SilentKnight @1.21: still broken after rebuilding it more than 3 times → SilentKnight @1.21: broken linking on Big Sur

comment:2 Changed 2 years ago by cooljeanius (Eric Gallager)

This went away for a little while, but now seems to be back again... I think maybe I had just deactivated it previously to get around the rev-upgrade error, and now somehow it got reactivated again?

Note: See TracTickets for help on using tickets.