Hi, It should be fixed in the packages in unstable.
Regards, Julien Lavergne Le mercredi 30 décembre 2009 à 14:39 +0530, Ritesh Raj Sarraf a écrit : > Package: ifuse > Version: 0.9.5-1 > Severity: important > > Hi, Thank you for your work. > > Please add a versioned dependency on libiphone0 > > > r...@champaran:~ $ ifuse /tmp/iphone/ > ifuse: symbol lookup error: ifuse: undefined symbol: iphone_device_new > r...@champaran:~ $ apt-cache show ifuse |less > r...@champaran:~ $ apt-cache policy libiphone0 > libiphone0: > Installed: 0.9.1-4 > Candidate: 0.9.1-4 > Version table: > 0.9.5-1 0 > 500 http://ftp.debian.org unstable/main Packages > 500 http://mirrors.kernel.org unstable/main Packages > *** 0.9.1-4 0 > 990 http://ftp.debian.org testing/main Packages > 990 http://mirrors.kernel.org testing/main Packages > 100 /var/lib/dpkg/status > > Upgrading libiphone0 manually fixes the problem. > > > Regards, > Ritesh > > > -- System Information: > Debian Release: squeeze/sid > APT prefers testing > APT policy: (990, 'testing'), (500, 'unstable'), (101, 'experimental') > Architecture: i386 (i686) > > Kernel: Linux 2.6.32-trunk-686 (SMP w/1 CPU core) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > > Versions of packages ifuse depends on: > ii libc6 2.10.2-2 GNU C Library: Shared libraries > ii libfuse2 2.8.1-1.1 Filesystem in USErspace library > ii libglib2.0-0 2.22.3-1 The GLib library of C routines > ii libgnutls26 2.8.5-2 the GNU TLS library - runtime > libr > ii libiphone0 0.9.5-1 Library for communicating with > the > ii libplist1 1.0-1 Library for handling Apple > binary > ii libtasn1-3 2.3-1 Manage ASN.1 structures (runtime) > ii libusb-1.0-0 2:1.0.6-1 userspace USB programming library > ii libusbmuxd1 1.0.0-1 USB multiplexor daemon for > iPhone > ii libxml2 2.7.6.dfsg-1 GNOME XML library > > ifuse recommends no packages. > > ifuse suggests no packages. > > -- no debconf information > > -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
