Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 40135

Summary: Ebuild for dia app-office/dia-0.92_pre7 did not emerge pygtk before ebuild
Product: Gentoo Linux Reporter: Andrew <tireman>
Component: New packagesAssignee: Gentoo Linux Gnome Desktop Team <gnome>
Status: RESOLVED INVALID    
Severity: normal CC: aross
Priority: High    
Version: unspecified   
Hardware: x86   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Andrew 2004-02-01 16:39:25 UTC
When installing dia, the pygtk ebuild was not set as a dependency causing the dia build to error out:


checking for python... /usr/bin/python
checking if Python version >= 1.5.2... okay
checking local Python configuration... looks good
checking for python module gtk... no
configure: error: could not find pygtk module

!!! ERROR: app-office/dia-0.92_pre7 failed.
!!! Function econf, Line 339, Exitcode 1
!!! econf failed



Reproducible: Didn't try
Steps to Reproduce:
1.
2.
3.
Comment 1 foser (RETIRED) gentoo-dev 2004-02-03 06:01:34 UTC
emerge info ? do you have python in USE ? The dep is there, if the pack is not it shouldn't break on it.
Comment 2 Andrew 2004-02-03 15:17:53 UTC
Yes I have python installed. Version 2.3.3

When I emerge'd dia out. For some reason it did not pick up on that dependency. When I manually emerge'd "pygtk" out then retried for dia, dia processed without a problem. 

root@smegs$ emerge info
Portage 2.0.49-r21 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r9, 2.4.22-gentoo-r2)
=================================================================
System uname: 2.4.22-gentoo-r2 i686 AMD-K7(tm) Processor
Gentoo Base System version 1.4.3.10
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O3 -mcpu=athlon -funroll-loops -pipe"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
CXXFLAGS="-O3 -mcpu=athlon -funroll-loops -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox"
GENTOO_MIRRORS="ftp://cs.ubishops.ca/pub/gentoo ftp://sunsite.ualberta.ca/pub/unix/Linux/gentoo/ ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X aalib apm arts avi berkdb cdr crypt cups encode esd foomaticdb gdbm gif gnome gpm gtk gtk2 imlib java jpeg kde libg++ libwww mad mikmod motif mozilla mpeg ncurses nls oggvorbis opengl oss pam pdflib perl png python qt quicktime readline sdl slang spell ssl svga tcltk tcpd truetype x86 xml2 xmms xv zlib"
Comment 3 foser (RETIRED) gentoo-dev 2004-02-04 02:45:50 UTC
I asked if you had it in USE (but you do it's in your info), it's installed on most Gentoo systems. The dep tracking obviously should include it, so that means pygtk is actually installed (can you confirm that?). In that case it is probably a python upgrade problem, did you run the python update script ? Can you attach the failing config.log ?
Comment 4 Andrew 2004-02-04 06:17:01 UTC
Is that not what I told you? If it was not in use, why would it be installed?

What python update script?

And no I don't have the failing config.log
Comment 5 foser (RETIRED) gentoo-dev 2004-02-04 08:16:28 UTC
We're talking _optional_ deps here, not mandatory (and yes python is sort of mandatory on Gentoo).

'What script' makes me think we have the problem. Liquidx care to explain?

And yes you do have the failing config.log, you only have to find it. It's in your temp builddir somewhere.

And you still have to confirm if pygtk-2.* is actually installed.
Comment 6 Alastair Tse (RETIRED) gentoo-dev 2004-02-04 11:16:54 UTC
well, basically, if you are upgrading from python-2.2 to python-2.3, you need to run /usr/sbin/python-updater which recompiles all the things that still stuck with python-2.2

if you haven't run it, then you should. this is both in python's ebuild and also on gentoo-announce and the forums announce, so you can't miss it.
Comment 7 Andrew 2004-02-05 19:38:41 UTC
Yes I have pygtk 2.0.0 installed now. When the ebuild for dia failed on pygtk, I intitiated the ebuild manually. 

*  dev-python/pygtk
      Latest version available: 2.0.0
      Latest version installed: 2.0.0

No I don't have a config.log for dia. 
Comment 8 Alex Vandiver 2004-03-14 21:22:26 UTC
I just ran into this, and found a possible alternate reason for the problem.  This can also happen if your DISPLAY is corrupted, or you don't have an X display attached to the terminal.  Apparently the check for pygtk tries to open a connection to the X server...
Comment 9 splite 2004-04-09 07:47:26 UTC
The check for pygtk only tries to connect to the X server if DISPLAY is set.  The ebuild should unset DISPLAY before running configure.  The check succeeds without DISPLAY set, and it's unlikely that the sandboxed user is going to be authorized to connect to whatever DISPLAY points to anyway.
Comment 10 Alastair Tse (RETIRED) gentoo-dev 2004-04-09 15:53:37 UTC
you sure that is how it works? 

liquidx@huggins liquidx $ unset DISPLAY
liquidx@huggins liquidx $ python -c 'import gtk'
Traceback (most recent call last):
  File "<string>", line 1, in ?
  File "/usr/lib/python2.3/site-packages/gtk-2.0/gtk/__init__.py", line 43, in ?
    from _gtk import *
RuntimeError: could not open display

Comment 11 Andrew Ross (RETIRED) gentoo-dev 2004-05-04 21:30:12 UTC
Is this even an issue anymore? After all, there is an ebuild for dia-0.92.2 in portage. Perhaps the pre_7 ebuild should be removed?
Comment 12 Leonardo Boshell (RETIRED) gentoo-dev 2004-06-07 15:01:12 UTC
pre7 has been removed from the tree now. Thanks for the report.