I must say I have been very surprised to discover the result :
cat /etc/debian_version
testing/unstable
Well, well ... Could I possibly be so "on the hedge" for my preferred distribution without even knowing it ?
So I checked a few things like the version of xfree :
*** Opt x11 xprint-commo 0.1.0.alpha 0.1.0.alpha Xprint - the X11 print system (configuration files)
*** Opt x11 xprt-xprinto 0.1.0.alpha 0.1.0.alpha Xprint - the X11 print system (dummy)
*** Opt x11 xsensors 0.46-1 0.46-1 A hardware health information viewer
*** Opt x11 xserver-comm 4.3.0.dfsg. 4.3.0.dfsg. files and utilities common to all X servers
*** Opt x11 xserver-xfre 4.3.0.dfsg. 4.3.0.dfsg. the XFree86 X server
*** Opt x11 xt 0.9.1-6 0.9.1-6 A graphical traceroute
*** Opt x11 xterm 4.3.0.dfsg. 4.3.0.dfsg. X terminal emulator
And this "should" confirm that I am running Debain/Sarge, when I compare
http://packages.debian.org/stable/x11/ and
http://packages.debian.org/testing/x11/And the version of gcc :
gcc --version
gcc (GCC) 3.3.5 (Debian 1:3.3.5-13)
which "seems to be" the sarge version : gcc (4:3.3.5-3), while the "testing" version is : gcc (4:4.0.2-2)
I suppose the /etc/debian_version may not be accurate, since I have moved to sarge before sarge become the "stable" distribution of Debian.
I looked for the package of "libbfd"
/var/lib/dpkg/info$ egrep libbfd *
binutils.list:/usr/lib/libbfd-2.16.1.so
binutils.shlibs:libbfd 2.16.1 binutils
dselect tells me this :
Std devel binutils 2.16.1-2 2.16.1-2 The GNU assembler, linker and binary utilitie
The stable version (
http://packages.debian.org/stable/x11/) is : binutils (2.15-6)
The testing version is : binutils (2.16.1cvs20051214-1)
So my binutils package is not correct, but I cannot figure out how this is possible.
I checked :
root:/var/lib/apt/lists# egrep "Package: binutil" *
ftp.debian.org_debian_dists_sarge_main_binary-i386_Packages:Package: binutils
And there is only 2.15 here ...
I really wonder where this 2.16 version comes from.
I swear I am not playing with anyone's nerves. You can disreguard this message if you are not interested. It seems to not be an amule problem, but rather a debian-related one.
Moreover, amule works perfectly. Thanks.Crashed one or two times, I'll post some backtraces if I reproduce the probleme.