Opened 6 months ago
Last modified 3 months ago
#68693 assigned defect
postgresql13 @13.13_0+universal destroot failure on macOS Sonoma 14.1.1
| Reported by: | sudheerhebbale (Sudheer Hebbale) | Owned by: | dgilman (David Gilman) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | barracuda156 | |
| Port: | postgresql13 |
Description (last modified by jmroot (Joshua Root))
The following error gets generated
Staging postgresql13 into destroot Error: Failed to destroot postgresql13: error copying "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_databases_postgresql13/postgresql13/work/destroot" to "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_databases_postgresql13/postgresql13/work/destroot-arm64/destroot": file already exists Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_databases_postgresql13/postgresql13/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port postgresql13 failed
Attachments (2)
Change History (5)
Changed 6 months ago by sudheerhebbale (Sudheer Hebbale)
comment:1 Changed 6 months ago by jmroot (Joshua Root)
| Cc: | barracuda156 added |
|---|---|
| Description: | modified (diff) |
| Owner: | set to dgilman |
| Port: | postgresql13 added |
| Status: | new → assigned |
| Summary: | Unable to install postgresql13 on macOS Sonoma 14.1.1 → postgresql13 @13.13_0+universal destroot failure on macOS Sonoma 14.1.1 |
Changed 5 months ago by halostatue (Austin Ziegler)
| Attachment: | main.2.log added |
|---|
main.log on Ventura with +universal
comment:2 Changed 5 months ago by halostatue (Austin Ziegler)
I am seeing the same destroot failure on Ventura with +universal, but not without +universal.
comment:3 Changed 3 months ago by dgilman (David Gilman)
I have a tentative fix that will go out with the next point release of PostgreSQL which is slated for the next week or so. I won't close this ticket until I get some feedback on how it works. The fix successfully builds a universal PostgreSQL but I can't confirm that it correctly runs on multiple architectures. In particular I think it may fail across the 32/64-bit split but that is uncommon anyway.
The fix was to use the build system's zic to compile the timezone files. The risk is that the binary timezone files are in some way arch specific. If that is the case it is not going to be possible to have a universal PostgreSQL and I'll just have to rip universal support out.