Fedora includes now a 64-bit Wine package (at least in F11) which of course breaks existing Wine setups. "yum install wine" will install the 64-bit version... Looks like we had our WineConf too late for this.
I have opened https://bugzilla.redhat.com/show_bug.cgi?id=533988 for this problem.
The quick fix is to just remove the wine*.x86_64 rpms and install the wine*.i586 instead.
bye michael
On Mon, Nov 9, 2009 at 5:54 PM, Michael Stefaniuc mstefani@redhat.com wrote:
Fedora includes now a 64-bit Wine package (at least in F11) which of course breaks existing Wine setups. "yum install wine" will install the 64-bit version... Looks like we had our WineConf too late for this.
I have opened https://bugzilla.redhat.com/show_bug.cgi?id=533988 for this problem.
The quick fix is to just remove the wine*.x86_64 rpms and install the wine*.i586 instead.
Actually, Roderick and I noticed this on IRC, with a user who couldn't get wine to run more than a couple times on a single prefix.
Austin English wrote:
On Mon, Nov 9, 2009 at 5:54 PM, Michael Stefaniuc mstefani@redhat.com wrote:
Fedora includes now a 64-bit Wine package (at least in F11) which of course breaks existing Wine setups. "yum install wine" will install the 64-bit version... Looks like we had our WineConf too late for this.
I have opened https://bugzilla.redhat.com/show_bug.cgi?id=533988 for this problem.
The quick fix is to just remove the wine*.x86_64 rpms and install the wine*.i586 instead.
Actually, Roderick and I noticed this on IRC, with a user who couldn't get wine to run more than a couple times on a single prefix.
Oh, I didn't claim that I found the problem. I have seen arethusa on #winehq helping users get rid of Wine in the 64-bit flavor from Fedora. I have just verified that "yum install wine" will indeed give a 64-bit Wine, checked the (rpm) spec file and opened a bug in the Fedora bugzilla.
Thanks for helping those users.
bye michael
"Michael" == Michael Stefaniuc mstefani@redhat.com writes:
Michael> Fedora includes now a 64-bit Wine package (at least in F11) Michael> which of course breaks existing Wine setups. "yum install wine" Michael> will install the 64-bit version... Looks like we had our Michael> WineConf too late for this.
Michael> I have opened Michael> https://bugzilla.redhat.com/show_bug.cgi?id=533988 for this Michael> problem.
Michael> The quick fix is to just remove the wine*.x86_64 rpms and Michael> install the wine*.i586 instead.
Did nobody of the packages test what they did?
On Tue, Nov 10, 2009 at 1:48 PM, Uwe Bonnes bon@elektron.ikp.physik.tu-darmstadt.de wrote:
"Michael" == Michael Stefaniuc mstefani@redhat.com writes:
Michael> Fedora includes now a 64-bit Wine package (at least in F11) Michael> which of course breaks existing Wine setups. "yum install wine" Michael> will install the 64-bit version... Looks like we had our Michael> WineConf too late for this.
Michael> I have opened Michael> https://bugzilla.redhat.com/show_bug.cgi?id=533988 for this Michael> problem.
Michael> The quick fix is to just remove the wine*.x86_64 rpms and Michael> install the wine*.i586 instead.
Did nobody of the packages test what they did?
No surprise there. At one point some distributions packaged wineserver as an /etc/init.d service, because it sounds like a system-wide server...
Autopackage had the right idea: the developers of a project should do the packaging.
-- Uwe Bonnes bon@elektron.ikp.physik.tu-darmstadt.de
Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
Damjan
Uwe Bonnes wrote:
"Michael" == Michael Stefaniuc mstefani@redhat.com writes:
Michael> Fedora includes now a 64-bit Wine package (at least in F11) Michael> which of course breaks existing Wine setups. "yum install wine" Michael> will install the 64-bit version... Looks like we had our Michael> WineConf too late for this. Michael> I have opened Michael> https://bugzilla.redhat.com/show_bug.cgi?id=533988 for this Michael> problem. Michael> The quick fix is to just remove the wine*.x86_64 rpms and Michael> install the wine*.i586 instead.
Did nobody of the packages test what they did?
It is easy to miss as it requires: - Fresh install of Wine (via PackageKit or yum install) and - Old 32-bit WINEPREFIX.
An update of Wine will pull the packages from the same arch aka i586 and thus the problem won't be visible for the people that just update their packages. That explains the limited outcry considering the impact of the problem.
bye michael
2009/11/10 Michael Stefaniuc mstefani@redhat.com:
Uwe Bonnes wrote:
Did nobody of the packages test what they did?
It is easy to miss as it requires:
- Fresh install of Wine (via PackageKit or yum install) and
- Old 32-bit WINEPREFIX.
Except that it's obvious that the packagers are not people who USE wine, or they would notice their ia32 Windows apps suddenly not running.