Thread: BUG #16488: psql installation initdb
The following bug has been logged on the website: Bug reference: 16488 Logged by: Dadoz nights Email address: spacexnasafbi@gmail.com PostgreSQL version: 12.3 Operating system: blackarch linux Description: hello pleas help i have been talking to archlinux they dont want even help and the blackarch community says its the arch linux problem go to there support so now i am here because this is the last choice i dont have any choices i have been 5 days in this problem and still in it . when i type this command this happens : initdb --locale en_US.UTF-8 -D /var/lib/postgres/data/data /usr/bin/postgres: error while loading shared libraries: libicui18n.so.67: cannot open shared object file: No such file or directory no data was returned by command ""/usr/bin/postgres" -V" initdb: error: The program "postgres" is needed by initdb but was not found in the same directory as "/usr/bin/initdb". Check your installation.
PG Bug reporting form <noreply@postgresql.org> writes: > when i type this command this happens : initdb --locale en_US.UTF-8 -D > /var/lib/postgres/data/data > /usr/bin/postgres: error while loading shared libraries: libicui18n.so.67: > cannot open shared object file: No such file or directory Well, that seems pretty straightforward: you don't have libicui18n, or at least you don't have the right version of it. Does ls /usr/lib*/libicui18n* show anything? I don't know anything about blackarch but on a Fedora 32 box I see /usr/lib64/libicui18n.so.65 /usr/lib64/libicui18n.so.65.1 If you don't see anything, perhaps you just need to install libicu. If you do but it's not version 67, then you have a version-skew problem, and you might have to recompile Postgres to make it work with the libicu version that your distro provides. Either way, I wonder how you got into this situation. Any reasonable package manager would have insisted on installing a compatible libicu version along with Postgres. Did you override such warnings at install? regards, tom lane
No, I don't.
Idont no I use thunar as file manager
So how do I install libcu
And things the right way
On Jun 9, 2020 5:10 PM, "Tom Lane" <tgl@sss.pgh.pa.us> wrote:
PG Bug reporting form <noreply@postgresql.org> writes:
> when i type this command this happens : initdb --locale en_US.UTF-8 -D
> /var/lib/postgres/data/data
> /usr/bin/postgres: error while loading shared libraries: libicui18n.so.67:
> cannot open shared object file: No such file or directory
Well, that seems pretty straightforward: you don't have libicui18n,
or at least you don't have the right version of it.
Does
ls /usr/lib*/libicui18n*
show anything? I don't know anything about blackarch but on
a Fedora 32 box I see
/usr/lib64/libicui18n.so.65
/usr/lib64/libicui18n.so.65.1
If you don't see anything, perhaps you just need to install libicu.
If you do but it's not version 67, then you have a version-skew
problem, and you might have to recompile Postgres to make it work
with the libicu version that your distro provides.
Either way, I wonder how you got into this situation. Any reasonable
package manager would have insisted on installing a compatible libicu
version along with Postgres. Did you override such warnings at install?
regards, tom lane
At Fri, 12 Jun 2020 16:22:11 +0200, baki baki <spacexnasafbi@gmail.com> wrote in > No, I don't. > Idont no I use thunar as file manager > So how do I install libcu > And things the right way As a workaround, "pacman -S icu" would do that for you. If you find another missing library, the pkgfile command will find the package to install for the file for you. > On Jun 9, 2020 5:10 PM, "Tom Lane" <tgl@sss.pgh.pa.us> wrote: > > PG Bug reporting form <noreply@postgresql.org> writes: > > when i type this command this happens : initdb --locale en_US.UTF-8 -D > > /var/lib/postgres/data/data > > /usr/bin/postgres: error while loading shared libraries: libicui18n.so.67: > > cannot open shared object file: No such file or directory > > Well, that seems pretty straightforward: you don't have libicui18n, > or at least you don't have the right version of it. > > Does > ls /usr/lib*/libicui18n* > show anything? I don't know anything about blackarch but on > a Fedora 32 box I see > /usr/lib64/libicui18n.so.65 > /usr/lib64/libicui18n.so.65.1 > > If you don't see anything, perhaps you just need to install libicu. > If you do but it's not version 67, then you have a version-skew > problem, and you might have to recompile Postgres to make it work > with the libicu version that your distro provides. > > Either way, I wonder how you got into this situation. Any reasonable > package manager would have insisted on installing a compatible libicu > version along with Postgres. Did you override such warnings at install? > > regards, tom lane regards. -- Kyotaro Horiguchi NTT Open Source Software Center
Thanks, I'll check it out.
It says bash pacman command not found
On Mon, Jun 15, 2020, 3:38 AM Kyotaro Horiguchi <horikyota.ntt@gmail.com> wrote:
At Fri, 12 Jun 2020 16:22:11 +0200, baki baki <spacexnasafbi@gmail.com> wrote in
> No, I don't.
> Idont no I use thunar as file manager
> So how do I install libcu
> And things the right way
As a workaround, "pacman -S icu" would do that for you. If you find
another missing library, the pkgfile command will find the package to
install for the file for you.
> On Jun 9, 2020 5:10 PM, "Tom Lane" <tgl@sss.pgh.pa.us> wrote:
>
> PG Bug reporting form <noreply@postgresql.org> writes:
> > when i type this command this happens : initdb --locale en_US.UTF-8 -D
> > /var/lib/postgres/data/data
> > /usr/bin/postgres: error while loading shared libraries: libicui18n.so.67:
> > cannot open shared object file: No such file or directory
>
> Well, that seems pretty straightforward: you don't have libicui18n,
> or at least you don't have the right version of it.
>
> Does
> ls /usr/lib*/libicui18n*
> show anything? I don't know anything about blackarch but on
> a Fedora 32 box I see
> /usr/lib64/libicui18n.so.65
> /usr/lib64/libicui18n.so.65.1
>
> If you don't see anything, perhaps you just need to install libicu.
> If you do but it's not version 67, then you have a version-skew
> problem, and you might have to recompile Postgres to make it work
> with the libicu version that your distro provides.
>
> Either way, I wonder how you got into this situation. Any reasonable
> package manager would have insisted on installing a compatible libicu
> version along with Postgres. Did you override such warnings at install?
>
> regards, tom lane
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center