353168 – dev-python/psycopg-2.3.2: "Error: could not determine PostgreSQL version from 'eselect'"

Bug 353168 - dev-python/psycopg-2.3.2: "Error: could not determine PostgreSQL version from 'eselect'"

Summary: dev-python/psycopg-2.3.2: "Error: could not determine PostgreSQL version from...

Status:	RESOLVED INVALID

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Library (show other bugs)
Hardware:	AMD64 Linux

Importance:	High normal
Assignee:	Gentoo Linux bug wranglers

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2011-01-29 21:06 UTC by Michal Petrucha
Modified:	2011-01-30 13:28 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
the output of emerge --info (emerge--info.txt,5.73 KB, text/plain) 2011-01-29 21:08 UTC, Michal Petrucha	Details
the complete build log (build.log,4.51 KB, text/plain) 2011-01-29 21:12 UTC, Michal Petrucha	Details
build environment (environment,190.97 KB, text/plain) 2011-01-29 21:13 UTC, Michal Petrucha	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Michal Petrucha 2011-01-29 21:06:01 UTC

The build of dev-python/psycopg-2.3.2 fails with this error message:

Error: could not determine PostgreSQL version from 'eselect'

Reproducible: Always

Steps to Reproduce:
1. emerge -av =dev-python/psycopg-2.3.2

Comment 1 Michal Petrucha 2011-01-29 21:08:42 UTC

Created attachment 261041 [details]
the output of emerge --info

Comment 2 Michal Petrucha 2011-01-29 21:12:41 UTC

Created attachment 261043 [details]
the complete build log

Comment 3 Michal Petrucha 2011-01-29 21:13:45 UTC

Created attachment 261045 [details]
build environment

Comment 4 Aaron W. Swenson gentoo-dev

2011-01-30 13:07:23 UTC

What is the output of `eselect postgresql show'?

Comment 5 Michal Petrucha 2011-01-30 13:28:57 UTC

Eh, sorry, my fault.

The output was (none), after I set it to 9.0, the error disappeared. It was probably unset during an upgrade.