-
Notifications
You must be signed in to change notification settings - Fork 3
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
resolve indeterminate or inappropriate postgresql alternative config #34
Comments
For this we need the 'alternatives' command line that selects, non interactively, our postgresql13 requirement. |
Using an aging system (Leap 15.3) with already 2 alternatives we have:
which was the default anyway:
|
Switch to postgresql10:
With the following slave settings to the master postgresql10 binary index:
So in the above we see the equivalent of pg_config not being available as our example systems '10' packages do not provide it, at least under the configuration of alternatives in the 'postgresql10' setting. Switch back to postgresql13 alternative.Our supported and previously working (with pg_config) package set:
And we have:
|
…ockstor#34 Enforce, via manual alternatives configuration, our target postgresql version.
…ppropriate_postgresql_alternative_config resolve indeterminate or inappropriate postgresql alternative config #34
Closing as: |
Thanks to @FroggyFlox & forum members agjbond007 & anborn; for helping to identify this issue. It is currently supposed that, as a result of zypper dup OS version transitions, given examples were (15.3->15.4) & (15.2->15.3->15.4) the, required for Poetry venv build, pg_config file can become unrepresented: i.e. no longer having an alternatives link. This file, as installed by our dependence on:
Is normally available via:
However, during a zypper dup, the new default postgresql version of 14 is installed as per agjbond007 report in the linked forum thread:
But in the above we see that there is no counterpart to the postgresql13-server-devel installed in the 14 variant, and thus no counterpart provider (via alternatives) of our required pg_config - used by our Poetry dependencies manager to build our Python dependencies upon install/update.
The fix provided by @FroggyFlox in the linked forum thread is to re-assert our dependency upon postgresql13 (and it's server-devel counterpart) via a move away from the auto alternative (as higher priority due to newer) which has unfortunately obscured (removed from alternative managed path) the requried for venv build 'pg_config' utility.
The following shows the by-hand intervention currently required for installs that have previously been 'zypper dup' (distribution updated) from a prior Leap version:
Proposal
We currently have an rpm defined dependency on postresql13 and it's associated server and server-devel packages so rather than move all these dependency over the the newer, OS default, of 14, we should assert our system requirement via the alternative system. At least until we update our own client library of (from pyproject.toml):
This older dependency, that is questionable re Postgresql 13, should likely not be tried further with postgresql 14. In the context of our master and testing branches currently span Python 2.7 / 3.6.
This proposed postgresql alternatives assertion could be accomplished within a scriptlet, prior to our Poetry venv build, and post our new rpm/scriptlets install (which would have already installed our dependencies): e.g. %post.
Referenced:
SuSe SLE: https://documentation.suse.com/sles/15-SP5/html/SLES-all/cha-update-alternative.html
Forum threads:
-- agjbond007 - https://forum.rockstor.com/t/upgrade-to-5-0-1-0-from-4-6-1-rockstor-fails/8905
-- anborn - https://forum.rockstor.com/t/system-unavailable-after-update-to-stable-4-6-1-0-release/8904
The text was updated successfully, but these errors were encountered: