[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#535153: marked as done (libc6: breaks wine upon upgrade, should have Breaks: wine)

Your message dated Sat, 11 Jul 2009 14:03:52 +0200
with message-id <[🔎] 20090711120352.GC16615@hall.aurel32.net>
and subject line Re: [pkg-wine-party] Bug#535153: libc6: breaks wine upon upgrade, should have Breaks: wine
has caused the Debian Bug report #535153,
regarding libc6: breaks wine upon upgrade, should have Breaks: wine
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
535153: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=535153
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: libc6-i386
Version: 2.9-18
Severity: serious

I run apt-get safe-upgrade, and it upgraded libc, the lib32* packages,
  ia32-apt-get, etc.

Now wine is unusable:
$ wine
/usr/bin/wine: line 63: /usr/lib32/wine/wine.bin: No such file or directory
/usr/bin/wine: line 63: exec: /usr/lib32/wine/wine.bin: cannot execute: No such file or directory

Wine itself wasn't upgraded (it was version 1.1.22-1 yesterday too, and it worked fine).

There are still files left in /emul, some of them belonging to wine:
$ ls /emul/ia32-linux/usr/lib/wine/ -1|wc -l
385

However dpkg thinks that wine has its files in /usr/lib32 already:
$ dpkg -L wine
...
/usr/lib32/wine/clusapi.dll.so
/usr/lib32/libwine.so.1

But the files are not there:
ls: cannot access /usr/lib32/wine: No such file or directory
They are in /emul still:
$ ls -l /emul/ia32-linux/usr/lib/libwine.so.1.0
-rw-r--r-- 1 root root 1207260 2009-06-10 20:59 /emul/ia32-linux/usr/lib/libwine.so.1.0
dpkg-query -S /emul/ia32-linux/usr/lib/libwine.so.1.0
dpkg: /emul/ia32-linux/usr/lib/libwine.so.1.0 not found.

I think libc6 should have a Breaks: for the current versions of wine (in unstable
and experimental), until wine is moved to /usr/lib32.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (600, 'unstable'), (500, 'unstable-i386'), (500, 'transitional-i386'), (500, 'transitional'), (500, 'stable-i386'), (500, 'stable'), (50, 'experimental'), (1, 'experimental-i386')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libc6-i386 depends on:
ii  libc6                         2.9-18     GNU C Library: Shared libraries

libc6-i386 recommends no packages.

libc6-i386 suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Sat, Jul 11, 2009 at 01:14:52PM +0200, Ove Kaaven wrote:
> Aurelien Jarno skrev:
> > Any news on that? Should we make the unstable version of wine not
> > installable, or should we simply close this bug?
> 
> I'm not entirely sure whether you mean unstable as in "sid" (where the
> stable version of Wine, 1.0.*, is), or as in Wine 1.1.* in experimental.
> 
> There's no reason to make Wine 1.0.* uninstallable. It uses /usr/lib,
> not /usr/lib32, and is therefore unaffected by the transition. (I could
> change that, but don't see much point.) Being the current stable release
> of Wine, it is likely to stay there for a while, and with very few
> updates, if any.
> 
> There are issues in experimental, though. I initially made it install
> into /usr/lib32 instead of /usr/lib as a bit of an experiment (in
> anticipation of Wine's 64-bit version), before the transitions began.
> I'll add a Pre-Depends if the Wine packages continue to use /usr/lib32,
> though maybe it won't (I might multiarchify it instead). And when Wine
> 1.1.* goes into unstable, it will probably also be under different
> package names.
> 
> (I would have uploaded such a fixed Wine package already, but right now
> it's a bit difficult to upload any Wine, given the ia32-libs situation.)
> 
> In any case, there won't be broken Wine packages (regarding this, at
> least..) in unstable. And in experimental, I'll just tell anyone who
> asks to reinstall the Wine debs (which works). I'd suggest you ignore
> the problem (close the bug).
> 

Ok, thanks for the explanations, closing the bug.

-- 
Aurelien Jarno	                        GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel32.net

--- End Message ---
Reply to: