Your message dated Sun, 23 Mar 2014 00:33:31 -0400
with message-id
<CANTw=monb3jznnbjn_fu7-kybbwbzdphfvcbrmunhwhkwxd...@mail.gmail.com>
and subject line Re: [pkg-wine-party] Bug#741981: wine-bin-unstable:i386:
1.7.14-4 update broke wine (missing wine32)
has caused the Debian Bug report #741981,
regarding wine-bin-unstable:i386: 1.7.14-4 update broke wine (missing wine32)
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 [email protected]
immediately.)
--
741981: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741981
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: wine-bin-unstable
Version: 1.7.14-4
Severity: important
After update to 1.7.14-4, my wine broke and attempting to execute anything
wine-related gives:
exec: wine32: not found
I made sure WINEARCH=win32 was set, but it did not help.
I think my problem is related to this item in the changelog:
* Install binaries to /usr/lib/wine-unstable
To work around the issue, I had to create a symlink named 'wine32' to
/usr/lib/wine-unstable/wine
Now, all works as expected.
Thanks
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.13-6.towo-siduction-amd64 (SMP w/3 CPU cores; PREEMPT)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages wine-bin-unstable:i386 depends on:
ii dpkg 1.17.6
ii wine32-unstable 1.7.14-4
wine-bin-unstable:i386 recommends no packages.
wine-bin-unstable:i386 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
This is intentional. You should use the wine-unstable script to launch
wine-unstable now (or the files in /usr/lib/wine-unstable).
Best wishes,
Mike
--- End Message ---
