Bug 1428997
Summary: | Port wxGTK3 to webkit2 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jeremy Newton <alexjnewt> |
Component: | wxGTK3 | Assignee: | Scott Talbert <swt> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | alexjnewt, swt |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-05-16 20:23:48 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jeremy Newton
2017-03-03 18:55:12 UTC
Pull request submitted upstream: https://github.com/wxWidgets/wxWidgets/pull/439 Can we push this as fixed with the 3.0.3 update? or did this only land in master? If so, can you just update the patch to the final implementation, and we can include this in the 3.0.3 update push? (In reply to Jeremy Newton from comment #2) > Can we push this as fixed with the 3.0.3 update? or did this only land in > master? > > If so, can you just update the patch to the final implementation, and we can > include this in the 3.0.3 update push? It has only been merged in master, and I've got another pull request pending for the 3.0 backport. It was only held off because they didn't feel comfortable merging it just before 3.0.3 release. I don't anticipate any changes, since the backport is almost identical to the original patch. Thus, I think it is fine for us to update to the latest patch. I'll go ahead and work on that and the 3.0.3 update tonight. (In reply to Scott Talbert from comment #3) > (In reply to Jeremy Newton from comment #2) > > Can we push this as fixed with the 3.0.3 update? or did this only land in > > master? > > > > If so, can you just update the patch to the final implementation, and we can > > include this in the 3.0.3 update push? > > It has only been merged in master, and I've got another pull request pending > for the 3.0 backport. It was only held off because they didn't feel > comfortable merging it just before 3.0.3 release. I don't anticipate any > changes, since the backport is almost identical to the original patch. > Thus, I think it is fine for us to update to the latest patch. I'll go > ahead and work on that and the 3.0.3 update tonight. Ah, yes, if you would rather avoid pushing the webkit2 patch to Fedora 24/25/26 (to avoid any regression), you could wrap the webkit2 stuff in a "if fedora > 26" or whatever the syntax is. Thanks for your help! wxGTK3-3.0.3-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-ef19872468 wxGTK3-3.0.3-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-ef19872468 wxGTK3-3.0.3-1.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-901ccd6490 wxGTK3-3.0.3-1.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-901ccd6490 wxGTK3-3.0.3-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report. wxGTK3-3.0.3-1.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report. Thanks Scott! |