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

[qt] Update qt 6.7.1 #38845

Merged
merged 53 commits into from
Jun 11, 2024
Merged

[qt] Update qt 6.7.1 #38845

merged 53 commits into from
Jun 11, 2024

Conversation

Neumann-A
Copy link
Contributor

@Neumann-A Neumann-A commented May 21, 2024

Closes #38835
Closes #39040

@carsten-grimm-at-ipolog
Copy link
Contributor

This update will also fix Issue #38968.

@WangWeiLin-MV WangWeiLin-MV linked an issue May 28, 2024 that may be closed by this pull request
@Neumann-A
Copy link
Contributor Author

So question now:

  • Should I finish the update to 6.7.1 now or should I wait for qtdeclarative being fixed by upstream? (https://bugreports.qt.io/browse/QTBUG-125481)
  • or should I try updating everything but keep qtdeclarative at 6.7.0 (which might create other issues?)
  • or simply wait for 6.7.2 and hope they resolve it until then?

@LilyWangLL LilyWangLL requested a review from vicroms May 29, 2024 08:57
@carsten-grimm-at-ipolog
Copy link
Contributor

So question now:

  • Should I finish the update to 6.7.1 now or should I wait for qtdeclarative being fixed by upstream? (https://bugreports.qt.io/browse/QTBUG-125481)
  • or should I try updating everything but keep qtdeclarative at 6.7.0 (which might create other issues?)
  • or simply wait for 6.7.2 and hope they resolve it until then?

If you decide to wait, there could be a separate pull request for the (as of yet unrated) vulnerability CVE-2024-36048 from #38968. That might take away one reason to upgrade to 6.7.1 now.

@Neumann-A
Copy link
Contributor Author

I expect the cve fix to be merged faster any way.

@carsten-grimm-at-ipolog
Copy link
Contributor

I expect the cve fix to be merged faster any way.

@Neumann-A , I have added a pr for the cve patch: #39056.

@nirvn
Copy link
Contributor

nirvn commented Jun 5, 2024

https://codereview.qt-project.org/c/qt/qtdeclarative/+/565938

Light at the end of the tunnel

# Conflicts:
#	ports/qtbase/vcpkg.json
#	ports/qtdeclarative/vcpkg.json
#	ports/qtinterfaceframework/vcpkg.json
#	ports/qtnetworkauth/vcpkg.json
#	ports/qttools/vcpkg.json
#	ports/qtwebengine/vcpkg.json
#	versions/baseline.json
#	versions/q-/qtbase.json
#	versions/q-/qtdeclarative.json
#	versions/q-/qtinterfaceframework.json
#	versions/q-/qtnetworkauth.json
#	versions/q-/qttools.json
#	versions/q-/qtwebengine.json
@Neumann-A Neumann-A marked this pull request as ready for review June 6, 2024 08:48
@BillyONeal BillyONeal added the info:reviewed Pull Request changes follow basic guidelines label Jun 11, 2024
@BillyONeal BillyONeal merged commit 0a34f76 into microsoft:master Jun 11, 2024
17 checks passed
@Neumann-A Neumann-A deleted the update_qt_6.7.1 branch June 11, 2024 19:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:port-update The issue is with a library, which is requesting update new revision info:reviewed Pull Request changes follow basic guidelines
Projects
None yet
5 participants