Opened 12 months ago
Last modified 12 months ago
#68699 assigned defect
jitsi-meet-electron @2023.10.0: still broken after rebuilding it more than 3 times
Reported by: | TallTed (Ted Thibodeau Jr) | Owned by: | takikawa (Asumu Takikawa) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.8.1 |
Keywords: | mojave | Cc: | |
Port: | jitsi-meet-electron |
Description
Trying to install Jitsi Meet Electron Version: 2023.10.0 on macOS Mojave 10.14.6 (18G9323) because the GUI version from GitHub forces update upon quit, and 2023.11.0 requires macOS Catalina 10.15.x or later.
Error: Port jitsi-meet-electron is still broken after rebuilding it more than 3 times. Error: Please run port -d -y rev-upgrade and use the output to report a bug. Error: rev-upgrade failed: Port jitsi-meet-electron still broken after rebuilding 3 times Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.
As advised --
$ sudo port -d -y rev-upgrade Password: DEBUG: Copying /Users/macted/Library/Preferences/com.apple.dt.Xcode.plist to /opt/local/var/macports/home/Library/Preferences ---> Scanning binaries for linking errors DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Jitsi Meet.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework Could not open /System/Library/Frameworks/ScreenCaptureKit.framework/Versions/A/ScreenCaptureKit: Error opening or reading file (referenced from /Applications/MacPorts/Jitsi Meet.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework) DEBUG: Marking /Applications/MacPorts/Jitsi Meet.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework as broken Could not open /System/Library/Frameworks/Accessibility.framework/Versions/A/Accessibility: Error opening or reading file (referenced from /Applications/MacPorts/Jitsi Meet.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework) DEBUG: Marking /Applications/MacPorts/Jitsi Meet.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework as broken Could not open /System/Library/Frameworks/QuickLookThumbnailing.framework/Versions/A/QuickLookThumbnailing: Error opening or reading file (referenced from /Applications/MacPorts/Jitsi Meet.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework) DEBUG: Marking /Applications/MacPorts/Jitsi Meet.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework as broken Could not open /System/Library/Frameworks/UniformTypeIdentifiers.framework/Versions/A/UniformTypeIdentifiers: Error opening or reading file (referenced from /Applications/MacPorts/Jitsi Meet.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework) DEBUG: Marking /Applications/MacPorts/Jitsi Meet.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework as broken DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Jitsi Meet.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Jitsi Meet.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Jitsi Meet.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Jitsi Meet.app/Contents/Frameworks/Jitsi Meet Helper (GPU).app/Contents/MacOS/Jitsi Meet Helper (GPU) DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Jitsi Meet.app/Contents/Frameworks/Jitsi Meet Helper (Plugin).app/Contents/MacOS/Jitsi Meet Helper (Plugin) DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Jitsi Meet.app/Contents/Frameworks/Jitsi Meet Helper (Renderer).app/Contents/MacOS/Jitsi Meet Helper (Renderer) DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Jitsi Meet.app/Contents/Frameworks/Jitsi Meet Helper.app/Contents/MacOS/Jitsi Meet Helper DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Jitsi Meet.app/Contents/Frameworks/Squirrel.framework/Versions/A/Resources/ShipIt DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Jitsi Meet.app/Contents/Frameworks/Squirrel.framework/Versions/A/Resources/ShipIt DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Jitsi Meet.app/Contents/Frameworks/Squirrel.framework/Versions/A/Squirrel DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Jitsi Meet.app/Contents/Frameworks/Squirrel.framework/Versions/A/Squirrel DEBUG: Ignoring loadcommand containing @rpath in /Applications/MacPorts/Jitsi Meet.app/Contents/MacOS/Jitsi Meet DEBUG: skipping arm64 in /Applications/MacPorts/Jitsi Meet.app/Contents/Resources/app.asar.unpacked/node_modules/@jitsi/robotjs/prebuilds/darwin-x64+arm64/node.napi.node since this system can't run it anyway DEBUG: skipping arm64 in /Applications/MacPorts/Jitsi Meet.app/Contents/Resources/app.asar.unpacked/node_modules/fsevents/fsevents.node since this system can't run it anyway ---> Found 4 broken files, matching files to ports ---> Found 1 broken port, determining rebuild order DEBUG: Broken: jitsi-meet-electron DEBUG: Processing port jitsi-meet-electron @0:2023.10.0_0 You can always run 'port rev-upgrade' again to fix errors. The following ports will be rebuilt: jitsi-meet-electron @2023.10.0 Continue? [Y/n]: y DEBUG: epoch: in tree: 0 installed: 0 DEBUG: jitsi-meet-electron 2023.10.0_0 exists in the ports tree DEBUG: jitsi-meet-electron 2023.10.0_0 is the latest installed DEBUG: jitsi-meet-electron 2023.10.0_0 is active DEBUG: Merging existing requested variants '' into variants DEBUG: new fully merged portvariants: DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/net/jitsi-meet-electron DEBUG: OS darwin/18.7.0 (macOS 10.14.6) arch i386 DEBUG: Sourcing PortGroup github 1.0 from /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/_resources/port1.0/group/github-1.0.tcl DEBUG: Re-registering default for extract.rename DEBUG: Re-registering default for livecheck.url DEBUG: Re-registering default for livecheck.regex DEBUG: Re-registering default for extract.rename DEBUG: universal_variant is false, so not adding the default universal variant DEBUG: Running callback portconfigure::add_automatic_compiler_dependencies DEBUG: Finished running callback portconfigure::add_automatic_compiler_dependencies DEBUG: Running callback portbuild::add_automatic_buildsystem_dependencies DEBUG: Finished running callback portbuild::add_automatic_buildsystem_dependencies DEBUG: Running callback portstartupitem::add_notes DEBUG: Finished running callback portstartupitem::add_notes DEBUG: rev-upgrade override ... upgrading! Skipping deactivate jitsi-meet-electron @2023.10.0_0 (dry run) Skipping activate jitsi-meet-electron @2023.10.0_0 (dry run) DEBUG: Rebuilding port jitsi-meet-electron finished with status 0 Warning: If this was no dry run, rev-upgrade would now run the checks again to find unresolved and newly created problems DEBUG: Checking time since last reclaim run $
Change History (4)
comment:1 Changed 12 months ago by ryandesign (Ryan Carsten Schmidt)
Keywords: | mojave added |
---|---|
Owner: | set to takikawa |
Status: | new → assigned |
Summary: | jitsi-meet-electron 2023.10.0 fails to build on macOS Mojave 10.14.6 (18G9323) (x86_64) → jitsi-meet-electron @2023.10.0: still broken after rebuilding it more than 3 times |
comment:2 Changed 12 months ago by ryandesign (Ryan Carsten Schmidt)
comment:3 Changed 12 months ago by TallTed (Ted Thibodeau Jr)
The above list of Frameworks that were introduced more recently than macOS Mojave would seem to suggest that the Port Health should be changed, and that there should optimally be some test performed by the port install/build, to prevent install/build attempts of 2023.11.0
or later on Mojave or earlier, and optimally leads the MacPorts user to the relevant older version for their environment (which I would have thought was 2023.10.1
, as that's the GUI version that works on Mojave, just requiring manual reinstall after each use since it also forces a background auto update).
comment:4 Changed 12 months ago by ryandesign (Ryan Carsten Schmidt)
Ports can be engineered to install appropriate older versions on older versions of macOS. At present, the jitsi-meet-electron port has not been engineered that way. Or additional ports can be created to provide older versions. At present, there is only one version, the one in jitsi-meet-electron.
Ports can indicate their range of compatible versions (using the platforms
keyword). At present, the jitsi-meet-electron port does not use that keyword.
While there are many deficiencies in the way the port health indicators are currently implemented, in this case the problem appears to be that the port does build, hence successful build status displayed on the port page.
All of the references to the new macOS frameworks are coming from Electron Framework.framework. It shouldn't have been possible to build that on Mojave with references to nonexistent frameworks, therefore I assume the build of jitsi-meet-electron did not build Electron Framework but rather copied a too-new version of Electron Framework that was downloaded from somewhere.
Replying to TallTed:
ScreenCaptureKit.framework was introduced in macOS 12.3.
Accessibility.framework was introduced in macOS 11.
QuickLookThumbnailing.framework was introduced in macOS 10.15.
UniformTypeIdentifiers.framework was introduced in macOS 11.