Ok, it looks like I've completely boloxed up my wine install on this box. I'm running RH 8.0 on an i386 machine and can't seem to find key components. I've tried removing the previous incarnations using rpm, but the files still seem to be there from an old install from 2003. If I just wanted to completely wipe wine off this thing and start fresh with a completely new install, what would be the best way to do it since it appears rpm isn't working? Maybe the next question should be, do I need to do that? I just downloaded the latest rpm for rh8 and I got several complaints from rpm that several files were in conflict with the previous version which was from 20040121...so I forced the install with rpm -ivh --force wine20040213-1rh8winehq.i386.rpm and it installed with no complaints. However, I can now no longer locate tools/wineinstall anywhere on this box. Do I still need it? This is coming from a wine newbie and Linux novice. Short of completely reinstalling everything else and starting over, is there another way to get this done? Thanks, Wayne
Joachim von Thadden
2004-Feb-19 01:58 UTC
How do you completely remove wine and start over?
Am Thu, Feb 19, 2004 at 12:09:46AM -0600 schrieb Wayne Dahl:> Ok, it looks like I've completely boloxed up my wine install on this > box. I'm running RH 8.0 on an i386 machine and can't seem to find key > components. I've tried removing the previous incarnations using rpm, > but the files still seem to be there from an old install from 2003. > > If I just wanted to completely wipe wine off this thing and start fresh > with a completely new install, what would be the best way to do it since > it appears rpm isn't working? > > Maybe the next question should be, do I need to do that? I just > downloaded the latest rpm for rh8 and I got several complaints from rpm > that several files were in conflict with the previous version which was > from 20040121...so I forced the install with rpm -ivh --force > wine20040213-1rh8winehq.i386.rpm and it installed with no complaints. > However, I can now no longer locate tools/wineinstall anywhere on this > box. Do I still need it? This is coming from a wine newbie and Linux > novice.Hmmm, I don't understand why you are messing up your RPM system? Linux is not Windows. You should understand what you do! OK, sorry for that, it's a little bit early in the morning for me. What I see from your mail is that you installed a new wine version with rpm -i <file> over your existing older version. If you would have used rpm -u <file> you would not got these messages about conflicts with existing files from another rpm package. Because with -i you install new software whereas with -u you just update. It is very likely that you now have both versions mixed together on your system. Check this by giving rpm -q wine and see whether you get both, the old and the new version. If it is like this, do rpm -e <last-version> (20040212) and the rpm -e <existing-version> (20040121). If there were any other versions, delete them also. Then (after some errors) all versions should be deleted from your system. If you now delete the .wine directory of your user you have a clean system. Now install the version of wine you really want. I recommend the 20031212 build. Anyway, these are my recommendation for you for the future: - read about rpm (man, google) to understand - you can almost always use rpm -u (also for new packages) - don't mess around with --force and --nodeps if you are not absolutely sure what you are doing: you may break your system with that - install non-RPM software under /usr/local - use the 20031212 version of wine as this one is known to work best until now> Short of completely reinstalling everything else and starting over, is > there another way to get this done?As I mentioned above: You are using Linux. There is no need to start over with a new system or reinstall everything like you have to do with Windows after you installed a few programs which completely mess up your libraries. Regards Joachim -- "Never touch a running system! Never run a touching system? Never run a touchy system!!!"
Ivan Leo Murray-Smith
2004-Feb-19 10:16 UTC
How do you completely remove wine and start over?
> Do I still need it?No, wineinstall is only needed if installing from the source code. Ivan.
On Thu, 2004-02-19 at 01:58, Joachim von Thadden wrote:> What I see from your mail is that you installed a new wine version with > rpm -i <file> over your existing older version. If you would have used > rpm -u <file> you would not got these messages about conflicts with > existing files from another rpm package. Because with -i you install new > software whereas with -u you just update. It is very likely that you now > have both versions mixed together on your system. Check this by giving > rpm -q wine and see whether you get both, the old and the new version.I was following the install directions given at http://www.winehq.org/site/docs/wine-user/installing#AEN481 and the instructions to do rpm -qa|grep -i wine never returned anything. I think this is why I had two different versions installed on this box. Your instructions were MUCH more helpful.> If it is like this, do rpm -e <last-version> (20040212) and the rpm -e > <existing-version> (20040121). If there were any other versions, delete > them also. Then (after some errors) all versions should be deleted from > your system. If you now delete the .wine directory of your user you have > a clean system. Now install the version of wine you really want. I > recommend the 20031212 build.Ok, after doing the above, I still cannot locate tools/wineinstall. Is it not installed or necessary with the rpms? It's been so long since I first installed on this machine, I may have installed from a tarball before instead of an rpm, but I can't remember. Thanks for your help Joachim. I'll probably be sending more requests for help in the future...and here's a question that I've had for a while. I have a native Win98 partition on this box (was a Win98 box before I installed Linux on it) on /mnt/hda1, but have had little luck running applications already installed there using the native environment. About the only app I've got running is mIRC, the IRC client. Applications that use say, Internet Explorer, and make calls to it, will they work with wine? I'm thinking of something like Intellicasts desktop weather display...if you click on the map on the front of their display, it calls IE to pull up the weather map. I couldn't really care less about using it, but I can't get my wife to stop...if I could get this stuff working for her in Linux, she'd have no reason to boot up the Win98 box. Thanks again, Wayne
Ivan Leo Murray-Smith
2004-Feb-19 16:22 UTC
How do you completely remove wine and start over?
> Ok, after doing the above, I still cannot locate tools/wineinstall. Is > it not installed or necessary with the rpms?wineinstall is only needed for source code install, no need for it if you're using RPMs. Download winesetuptk from http://sourceforge.net/project/showfiles.php?group_id=6241 install it and run it, you can use it to configure wine to use the windows partition. Ivan.
Hi Wayne, If the leftover files you are talking about are the ones in the /usr/src directory because you originally installed it **from a .src.rpm**, I have just gone and deleted those all from the SPECS/RPMS/BUILD etc... directories after uninstalling the package. To me, they seem like leftover installation files once the package is installed. You may first want to find out if this is OK to do (for any .src.rpm package for that matter). This is from one newbie to another, so take it with a grain of salt. However, if you just installed wine from an ordinary .i386.rpm, (not a source rpm), then just remove your .wine directory (rm -rf ~/.wine) and type "wine" and it will be created anew. then you can edit the config file and do a "wineboot". You will loose all your programs installed on the fake win drive and any customizations you made in the config file.