Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 6.0.0 notarization fix #2709

Merged
merged 6 commits into from
Jan 17, 2024

Conversation

wpotrzebowski
Copy link
Contributor

@wpotrzebowski wpotrzebowski commented Jan 16, 2024

Description

This PR should fix notarization for release_6.0.0, so that Mac builds should pass now

Fixes # (issue/issues)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.

Review Checklist (please remove items if they don't apply):

  • Code has been reviewed
  • Functionality has been tested
  • Windows installer (GH artifact) has been tested (installed and worked)
  • MacOSX installer (GH artifact) has been tested (installed and worked)
  • User documentation is available and complete (if required)
  • Developers documentation is available and complete (if required)
  • The introduced changes comply with SasView license (BSD 3-Clause)

@wpotrzebowski wpotrzebowski changed the base branch from main to release_6.0.0 January 16, 2024 21:41
@wpotrzebowski wpotrzebowski marked this pull request as ready for review January 17, 2024 22:01
Copy link
Member

@rozyczko rozyczko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks like a straightforward extension of the notarization to include the QtWebEngine and other Qt libraries. If this works, then re-notarizing the libraries is ok

"SasView*.app/Contents/Resources/PySide6/Qt/lib/Qt*.framework/Versions/A/Qt*", recursive=True
)

#pyside_libs = pyside_QtWebEngineCore + pyside_QtWebEngineProcess
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we need to notarize Qt libraries? They are already signed by the Qt Company, after all?
Unless this is something very macos specific? But then, we don't notarize other libraries we depend on...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rozyczko: Yeah, good question. Once they are touched e.g. packaged with pyinstaller they need to be signed again.

@lucas-wilkins lucas-wilkins merged commit 5c1edfc into release_6.0.0 Jan 17, 2024
36 checks passed
@lucas-wilkins lucas-wilkins deleted the release_6.0.0_notarization_fix branch January 17, 2024 22:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants