Wine installer broken in non ahs version (Solved) [Solved]

[tony37]

Can someone having problems do a simulation with aptitude and see what it has to say?

Code: Select all

aptitude -s install winehq-staging

The error messages given by 'apt' in case of dependency problems are mostly useless

[JayM]

Okay, when I try to install wine from MXPI Popular Apps in a VirtualBox VM installation of MX-19.3, when I click on Show Details I get an empty details field. This is with both the LA mirror and the "mothership" in SLC. When I do the same an an MX-19.3 AHS VB installation I see a list of packages to be installed. So codydragonrude was right and I was wrong: there's something different about and broken in the non-AHS version. For one thing, /usr/share/mx-packageinstaller-packagelist/Wine.pm is missing in the non-AHS version.

(Crow doesn't taste too bad if you put enough ketchup on it.)

[tony37]

@JayM I don't have the same problem, so can you do the command from post 11 and see what it does?

[JayM]

Code: Select all

jay@mx:~
$ aptitude -s install winehq-staging
The following NEW packages will be installed:
  libaom0:i386{a} libasound2:i386{a} libasound2-plugins:i386{a} libasyncns0:i386{a} 
  libatomic1:i386{a} libavcodec58:i386{ab} libavresample4:i386{ab} libavutil56:i386{ab} 
  libblkid1:i386{a} libbsd0:i386{a} libcairo2:i386{a} libcap2:i386{a} libcodec2-0.8.1:i386{a} 
  libcroco3:i386{a} libcrystalhd3:i386{a} libdatrie1:i386{a} libdb5.3:i386{a} 
  libdbus-1-3:i386{a} libdrm2:i386{a} libexif12:i386{a} libexpat1:i386{a} libffi6:i386{a} 
  libflac8:i386{a} libfontconfig1:i386{a} libfreetype6:i386{a} libfribidi0:i386{a} 
  libgcrypt20:i386{a} libgd3:i386{a} libgdk-pixbuf2.0-0:i386{a} libglib2.0-0:i386{a} 
  libgmp10:i386{a} libgnutls30:i386{a} libgomp1:i386{a} libgpg-error0:i386{a} 
  libgphoto2-6:i386{a} libgphoto2-port12:i386{a} libgraphite2-3:i386{a} libgsm1:i386{a} 
  libgstreamer-plugins-base1.0-0:i386{a} libgstreamer1.0-0:i386{a} libharfbuzz0b:i386{a} 
  libhogweed4:i386{a} libice6:i386{a} libicu63:i386{a} libidn2-0:i386{a} 
  libjack-jackd2-0:i386{a} libjbig0:i386{a} libjpeg62-turbo:i386{a} liblcms2-2:i386{a} 
  libldap-2.4-2:i386{a} libltdl7:i386{a} liblz4-1:i386{a} liblzma5:i386{a} libmount1:i386{a} 
  libmp3lame0:i386{a} libmpg123-0:i386{a} libncurses5{a} libncurses5:i386{a} libnettle6:i386{a} 
  libnuma1:i386{a} libogg0:i386{a} libopenal1:i386{a} libopenjp2-7:i386{a} libopus0:i386{a} 
  liborc-0.4-0:i386{a} libp11-kit0:i386{a} libpango-1.0-0:i386{a} libpangocairo-1.0-0:i386{a} 
  libpangoft2-1.0-0:i386{a} libpcre3:i386{a} libpixman-1-0:i386{a} libpng16-16:i386{a} 
  libpulse0:i386{a} librsvg2-2:i386{a} libsamplerate0:i386{a} libsasl2-2:i386{a} 
  libsasl2-modules-db:i386{a} libselinux1:i386{a} libshine3:i386{a} libsm6:i386{a} 
  libsnappy1v5:i386{a} libsndfile1:i386{a} libsndio7.0:i386{a} libsoxr0:i386{a} 
  libspeex1:i386{a} libstdc++6:i386{a} libswresample3:i386{ab} libsystemd0:i386{a} 
  libtasn1-6:i386{a} libthai0:i386{a} libtheora0:i386{a} libtiff5:i386{a} libtinfo5{a} 
  libtinfo5:i386{a} libtwolame0:i386{a} libudev1:i386{a} libunistring2:i386{a} 
  libusb-1.0-0:i386{a} libuuid1:i386{a} libva-drm2:i386{ab} libva-x11-2:i386{ab} 
  libva2:i386{ab} libvdpau1:i386{a} libvkd3d1{a} libvkd3d1:i386{a} libvorbis0a:i386{a} 
  libvorbisenc2:i386{a} libvpx5:i386{a} libvulkan1:i386{a} libwavpack1:i386{a} libwebp6:i386{a} 
  libwebpmux3:i386{a} libwrap0:i386{a} libx11-6:i386{a} libx11-xcb1:i386{a} libx264-155:i386{a} 
  libx265-165:i386{a} libxau6:i386{a} libxcb-render0:i386{a} libxcb-shm0:i386{a} 
  libxcb1:i386{a} libxdmcp6:i386{a} libxext6:i386{a} libxfixes3:i386{a} libxi6:i386{a} 
  libxml2:i386{a} libxpm4:i386{a} libxrender1:i386{a} libxtst6:i386{a} libxvidcore4:i386{a} 
  libzstd1:i386{a} libzvbi0:i386{a} ocl-icd-libopencl1:i386{a} wine-gecko2.47.1{a} 
  wine-gecko2.47.1:i386{a} wine-mono5.1.0{a} wine-staging{a} wine-staging-amd64{a} 
  wine-staging-i386:i386{a} winehq-staging zlib1g:i386{a} 
The following packages will be REMOVED:
  libcrystalhd3{u} liblua5.3-0{u} libxcb-cursor0{u} libxcb-xtest0{u} libxdg-basedir1{u} 
  linux-headers-4.19.0-13-amd64{u} linux-headers-4.19.0-13-common{u} lua-lgi{u} 
The following packages are RECOMMENDED but will NOT be installed:
  gstreamer1.0-plugins-base:i386 i965-va-driver:i386 i965-va-driver-shaders:i386 
  intel-media-va-driver:i386 intel-media-va-driver-non-free:i386 libcapi20-3 libcapi20-3:i386 
  libcups2:i386 libgdk-pixbuf2.0-bin libgdk-pixbuf2.0-bin:i386 libgnutlsxx28 libgnutlsxx28:i386 
  libgpg-error-l10n libgphoto2-l10n libgpm2:i386 libgtk-3-0:i386 libodbc1 libodbc1:i386 
  libosmesa6 libosmesa6:i386 libpcap0.8:i386 librsvg2-common:i386 libsane:i386 
  libsasl2-modules:i386 libv4l-0:i386 libvdpau-va-gl1:i386 libxcomposite1:i386 libxcursor1:i386 
  libxinerama1:i386 libxrandr2:i386 libxslt1.1:i386 libxt6:i386 libxxf86vm1:i386 
  mesa-va-drivers:i386 mesa-vdpau-drivers:i386 nvidia-legacy-340xx-vdpau-driver:i386 
  nvidia-legacy-390xx-vdpau-driver:i386 nvidia-tesla-vdpau-driver:i386 nvidia-vdpau-driver:i386 
  uuid-runtime uuid-runtime:i386 va-driver-all:i386 vdpau-driver-all:i386 vdpau-va-driver:i386 
0 packages upgraded, 141 newly installed, 8 to remove and 0 not upgraded.
Need to get 288 MB of archives. After unpacking 777 MB will be used.
The following packages have unmet dependencies:
 libswresample3 : Breaks: libswresample3:i386 (!= 7:4.3.1-2~mx19+2) but 7:4.1.6-1~mx19+2 is to be installed
 libswresample3:i386 : Breaks: libswresample3 (!= 7:4.1.6-1~mx19+2) but 7:4.3.1-2~mx19+2 is installed
 libva2 : Breaks: libva2:i386 (!= 2.6.1-1mx19+1) but 2.4.0-1 is to be installed
 libva2:i386 : Breaks: libva2 (!= 2.4.0-1) but 2.6.1-1mx19+1 is installed
 libavcodec58 : Breaks: libavcodec58:i386 (!= 7:4.3.1-2~mx19+2) but 7:4.1.6-1~mx19+2 is to be installed
 libavcodec58:i386 : Breaks: libavcodec58 (!= 7:4.1.6-1~mx19+2) but 7:4.3.1-2~mx19+2 is installed
 libavutil56 : Breaks: libavutil56:i386 (!= 7:4.3.1-2~mx19+2) but 7:4.1.6-1~mx19+2 is to be installed
 libavutil56:i386 : Breaks: libavutil56 (!= 7:4.1.6-1~mx19+2) but 7:4.3.1-2~mx19+2 is installed
 libva-x11-2 : Breaks: libva-x11-2:i386 (!= 2.6.1-1mx19+1) but 2.4.0-1 is to be installed
 libva-x11-2:i386 : Breaks: libva-x11-2 (!= 2.4.0-1) but 2.6.1-1mx19+1 is installed
 libva-drm2 : Breaks: libva-drm2:i386 (!= 2.6.1-1mx19+1) but 2.4.0-1 is to be installed
 libva-drm2:i386 : Breaks: libva-drm2 (!= 2.4.0-1) but 2.6.1-1mx19+1 is installed
 libavresample4 : Breaks: libavresample4:i386 (!= 7:4.3.1-2~mx19+2) but 7:4.1.6-1~mx19+2 is to be installed
 libavresample4:i386 : Breaks: libavresample4 (!= 7:4.1.6-1~mx19+2) but 7:4.3.1-2~mx19+2 is installed
The following actions will resolve these dependencies:

      Keep the following packages at their current version:
1)      libasound2-plugins:i386 [Not Installed]            
2)      libavcodec58:i386 [Not Installed]                  
3)      libavresample4:i386 [Not Installed]                
4)      libavutil56:i386 [Not Installed]                   
5)      libswresample3:i386 [Not Installed]                
6)      libva-drm2:i386 [Not Installed]                    
7)      libva-x11-2:i386 [Not Installed]                   
8)      libva2:i386 [Not Installed]                        
9)      wine-staging [Not Installed]                       
10)     wine-staging-i386:i386 [Not Installed]             
11)     winehq-staging [Not Installed]                     



Accept this solution? [Y/n/q/?] 

[tony37]

libva2 : Breaks: libva2:i386 (!= 2.6.1-1mx19+1) but 2.4.0-1 is to be installed

One possibility is that you installed libva packages from the test repo at some time and now the 32-bit packages would need to come from there too to stay compatible
Or else this 2.6.1-1mx19+1 version of libva2 used to be in the MX stable repo, but has now disappeared

[JayM]

No, this is a recent stock installation of MX in VB. All I've done AFAIR is the updates. I can blow the virtual machine away and reinstall from scratch though, just to make sure.

[codydragonrude]

I'm going to mark this as solved because i switched to another distro
I just do not have the time to sit here and troubleshoot distro problems

[JayM]

I remembered that I have another VM installation of MX-19.3 non-AHS, this one installed as UEFI, which I've never done anything with but updated and wine installs fine on it from MXPI, Pop Apps, Misc. The first VB installation is the one that I use to try to replicate peoples' problems and stuff so it's probably hosed and needs a reinstall. I'll wait and do MX-19.4 though.

So, to recap regarding the OP's original complaint:
1. There is no "wine installer." Wine is installed from MX Package Installer, Synaptic Package Manager, or apt from the command-line just like any other application.
2. Wine installs from MX Package Installer, Popular Applications, Misc. on a fresh installation of MX-19.3 with no problems. There is nothing the matter with the package installer or the distro.

It's possible that OP's repository mirror was in the middle of being updated at the time he tried to install wine, so if he'd just been a little more patient and waited a while it may have resolved itself. Or his "you have held broken packages" issue may have been caused by using a broken 3rd-party MX mirror all along which may have updated his system with broken packages. OP was too impatient and uncooperative to work with forum volunteers and his peers to try to fix it.

[SwampRabbit]

@codydragonrude

Codythdragonrude @codythedragonrude@linuxrocks.online

lol mxlinux dropping a 19.4 iso probably to fix that issue that's totally my problem LOL

Nope, not even close, was in the works long before your post, enjoy Manjaro though its a good Distro.

Codythdragonrude @codythedragonrude@linuxrocks.online

the mx linux forum was pretty useless

they kept suggesting things that did not work and saying it's not a them but rather a me problem even though they are the ones who decided to have a custom repo wine installer which also breaks the repo by just doing it from the winehq site

mxlinux is a MessX https://linuxrocks.online/@codythedrag

Iol... you know what... nvm... it ain't even worth it for someone like this


Edit: maybe you can use the real way to mark a thread solved, then again you don't ever get on the forums much, so you probably missed that function exists now.

[tony37]

I do think that at some point some packages (ffmpeg, libva) made it to the MX stable repo which shouldn't have done so. Maybe @JayM can check on his VB install where he had the problem when libva2 got updated:

Code: Select all

apt-history libva2

But yes, on a new install (any new install, no 19.4 needed for this), there are no problems.