Your message dated Sun, 5 Oct 2014 00:54:09 -0400 with message-id <CANTw=MPY8s1N9UaHfxANBkaYU=bftqgrrhyqqpnfprz2fsp...@mail.gmail.com> and subject line Re: [pkg-wine-party] Bug#763131: Bug#763131: wine-development: wine64 depends on wine32 being installed has caused the Debian Bug report #763131, regarding wine-development: wine64 depends on wine32 being installed 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.) -- 763131: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763131 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Source: wine-development Version: 1.7.27-1 Severity: normal Hi, wine64 seems not to work if the 32-bit packages aren't installed. I had only the 64-bit packages installed: ii libwine-development:amd64 1.7.27-1 amd64 ii wine-development 1.7.27-1 amd64 ii wine64-development 1.7.27-1 amd64 ... and executed the following line (wrapped for readability here, it was one line): WINEARCH=win64 \ WINELOADER=/usr/lib/wine-development/wine64 \ WINEDEBUG=fixme+all,err+all \ /usr/lib/wine-development/wine64 ImageMagick-6.8.9-7-Q16-x64-static.exe This immediately exits (returns 1), but just gives this output: wine: created the configuration directory '/home/jens/.wine' Could not load wine-gecko. HTML rendering will be disabled. wine: configuration in '/home/jens/.wine' has been updated. After installing libwine-development:i386 and wine32-development:i386 above command worked flawlessly if I removed ~/.wine. If I didn't remove ~/.wine the installation also worked (I could start imdisplay.exe later), but showed some popups about ole errors [1] and failed to open the webpage (in the Linux system webbroser). Useless stuff I tried: I tried adding "env" before the command line and exported some variables: export W=/usr/lib/x86_64-linux-gnu/wine-development/ export WINEVERPATH=$W export PATH=$W:/usr/lib/wine-development/:$PATH export WINESERVER=$W/wineserver export WINELOADER=/usr/lib/wine-development/wine64 export WINEDLLPATH=$W/fakedlls export LD_LIBRARY_PATH=$W [1] Errors when installing in a broken prefix: err:ole:CoGetClassObject class {00021401-0000-0000-c000-000000000046} not registered err:ole:create_server class {00021401-0000-0000-c000-000000000046} not registered err:ole:CoGetClassObject no class object {00021401-0000-0000-c000-000000000046} could be created for context 0x5 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (300, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) 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 wine-development depends on: ii wine64-development 1.7.27-1 wine-development recommends no packages. Versions of packages wine-development suggests: ii binfmt-support 2.1.5-1 ii ttf-mscorefonts-installer 3.5 -- no debconf information
--- End Message ---
--- Begin Message ---On Sat, Sep 27, 2014 at 11:11 PM, jre wrote: > Then wine-development should depend (without alternative) on > wine32-development and perhaps recommend wine64-development. That setup only affects users that ignore recommends, which is advanced, so presumably they knew what they are doing. It is useful as an option for the users that do want it. Best wishes, Mike
--- End Message ---
