Opened 18 months ago
Closed 18 months ago
#72033 closed defect (fixed)
qt6-qtwebengine @6.8.1: destroot fails
| Reported by: | tobbi (Tobias Markus) | Owned by: | MarcusCalhoun-Lopez (Marcus Calhoun-Lopez) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.10.5 |
| Keywords: | monterey | Cc: | reneeotten (Renee Otten) |
| Port: | qt6-qtwebengine |
Description
The staging phase of qt6-qtwebengine fails on my MacOSX 12.7.6 with the following error message:
Error: Failed to destroot qt6-qtwebengine: xinstall: Unable to create new file for: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_aqua_qt6/qt6-qtwebengine/work/destroot/opt/local/libexec/qt6/lib/QtWebEngineCore.framework/Resources Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_aqua_qt6/qt6-qtwebengine/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port qt6-qtwebengine failed
Attachments (1)
Change History (6)
Changed 18 months ago by tobbi (Tobias Markus)
| Attachment: | qt6-qtwebengine.log added |
|---|
comment:1 Changed 18 months ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | reneeotten added |
|---|---|
| Keywords: | monterey added |
| Owner: | set to MarcusCalhoun-Lopez |
| Status: | new → assigned |
| Summary: | Staging qt6-qtwebengine 6.8.1 fails on MacOS X 12.7.6 → qt6-qtwebengine @6.8.1: destroot fails |
We've seen that error on the buildbot before as well:
comment:2 Changed 18 months ago by jmroot (Joshua Root)
This port is marked as requiring darwin >= 23 (i.e. macOS >= 14), but I guess it wasn't always that way. Maybe a better upgrade path (to qt67-qtwebengine in this case?) is needed for older OS versions that fall out of the supported range.
comment:3 Changed 18 months ago by tobbi (Tobias Markus)
I found a similar issue that happened on restoring ports for qt-qtwebengine @6.4.3 here: #68465
comment:4 Changed 18 months ago by tobbi (Tobias Markus)
I can verify that creating the path manually, as described in comment:ticket:68465:description fixed the issue for me.
comment:5 Changed 18 months ago by reneeotten (Renee Otten)
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.

log