-
-
Notifications
You must be signed in to change notification settings - Fork 14.9k
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
postgresql_11: remove #264250
postgresql_11: remove #264250
Conversation
Failing Hydra build: https://hydra.nixos.org/build/239477682/nixlog/1 This got fixed upstream already in the release branches, applying the patches here solves the issue. This skips v11 since there's no patch available and it will be dropped soon anyways[1]. [1] NixOS#264250
@ofborg eval |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should an entry be added in pkgs/top-level/aliases.nix
?
@natsukium The eval is failing because #264290 isn't included, needs rebase
What about postgresql_10? |
This wasn't done in the past and I don't see a reason to do this (assuming you mean an alias like In this case it's mostly a matter of reading the release notes or getting an error when evaluating your NixOS deployment which should be sufficient IMHO.
Assuming you mean that this isn't in the |
As described in the release lifecycle docs from postgresql[1], v11 will stop receiving fixes as of Nov 9 2023. This means it's EOL throughout the entire lifetime of 23.11, so let's drop it now. A lot of examples are also referencing postgresql_11. Where it's sensible, use postgresql_15 as example now to avoid confusion. This is also handy because the LLVM 16 fix for postgresql is not available for postgresql 11 ;-) [1] https://www.postgresql.org/support/versioning/
By default `pg_config --bindir` is executed during configure phase to get the bin directory containing all the postgres executables used by glom. This seems wrong given that the same postgresql_15 package will be executed on build and on the final host platform which is not necessarily the same. To avoid that, specify the bin dir manually via the corresponding configure option.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks!
Would you mind removing pipelinedb.nix
and other references of "11"
in the extensions?
@marsam done :) |
This one is apparently abandoned by upstream and only supported postgresql_11 which is about to be dropped from nixpkgs.
Huh just realized that there's still a reference left in |
I don't really understand why this is only for a single version, so I figured I'd just add this to the test matrix to also cover this test-case for each major. Now, there's also one thing less to take care of when removing old postgresql versions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
I was upgrading my configuration from 23.05 to 23.11 and got this error:
It was confusing because I have never set @Ma27, I suggest changing the error message to something like this:
|
Feel free to file a PR for that. |
Description of changes
This version will stop receiving fixes as of Nov 09 2023, so it needs to be removed before 23.11.
cc @NixOS/nixos-release-managers
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)