On 31/01/13 12:08 AM, Brad Alexander wrote:
On Wed, Jan 30, 2013 at 11:08 PM, Gary Dale<garyd...@rogers.com> wrote:
On 30/01/13 07:31 PM, Brad Alexander wrote:
Keeping on the gaming theme, I have a question Many months ago, I
installed playonlinux, and the wine64-unstable libs in order to play
Starcraft II. Well I haven't played it in a longish while, apparently
since before multiarch. So I fired up playonlinux, tried to run
Starcraft, and got the following popup from playonlinux:
This is the wine64-bin helper package, which does not provide wine itself,
but instead exists solely to provide the following information about
enabling multiarch on your system in order to be able to install and run
the 32-bit wine packages.
The following commands should be issued as root or via sudo in order to
enable multiarch (the last command installs 32-bit wine):
# dpkg --add-architecture i386
# apt-get update
# apt-get install wine-bin:i386
Be very careful as spaces matter above. Note that this package
(wine64-bin) will be removed in the process. For more information on
the multiarch conversion, see: http://wiki.debian.org/Multiarch/HOWTO
However, when I tried to install wine-bin:i386, apt tells me:
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
wine-bin:i386 : Depends: libwine-bin:i386 (= 1.4.1-4) but it is not
going to be installed
and apt-cache search for it indeed comes up empty. However, searching
on the unstable page on packages.d.o, I see both libwine-bin and
libwine-bin-unstable, and what's more, they are only for i386,
kfreebsd-i386 and powerpc. should I just apt-get install wine-bin (or
wine-bin-unstable), or did I miss something with the architectures?
(dpkg --print-architectures says amd64, and dpkg
--print-foreign-architectures says i386).
Thanks,
--b
I believe you need to install wine-bin:i386 to ensure that you are getting
the correct architecture. You could try installing libwine-bin to see if
that resolves the problem (or at least gives you a more helpful message).
Or you could file a bug report. Unstable doesn't always work properly. The
procedure above worked fine with Wheezy.
This is exactly what I did above. I installed (or attempted to
install) wine-bin:i386. It was libwine-bin:i386 that was missing in
action. I could probably try to downgrade to wheezy, but I suspect
that would lead to significant breakage.
Either you're not explaining yourself well or you missed the point,
which was to try apt-get install libwine-bin. When a package doesn't
install due to a dependency issue, installing the missing dependency (or
at least trying to) may give you more information. Perhaps the package
itself doesn't exist in the correct version.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/510a7df1.4070...@rogers.com
