Skip to content

Postgresql{13..17}: update to newest versions #28413

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

Merged
merged 5 commits into from
May 20, 2025

Conversation

BjarneDMat
Copy link
Contributor

@BjarneDMat BjarneDMat commented May 12, 2025

Model Identifier: MacPro5,1                 Model Identifier: Macmini6,1
macOS 14.7.5 23H527 x86_64                  macOS 10.15.7 19H2026 x86_64
Xcode 16.2 16C5032a                         Xcode 12.4 12D4e
Command Line Tools 16.2.0.0.1.1733547573    Command Line Tools 12.4.0.0.1.1610135815
port -cuN -f uninstall postgresql*
for pgsql in {13..17}; do port clean --all postgresql${pgsql}; done
for pgsql in {13..17}; do port -cuN -d install postgresql${pgsql}; done
for pgsql in {13..17}; do port -cuN -d install postgresql${pgsql}-server; done
for pgsql in {13..17}; do port -cuN -d upgrade --enforce-variants postgresql${pgsql} +python3; done
port install -cuN llvm-20
for pgsql in {13..17}; do port -cuN -d upgrade --enforce-variants postgresql${pgsql} +llvm -python3; done
for pgsql in {13..17}; do port -cuN -d upgrade --enforce-variants postgresql${pgsql} +llvm +python3; done

update to newest versions
update variant python to python313
update variant llvm to llvm-20

@macportsbot
Copy link

Notifying maintainers:
@jyrkiwahlstedt for port postgresql13-doc, postgresql13-server, postgresql14-doc, postgresql14-server, postgresql15-doc, postgresql15-server.
@barracuda156 for port postgresql13, postgresql14, postgresql15, postgresql16-server, postgresql16, postgresql17-server, postgresql17.
@dgilman for port postgresql13, postgresql14, postgresql15, postgresql16-server, postgresql16, postgresql17-server, postgresql17.

@dgilman
Copy link
Contributor

dgilman commented May 13, 2025

It looks like your PR got raced by mine earlier in the week. I think this one is OK, though, after a rebase on master. However, I would keep the Python 2.7 variant on the ports that had it becuase it is very challenging for any users on Python 2 to get off of it. It is a much more practical experience for them to get off of Python 2 when they do a major PostgreSQL update.

@BjarneDMat BjarneDMat force-pushed the postgresql branch 2 times, most recently from 6a0c5c6 to 4fce054 Compare May 13, 2025 14:29
@BjarneDMat
Copy link
Contributor Author

🆗 I've reversed the python27 changes - they were only present in 13 & 14

@BjarneDMat BjarneDMat force-pushed the postgresql branch 2 times, most recently from e0f8013 to 38ab51e Compare May 13, 2025 14:49
@BjarneDMat
Copy link
Contributor Author

🤔 any chance I could make you take a look at #27811 🙏🏻❓

BjarneDM added 5 commits May 20, 2025 11:06
- use Python 3.13, LLVM 20 in postgresql13 port
- use Python 3.13, LLVM 20 in postgresql14 port
- use Python 3.13, LLVM 20 postgresql15 port
- use Python 3.13, LLVM 20 in postgresql16 port
- use Python 3.13, LLVM 20 in postgreqsl17 port
@reneeotten reneeotten merged commit 4ff5555 into macports:master May 20, 2025
3 checks passed
@BjarneDMat BjarneDMat deleted the postgresql branch May 21, 2025 10:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

6 participants