postgresql is blocking libpq - ????

[i0]

Hey

Cannot update postgresql.
Does the following mean that i have to remove completely postgresql server to upgrade it to vers 8.1.5??

Code: Select all

orion log # emerge -vpuD libpq

These are the packages that would be merged, in order:

Calculating dependencies... done!
[blocks B     ] <=dev-db/postgresql-8.1.4 (is blocking dev-db/libpq-8.1.5)
[ebuild     U ] sys-devel/m4-1.4.6 [1.4.4] USE="nls" 495 kB 
[ebuild     U ] sys-libs/zlib-1.2.3-r1 [1.2.3] USE="-build" 0 kB 
[ebuild     U ] sys-apps/texinfo-4.8-r5 [4.8-r2] USE="nls -build -static" 0 kB 
[ebuild     U ] sys-devel/autoconf-wrapper-3.2-r2 [3.2] 0 kB 
[ebuild     U ] sys-devel/autoconf-2.60 [2.59-r7] USE="-emacs" 1,334 kB 
[ebuild     U ] sys-devel/automake-wrapper-2-r1 [1-r1] 0 kB 
[ebuild     U ] dev-db/libpq-8.1.5 [8.1.4] USE="nls pam readline ssl zlib -kerberos -pg-intdatetime% -threads" 7,997 kB 

Total size of downloads: 9,827 kB
orion log # emerge -vpuD postgresql

These are the packages that would be merged, in order:

Calculating dependencies... done!
[blocks B     ] <=dev-db/postgresql-8.1.4 (is blocking dev-db/libpq-8.1.5)
[ebuild     U ] sys-devel/autoconf-wrapper-3.2-r2 [3.2] 0 kB 
[ebuild     U ] sys-apps/texinfo-4.8-r5 [4.8-r2] USE="nls -build -static" 0 kB 
[ebuild     U ] sys-devel/m4-1.4.6 [1.4.4] USE="nls" 495 kB 
[ebuild     U ] sys-devel/autoconf-2.60 [2.59-r7] USE="-emacs" 1,334 kB 
[ebuild     U ] sys-devel/automake-wrapper-2-r1 [1-r1] 0 kB 
[ebuild     U ] sys-libs/zlib-1.2.3-r1 [1.2.3] USE="-build" 0 kB 
[ebuild     U ] dev-db/libpq-8.1.5 [8.1.4] USE="nls pam readline ssl zlib -kerberos -pg-intdatetime% -threads" 7,997 kB 
[ebuild     U ] dev-db/postgresql-8.1.5 [8.1.4] USE="nls pam perl python readline ssl zlib -doc -kerberos -pg-intdatetime (-selinux) -tcl -test% -xml (-libg++%) (-threads%) (-tk%)" 0 kB 

Total size of downloads: 9,827 kB

file package.keywords contains:
dev-db/postgresql
dev-db/libpq

So yes, i use testing versions.

[Yui]

Just unmerge postgresql and re-emerge it after...

[i0]

uuh.

Not the answer i was looking for.

Is there another way?
This in not a big upgrade, why such complicated method?
Is this normal for postgresql upgrade?

[Yui]

What I understand from that

[blocks B ] <=dev-db/postgresql-8.1.4 (is blocking dev-db/libpq-8.1.5)

Is that postgresql-8.1.4 cannot be installed with libpq-8.1.5, yeah I know postgres will upgrade to 8.1.5 just after but well, emerge don't see it like that

If you don't want to unmerge it try to upgrade postgresql before libpq so

emerge -av postgresql

Without the D and u, maybe it will work.

If not maybe emerge have some options that can force it to emerge anyway but I can't help you on that

Edit : Maybe by editing the ebuild, I don't know ...

[i0]

Nope
Whitout D result is same.

Code: Select all

orion log # emerge -p postgresql

These are the packages that would be merged, in order:

Calculating dependencies... done!
[blocks B     ] <=dev-db/postgresql-8.1.4 (is blocking dev-db/libpq-8.1.5)
[ebuild     U ] dev-db/libpq-8.1.5 [8.1.4] USE="-pg-intdatetime%" 
[ebuild     U ] dev-db/postgresql-8.1.5 [8.1.4] USE="-test%" 
orion log # emerge -p libpq

These are the packages that would be merged, in order:

Calculating dependencies... done!
[blocks B     ] <=dev-db/postgresql-8.1.4 (is blocking dev-db/libpq-8.1.5)
[ebuild     U ] dev-db/libpq-8.1.5 [8.1.4] USE="-pg-intdatetime%" 

I would not like to force package to be upgraded.
You do one thing not as it is supposed to be done and soon you'll discover that it affects other things too and so on - rolling snowball effect.

I would like to do it as intended, just that i refuse to believe that for this small version upgrade i need to unmerge it.

Anybody?

[tightcode]

I agree with i0 here. You shouldn't have to uninstall a package to upgrade it. I have run into the same problem.

Cheers, TC

[Corona688]

I agree with i0 here. You shouldn't have to uninstall a package to upgrade it.

Certainly seem to be a lot of things that need that lately.

[mzalfres]

Hi,

I have solved that with quite simple modification of ebuild, just hashed dependency in $PORTDIR/dev-db/libpq/libpq-8.1.5.ebuild
Of course, you need also modify all checksums in $PORTDIR/dev-db/libpq/Manifest file to make it working...

Code: Select all

#RDEPEND="!<=dev-db/postgresql-8.1.4
RDEPEND="       kerberos? ( virtual/krb5 )
                pam? ( virtual/pam )
                readline? ( >=sys-libs/readline-4.1 )
                ssl? ( >=dev-libs/openssl-0.9.6-r1 )
                zlib? ( >=sys-libs/zlib-1.1.3 )"

Cheers,

ZJ.

[anime-otaku]

I had the same problem...on my laptop, but the postgres there is only for developing, so I unmerged it and libpq,too and remerged it afterwards....I had to update 2 config files. I couldn't test it yet, but it seems to work.

[i0]

I have solved that with quite simple modification of ebuild, just hashed dependency in $PORTDIR/dev-db/libpq/libpq-8.1.5.ebuild
Of course, you need also modify all checksums in $PORTDIR/dev-db/libpq/Manifest file to make it working...

Is there any negative effects? did you dump databases before and after updrade imported them?
If no, is everything working as it supposed to?

I had the same problem...on my laptop, but the postgres there is only for developing, so I unmerged it and libpq,too and remerged it afterwards....I had to update 2 config files. I couldn't test it yet, but it seems to work.

Did You dump databases before unmerge?

[anime-otaku]

Did You dump databases before unmerge?

No...and I didn't tested it yet, but it has to be a minor change so it shouldn't be a problem.

[ehud]

Does anyone know how to contact the ebuild maintainer?
There must be a reason for adding the dependency of libpq on the same postgresql version (which doesn't allow an upgrade). This wasn't in the previous version of libpq, and it would be nice to know why it was added.

Maybe it was meant to avoid a situation where we upgrade libpq and then something fails, so we get a newer libpq with an older postgresql which is compiled using an older libpq?

[i0]

...
There must be a reason for adding the dependency of libpq on the same postgresql version (which doesn't allow an upgrade). ...

YES!
Exactly my point. There must be some reason they did that.
As for me, i'll try unmerge method on one machine.
Second one is too critical to poke around with.
I'll let you know how it went.

[mzalfres]

Hi again,

some explanation: removing dependancy from ebuild is OK, ONLY assuming you want to update both packages. Otherwise, results are unpredictable.

I did my update this way and can't see any problems with my postgres. BUT, currently I have no special use for database (only amarok is using it )

Regards,

Marek ZJ.

[djcapelis]

I think

Code: Select all

emerge -uO1av postgresql libpq libpqxx

ought to do it.....

The merge is running now, anyone see a problem with this?

[djcapelis]

I think

Code: Select all

emerge -uO1av postgresql libpq libpqxx

ought to do it.....

The merge is running now, anyone see a problem with this?

Actually, this works a lot better: (In that, it actually works)

Code: Select all

emerge -uO1av libpq libpqxx postgresql

You may want to play it safe and

Code: Select all

emerge -1av libpq libpqxx

as well... a bit too tired to figure out whether that's really necessary though, you might be able to get away without it.

[akaempf]

I had this problem as well, and was able to get around it by unmerging both postgresql and libpq, then emerging postgresql (which pulls in libpq as a dependency). Seems to work fine with my existing databases.

[llongi]

Well, the blocker was added for the simple reason of file-collisions. With the new libpq/postgresql versions we've moved a file from the postgresql package to the libpq package. Now, you have to emerge libpq BEFORE postgresql, so when Portage was installing libpq it would bail out with a "file collision found, blabla" error. The only way we have of notifying the user of this is by adding a blocker.
The easiest and most correct way to upgrade would be this:

Code: Select all

FEATURES="-collision-protect" emerge --nodeps libpq
emerge postgresql

The first one basically emerge libpq without checking for blockers and disables the file-collision check, so that the new libpq will install correctly, and then you can normally upgrade postgresql itself (which you MUST do, both really *must* be upgraded!).
HTH!

[zwennie]

Hi all,

i upgrade my previous postgresql 8.0.9 to the testing version 8.1.5-r1 but after it finishes nothing works. I need version 8.1.x because mediawiki doesn't work with earlier versions. it would work with mysql, but i tried installing mediawiki with mysql a few times, it doesnt work...
if someone is interested, here is the error message:

Code: Select all

Creating tables... using MySQL 4 table defs...Query "CREATE TABLE `wiki_job` ( job_id int(9) unsigned NOT NULL auto_increment, job_cmd varchar(242) NOT NULL default '', job_namespace int NOT NULL, job_title varchar(242) binary NOT NULL, job_params blob NOT NULL default '', PRIMARY KEY job_id (job_id), KEY (job_cmd, job_namespace, job_title) ) TYPE=InnoDB " failed with error code "Specified key was too long; max key length is 1024 bytes (localhost)".

but my question was after postgresql... I tried installing postgresql different ways, i unemerged postgres and reemerged and so on, lately i tried it after last suggestion in this thread.
Here is what happens:
before unemerging the old version i did a pg_dumpall operation to save my db contents. after that i renamed the postgresql directory in /var/lib to a new name.
then i emerge the new version, which works pretty well. now i followed the instrutions and did a

Code: Select all

"emerge --config =postgresql-8.1.5-r1"

which also seems to be working well.
the server is starting and stopping cleanly.
but now, if i try to restore my db dump it dosent work. also if i try to create a new database or user i get an error message:

Code: Select all

createdb: could not connect to database postgres: FATAL:  database "postgres" does not exist
DETAIL:  The database subdirectory "/var/lib/postgresql/data/pg_tblspc/499/10793" is missing.

does someone have any help? i dont know further...

thanks for any hints...

[Ast0r]

Well, the blocker was added for the simple reason of file-collisions. With the new libpq/postgresql versions we've moved a file from the postgresql package to the libpq package. Now, you have to emerge libpq BEFORE postgresql, so when Portage was installing libpq it would bail out with a "file collision found, blabla" error. The only way we have of notifying the user of this is by adding a blocker.
The easiest and most correct way to upgrade would be this:

Code: Select all

FEATURES="-collision-protect" emerge --nodeps libpq
emerge postgresql

The first one basically emerge libpq without checking for blockers and disables the file-collision check, so that the new libpq will install correctly, and then you can normally upgrade postgresql itself (which you MUST do, both really *must* be upgraded!).
HTH!

Is this safe on a production system? I want to upgrade my systems that use Postgresql, but if it fucks up my databases I will be in deep shit.

EDIT: Also, if I install libpq 8.0.9, will my PHP scripts that use libpq still work as long as I don't restart Apache or will I have to install the new version of PostgreSQL and restart it before they will work? I am trying to figure out if I need to do the upgrade at night or whether I can install it now and just restart the services tonight.

[llongi]

Is this safe on a production system? I want to upgrade my systems that use Postgresql, but if it fucks up my databases I will be in deep shit.

EDIT: Also, if I install libpq 8.0.9, will my PHP scripts that use libpq still work as long as I don't restart Apache or will I have to install the new version of PostgreSQL and restart it before they will work? I am trying to figure out if I need to do the upgrade at night or whether I can install it now and just restart the services tonight.

Well, it should be perfectly safe, as it does the same as any old upgrade did, it just disables file-collision-checking for libpq, so it can overwrite the pg_config binary, which has got nothing to do with a "running" postgresql, it's only used to gather info when other packages compile.
It also shouldn't break PHP scripts at all, as the library version didn't change.

[cmulcahy]

Greetings, all:

I'm trying to get by this error as well. I'm trying the -collision-protect and --nodeps ideas. It's still not working. It is like it is not acknowledging my options. Thoughts?

Thanks!

Code: Select all

gentoobox chris # FEATURES="-collision-protect" emerge --nodeps libpq
Calculating dependencies... done!

!!! Error: the >=dev-db/libpq-8.0.9 package conflicts with another package;
!!!        the two packages cannot be installed on the same system together.
!!!        Please use 'emerge --pretend' to determine blockers.

For more information about Blocked Packages, please refer to the following
section of the Gentoo Linux x86 Handbook (architecture is irrelevant):

http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?full=1#blocked

gentoobox chris # FEATURES="-collision-protect" emerge --nodeps libpq -p

These are the packages that would be merged, in order:

Calculating dependencies... done!
[blocks B     ] >=dev-db/libpq-8.0.9 (is blocking dev-db/postgresql-8.0.8)
[ebuild  N    ] dev-db/libpq-8.0.9  USE="nls pam readline ssl zlib -kerberos -pg-intdatetime -threads"
gentoobox chris #

[talles]

I tried to get around this by unmerging postgresql and libpq, but now emerge postgresql fails with this error:

Code: Select all

!!! ERROR: dev-db/postgresql-8.0.9-r1 failed.
Call stack:
  ebuild.sh, line 1562:   Called dyn_setup
  ebuild.sh, line 665:   Called pkg_setup
  postgresql-8.0.9-r1.ebuild, line 50:   Called built_with_use 'dev-db/postgresql' 'pg-hier'
  eutils.eclass, line 1597:   Called die

!!! Unable to resolve dev-db/postgresql to an installed package
!!! If you need support, post the topmost build error, and the call stack if relevant.

Any idea what I'm missing here?

[Ast0r]

Is this safe on a production system? I want to upgrade my systems that use Postgresql, but if it fucks up my databases I will be in deep shit.

EDIT: Also, if I install libpq 8.0.9, will my PHP scripts that use libpq still work as long as I don't restart Apache or will I have to install the new version of PostgreSQL and restart it before they will work? I am trying to figure out if I need to do the upgrade at night or whether I can install it now and just restart the services tonight.

Well, it should be perfectly safe, as it does the same as any old upgrade did, it just disables file-collision-checking for libpq, so it can overwrite the pg_config binary, which has got nothing to do with a "running" postgresql, it's only used to gather info when other packages compile.
It also shouldn't break PHP scripts at all, as the library version didn't change.

I did the update last night and it worked fine for the most part. The pg_autovacuum init script seems to be broken, though. :\

[cgmoller]

I am getting this too.

I tried to get around this by unmerging postgresql and libpq, but now emerge postgresql fails with this error:

Code: Select all

!!! ERROR: dev-db/postgresql-8.0.9-r1 failed.
Call stack:
  ebuild.sh, line 1562:   Called dyn_setup
  ebuild.sh, line 665:   Called pkg_setup
  postgresql-8.0.9-r1.ebuild, line 50:   Called built_with_use 'dev-db/postgresql' 'pg-hier'
  eutils.eclass, line 1597:   Called die

!!! Unable to resolve dev-db/postgresql to an installed package
!!! If you need support, post the topmost build error, and the call stack if relevant.

Any idea what I'm missing here?

I had the same issue -

Code: Select all

[blocks B     ] <=dev-db/postgresql-8.0.8 (is blocking dev-db/libpq-8.0.9)
[ebuild     U ] dev-db/libpq-8.0.9 [8.0.8] USE="-pg-intdatetime% -threads%"
[ebuild     U ] dev-db/postgresql-8.0.9-r1 [8.0.8] USE="-test%"

I unmerged postgresql-8.0.8
I then emerged libpq-8.0.9 with no problems
Now I too am getting the same error as above.
I noticed I had 8.0.1 and 8.0.9 together - so I unmerged them both and re-emerged 8.0.9.
No change.

Thoughts?