View previous topic :: View next topic |
Author |
Message |
kingfame_147 Apprentice
Joined: 11 Oct 2008 Posts: 171
|
Posted: Thu Jul 23, 2009 2:49 pm Post subject: Amarok with postgresql 8.2.7 on amd64 |
|
|
Hi,
yesterday i decided to unmask postgresql-8.2.7 because i needed a 8.2 version.
After updating postgresql amarok didn't start because of an libpq.so error. Thats ok, because amarok links vs. the old libpq. But if i want to remerge amarok now i looks like that:
Code: |
[ebuild NS ] dev-db/libpq-7.4.19 [8.2.7] USE="nls pam readline ssl zlib -kerberos" 0 kB
[ebuild NS ] virtual/postgresql-base-7.4 [8.0] 0 kB
[ebuild R ] media-sound/amarok-1.4.10_p20090130-r2 USE="amazon musicbrainz mysql opengl postgres python xinerama -daap -debug -ifp -ipod -kde -mp4 -mtp -njb (-real) -visualization" LINGUAS="de -af -ar -az -be -bg -bn -br -ca -cs -cy -da -el -en_GB -eo -es -et -eu -fa -fi -fr -ga -gl -he -hi -hu -id -is -it -ja -km -ko -ku -lo -lt -mk -ms -nb -nds -ne -nl -nn -pa -pl -pt -pt_BR -ro -ru -rw -se -sk -sl -sq -sr -sr@Latn -ss -sv -ta -tg -th -tr -uk -uz -zh_CN -zh_TW" 0 kB
|
Is there any reason why amarok wants to use libpq-7.4.19?! Before the postgresql update i had the normal 8.0.15 running. Why amarok wants that old libpq now?
libpq doesnt compile right now because it conflicts with with the newer libpq version. How can i tell amarok to use that new version? :/
Regards,
fame |
|
Back to top |
|
|
audiodef Watchman
Joined: 06 Jul 2005 Posts: 6639 Location: The soundosphere
|
|
Back to top |
|
|
kingfame_147 Apprentice
Joined: 11 Oct 2008 Posts: 171
|
Posted: Thu Jul 23, 2009 8:21 pm Post subject: |
|
|
1) I want amarok to use postgresql for my collection. So yes, i need it.
2) i dont need the old libpq, but if i emerge amarok now (after the upgrade of postgresql) emerge also want's to install that old libpq.
The strange thing is that BEFORE the update the old libpq wasn't installed. |
|
Back to top |
|
|
kingfame_147 Apprentice
Joined: 11 Oct 2008 Posts: 171
|
Posted: Sun Jul 26, 2009 11:19 am Post subject: |
|
|
I found the problem:
i didn't umasked "virtual/postgresql-base". But a packaged needed that package and therefore as a dep. "virtual/postgresql-base" wanted that old libpq package.
Thanks for your help.
Regards,
fame |
|
Back to top |
|
|
|