Bug#46585: python-gtk: python-gtk does not start

[Torsten Landschoff <torsten@debian.org>]

Hi *, 

I got the following bug report on my python-gtk package:

On Mon, Oct 04, 1999 at 11:08:51AM +0200, Enrico Zini wrote:
> Package: python-gtk
> Version: 0.6.3-2
> Severity: grave
> [...]
> $ cd /usr/share/doc/python-gtk/examples/simple
> $ ./hello1.py
> Traceback (innermost last):
>   File "./hello1.py", line 6, in ?
>     from _gtk import *
> ImportError: /usr/lib/python1.5/site-packages/_gtkmodule.so: symbol __fork,
> version GLIBC_2.0 not defined in file libpthread.so.0 with link time
> reference
> 
> [...]
>
> -- System Information
> Debian Release: 2.1
> Kernel Version: Linux marvin 2.2.10 #2 Mon Jun 14 19:04:44 CEST 1999 i586 
> 
> Versions of the packages python-gtk depends on:
> ii  libc6           2.1.2-0pre12   GNU C Library: Shared libraries and timezone
> ii  libglib1.2      1.2.4-1        The GLib library of C routines
> ii  libgtk1.2       1.2.5-1        The GIMP Toolkit set of widgets for X
> ii  python-base     1.5.2-6        An interactive object-oriented scripting lan
> ii  xlib6g          3.3.5-1        shared libraries required by X clients

Later he told me that upgrading his libraries solved the problem. I would 
really like to fix that bug I do not have an older libc2.1 than that 
installed on my system and it runs just fine here.

Is there a way we could find out which version of libc changed the symbol 
__fork? I would tend to say that this is a bug in the libc package - the 
shlibs file should be changed to accomodate for the incompatibility 
introduced in libc 2.1.??. 

It could be argued that the problem is in my package as __fork seems to 
be an internal symbol of the libc. But there is no reference to this 
symbol in the sources - a search for "fork" did not find anything. I 
think it must be referenced in some includes.

Reading the upstream changelog I did not find any references to the fork 
symbol. What should I do now? Should I close the bug, add a dependency 
on libc6 (>= 2.1. - what?) or can we change libc and recompile the 
package?

Any help (as with older libc's for testing) appreciated.

Thanks
    Torsten