Package: libbz2-1.0
Version: 1.0.2-7
Severity: grave
Justification: renders package unusable


Hi,

I think there is a problem with libbz2-1.0. Upon installation on a
completely sane system (for example, a pbuilder environnement), the
symlink /usr/lib/libbz2.so -> /usr/lib/libbz2.so.1.0 is missing,
preventing the compilation of programs using libbz2.

Here is an exemple, ran inside a testing pbuilder environnement (same
problem with an unstable pbuilder environnement) :

[EMAIL PROTECTED]:/# apt-get install libbz2-1.0
Reading Package Lists... Done
Building Dependency Tree... Done
Suggested packages:
  libbz2-dev bzip2
The following NEW packages will be installed:
  libbz2-1.0
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/38.7kB of archives.
After unpacking 119kB of additional disk space will be used.
Selecting previously deselected package libbz2-1.0.
(Reading database ... 8049 files and directories currently installed.)
Unpacking libbz2-1.0 (from .../libbz2-1.0_1.0.2-7_i386.deb) ...
Setting up libbz2-1.0 (1.0.2-7) ...

[EMAIL PROTECTED]:/# cd root/
[EMAIL PROTECTED]:/root# cat > toto.c
int main(void) { return 0; }
[EMAIL PROTECTED]:/root# gcc -o toto toto.c -lbz2
/usr/bin/ld: cannot find -lbz2
collect2: ld returned 1 exit status

Now, if I add the symlink, the application will compile:

[EMAIL PROTECTED]:/root# ln -s /usr/lib/libbz2.so.1.0 /usr/lib/libbz2.so
[EMAIL PROTECTED]:/root# gcc -o toto toto.c -lbz2

This problem is not present in my stable pbuilder environnement.

Sincerly,

Thomas

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11.11
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)

Versions of packages libbz2-1.0 depends on:
ii  libc6                       2.3.2.ds1-22 GNU C Library: Shared libraries an

libbz2-1.0 recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to