Package: ia32-libs Version: 1.5 Severity: grave Justification: renders package unusable
I had installed an amd64 system (debian unstable) a few weeks back (this is the system I am on now), I got most of my applications (both 32 and 64) working (using ia32-libs version-1.5). When I tried to do the same on a friend's laptop I got ALOT of problems with 32-bit applications (from big EDA companies) complaining about GLIBC_2.0 not being defined. On the advice of 'mrvn' (from #debian-amd64) I downgraded the laptop's ia32-libs from 1.6 to 1.4 (sarge -- we didn't know how to grab 1.5) and the complaints ceased and all functions properly now. The issue as it stands is, what changed in glibc between 1.5 and 1.6 relating to GLIBC_2.0 and could this "GLIBC_2.0" tag be reintroduced ? Fedora/RH seem to be handling this problem somehow since other friends note things working for them with the latest beta releases (akin to debian's unstable) without any issues. BTW: the laptop's system info is pasted below post the change-over from 1.6 back to 1.4 on its ia32-libs. -- Laptop System Information: Debian Release: testing/unstable APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-amd64-generic Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages ia32-libs depends on: ii lib32gcc1 3.4.3-13 GCC support library (ia32) ii lsb-release 3.0-16 Linux Standard Base version report ia32-libs recommends no packages. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-11-amd64-k8-smp Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages ia32-libs depends on: ii lib32gcc1 1:4.0.2-9 GCC support library (32 bit Versio ii lib32z1 1:1.2.3-9 compression library - 32 bit runti ii lsb-release 3.0-16 Linux Standard Base version report ia32-libs recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]