Red Hat Bugzilla – Bug 1288730
postgresql: README.rpm-dist incorrect about running postgresql-setup
Last modified: 2016-11-24 09:26:40 EST
README.rpm-dist contains this advice:
For a fresh installation, you will need to initialize the cluster first
(as a postgres user):
$ postgresql-setup --initdb
-bash-4.3$ postgresql-setup --initdb
FATAL: /usr/bin/postgresql-setup requires root access for this action
-bash-4.3$ rpm -q postgresql-server
Thanks for the report, I fixed this in git some time ago:
I don't think it is worth doing respin -- if it is OK, I would wait for
the next PostgreSQL update in 23.
Pavel, would you be OK with moving postgresql-setup to v3.5 in rawhide
Yes, I see no problem.
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 23 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fixed F24+, sorry for not fixing this for F23, there were race condition
in "ownership" of this bug.
(In reply to Pavel Raiskup from comment #4)
> Fixed F24+, sorry for not fixing this for F23, there were race condition
> in "ownership" of this bug.
No problem, thanks!