When I try to install wine using Yast > Software > Software Management I get this
YaST2 conflicts list - generated 2010-05-02 09:07:52
wine-1.1.43-1.4.x86_64 requires wine-32bit = 1.1.43, but this requirement cannot be provided
uninstallable providers: wine-32bit-1.1.43-1.4.i586[OSS]
] do not install wine-1.1.43-1.4.x86_64
] break wine by ignoring some of its dependencies
YaST2 conflicts list END
If I try the 32 bit package I get this
YaST2 conflicts list - generated 2010-05-02 09:11:01
nothing provides libpng14.so.14.so.8 needed by wine-32bit-1.1.43-1.4.i586
] break wine-32bit by ignoring some of its dependencies
] do not install wine-32bit-1.1.43-1.4.i586
A big factor in any such problem is the repositories you have setup. Hence you MUST list the repository details in your help request, else any answer you get is the wildest of speculation and not much help.
I confess I struggle with my attitude when trying to be helpful in cases such as this, because when beta software testing, one should ready know this already … anyway, … maybe once again I’m just a grumpy old man.
This looks like a packaging bug to me, although maybe someone who knows more than I could chime in (because I don’t know much here). But seeing libpng14.so.14.so.8 strikes me as odd. I think it should just be “libpng14.so.14” and I suspect the previous version was “libpng8.so.8” (or something like that) and an error was made when updating the rpm spec file ? …
Those repos look more or less ok. I don’t think the “debug” nor “Update” are worth anything, as those won’t be active until 11.3 GM in July.
I confess I prefer to use the stable baseline from “factory-snapshot” (as opposed to “factory”) for both OSS and Non-OSS, but I think in this case (re: the wine hiccup) it won’t make any difference.
Since you are using “factory”, you could also use the wine factory:
Simple typo, I would suggest to contact the packager/maintainer of that package, the address can be found in the changelog of the package, i.e. like this:
Downloading it won’t solve the dependency problem. It will only confirm the dependency error. Unfortuately the packager did not identify themselves in the rpm. I get this from the wine repos “factory”:
Name : wine Relocations: (not relocatable)
Version : 1.1.39 Vendor: obs://build.opensuse.org/Emulators
Release : 3.1 Build Date: Tue 02 Mar 2010 03:52:19 PM CET
Install Date: (not installed) Build Host: build37
Group : System/Emulators/PC Source RPM: wine-1.1.39-3.1.src.rpm
Size : 90095910 License: LGPL, Other License(s), see package
Signature : DSA/SHA1, Tue 02 Mar 2010 03:54:16 PM CET, Key ID 8e5578b7233ab63d
URL : http://www.winehq.com
Summary : An MS Windows emulator
Description :
An MS Windows emulator, consisting of both runtime and also source
compatibility functions. You can run your MS executables with it, and
you can write your Windows programs under Linux and link against the
WINE libraries.
It is not necessary to have a Windows installation to run WINE.
Please have a look at /usr/share/doc/packages/wine/README.SuSE. There
is more documentation available in that directory. Read 'man wine' for
further information.
You can invoke wine by entering: 'wine program.exe' wine can be
configured by running 'winecfg'.
Distribution: Emulators:Wine / openSUSE_Factory
and from the openSUSE milestone-6 snapshot repos:
Name : wine Relocations: (not relocatable)
Version : 1.1.43 Vendor: openSUSE
Release : 1.3 Build Date: Tue 27 Apr 2010 05:37:40 PM CEST
Install Date: (not installed) Build Host: build32
Group : System/Emulators/PC Source RPM: wine-1.1.43-1.3.src.rpm
Size : 2407506 License: LGPLv2.1+
Signature : RSA/8, Tue 27 Apr 2010 05:42:10 PM CEST, Key ID b88b2fd43dbdc284
Packager : http://bugs.opensuse.org
URL : http://www.winehq.com
Summary : An MS Windows Emulator
Description :
An MS Windows emulator, consisting of both runtime and source
compatibility functions. You can run your MS executables with it and
write your Windows programs under Linux and link against the WINE
libraries.
It is not necessary to have a Windows installation to run WINE.
Refer to /usr/share/doc/packages/wine/README.SuSE. There is more
documentation available in that directory. Read 'man wine' for further
information.
You can invoke wine by entering 'wine program.exe'. Configure it by
running 'winecfg'.
Distribution: openSUSE Factory
hence based on the above, you should write a bug report on this wine dependency problem. There is guidance for writing bug reports here: Submitting Bug Reports - openSUSE Use your openSUSE forum user name and password when logging on to bugzilla. Check first to see if someone else has raised the bug report already.
Hi
Ahh libpng14, there have been issues with that noted on the packaging
mailing list (update to 1.4 branch) . You might want to browse the
March/April archives and either post a query there or use IRC.
After being utterly frustrated with Fedora, I have found a new sense of vigor for Linux w/SUSE…I’ve been on the site for a while, and the community seems to be exactly what I’m looking for to help me along with Linux…Thanks to all of the contributors who see this, I love the idea of growing into someone who can help someone in my position in the future…
I am having this exact same issue on my laptop, and am subscribing to this thread so I can catch wind of a fix…Thanks again to everyone, can’t wait to see how this gets solved…!