Uninstall old wine version and install new version

[Bakshara]

I did a forum search and found 16 pages for uninstalling wine. Only one was semi-helpful.

What I got was:

[Bakshara@Bakshara ~]$ rmdir ~/.wine
rmdir: failed to remove `/home/Bakshara/.wine': Directory not empty

What do I need to do?

I want to uninstall wine 1.1.24 and install 1.1.26. I currently only have three apps installed. So any thing I will loose will be easy to reinstall.

Bakshara the Linux noob!

[John Drescher]

I did a forum search and found 16 pages for uninstalling wine. Only one was semi-helpful.

What I got was:

[Bakshara@Bakshara ~]$ rmdir ~/.wine
rmdir: failed to remove `/home/Bakshara/.wine': Directory not empty

This is not about uninstalling wine. Its about deleting your installed
applications to start with a clean wine prefix. In most cases this is
unnecessary. For example I am using the same prefix for the last 3
years. I have created additional prefixes to test applicatoions but I
have not deleted .wine and the applications I installed with whatever
wine version existed at that time still work..

What do I need to do?

I want to uninstall wine 1.1.24 and install 1.1.26.

Generally your package manager does this for you. How did you install wine?

I currently only have three apps installed. So any thing I will loose will be easy to reinstall.

As I said before you do not need to do this. The wine installation is
in no way tied to your wine prefix so you can leave the installed
applications alone and still upgrade wine.

John

[austin987]

On Fri, Jul 31, 2009 at 10:08 AM, Bakshara<[email protected]> wrote:

I did a forum search and found 16 pages for uninstalling wine. Only one was semi-helpful.

What I got was:

[Bakshara@Bakshara ~]$ rmdir ~/.wine
rmdir: failed to remove `/home/Bakshara/.wine': Directory not empty

rmdir only removes empty directories. Use 'rm -rf ~/.wine' instead.


--
-Austin

[Bakshara]

On Fri, Jul 31, 2009 at 10:08 AM, Bakshara<[email protected]> wrote:
...
rmdir only removes empty directories. Use 'rm -rf ~/.wine' instead.
...
-Austin

From: http://wiki.winehq.org/HowTo

Wine HowTo

Before you install Wine, make sure that there is no previous Wine installation on your system, either from a package or from source. If you haven't yet installed Wine, you should be fine. See the Removing old Wine versions chapter in the User Guide for details.Many Linux distributions come with an included Wine package, but due to Wine's rapid development rate these are usually old and often broken versions. It is best to uninstall your distribution's included package versions and update to the latest Wine version available here.

That says,

To uninstall Wine from source, once again navigate to the same source folder that you used to install Wine using the terminal. Then, run the following command:

Code: Select all

# make uninstall

The response I get from trying is:

[root@Bakshara lib]# make uninstall
make: *** No rule to make target `uninstall'. Stop.
[root@Bakshara lib]# make uninstall ./wine
make: *** No rule to make target `uninstall'. Stop.
[root@Bakshara lib]# make uninstall ./wine
make: *** No rule to make target `uninstall'. Stop.
[root@Bakshara lib]# make uninstall ~/.wine
make: *** No rule to make target `uninstall'. Stop.
[root@Bakshara lib]# make uninstall ~/wine
make: *** No rule to make target `uninstall'. Stop.
[root@Bakshara lib]# make uninstall /wine
make: *** No rule to make target `uninstall'. Stop.
[root@Bakshara lib]# make uninstall wine
make: *** No rule to make target `uninstall'. Stop.
[root@Bakshara lib]#

Doing

Code: Select all

rm -rf ~/.wine

Gives me this, but still has 386 items under it.

Code: Select all

[root@Bakshara lib]# rm -rf ~/.wine
[root@Bakshara lib]# 

[austin987]

On Fri, Jul 31, 2009 at 10:30 PM, Bakshara<[email protected]> wrote:

austin987 wrote:

On Fri, Jul 31, 2009 at 10:08 AM, Bakshara<[email protected]> wrote:
...
rmdir only removes empty directories. Use 'rm -rf ~/.wine' instead.
...
-Austin

From: http://wiki.winehq.org/HowTo

Wine HowTo

Before you install Wine, make sure that there is no previous Wine installation on your system, either from a package or from source. If you haven't yet installed Wine, you should be fine. See the Removing old Wine versions chapter in the User Guide for details.Many Linux distributions come with an included Wine package, but due to Wine's rapid development rate these are usually old and often broken versions. It is best to uninstall your distribution's included package versions and update to the latest Wine version available here.

That says,

To uninstall Wine from source, once again navigate to the same source folder that you used to install Wine using the terminal. Then, run the following command:

Code:

# make uninstall

The response I get from trying is:

[root@Bakshara lib]# make uninstall
make: *** No rule to make target `uninstall'.  Stop.

Did you install from source? Try './configure' first.

What does `which -a wine` show?

Doing

Code:

rm -rf ~/.wine



Gives me this, but still has 386 items under it.

Code:

[root@Bakshara lib]# rm -rf ~/.wine
[root@Bakshara lib]#

What does:
$ rm -rf ~/.wine && ls -al ~/.wine

show?

--
-Austin

[Gert van den Berg]

On Sat, Aug 1, 2009 at 05:30, Bakshara<[email protected]> wrote:

Code:

rm -rf ~/.wine

Gives me this, but still has 386 items under it.

Code:

[root@Bakshara lib]# rm -rf ~/.wine
[root@Bakshara lib]#

You're running it as the wrong user. The above deleted root's default
WINEPREFIX.

(Each user has its own WINEPREFIX)

(sudo should work, since ~ is expanded by the shell. AFAIK it only
works in bash, you need to use $HOME in other cases)

[Bakshara]

Gert van den Berg,

You're running it as the wrong user. The above deleted root's default
WINEPREFIX.

I am the only user.

What is "$HOME?" How do I get to it?

There are currently six "WINEPREFIX" files: three are "shell scrip", two are "Troff documents", and one is "Gzip archive."
wineprefixcreate
wineprefixcreate.1.gz
wineprefixcreate.in
wineprefixcreate.in
wineprefixcreate.man.in
wineprefixcreate.man.in

austin987,
These are the two:

Code: Select all

[Bakshara@Bakshara ~]$ rm -rf ~/.wine

usr/lib/wine <- 386 items still
???/wine <- 3 items still
???/wine <- 5 items still
???/wine-core-1.1.23 <- 21 items still
???/wine-pulseaudio-1.1.23 <- 21 items still

Code: Select all

[Bakshara@Bakshara ~]$ su -
Password: 
[root@Bakshara ~]# rm -rf ~/.wine
[root@Bakshara ~]# 

usr/lib/wine <- 386 items still
???/wine <- 3 items still
???/wine <- 5 items still
???/wine-core-1.1.23 <- 21 items still
???/wine-pulseaudio-1.1.23 <- 21 items still

As "[Bakshara@Bakshara ~]"

Code: Select all

./configure

bash: ./configure: No such file or directory

Code: Select all

which -a wine
/usr/bin/wine

shows 2,210 items

Code: Select all

rm -rf ~/.wine && ls -al ~/.wine 

ls: cannot access /home/Bakshara/.wine: No such file or directory

As "[root@Bakshara ~]"

Code: Select all

./configure

-bash: ./configure: No such file or directory

Code: Select all

which -a wine
/usr/bin/wine

shows 2,210 items

Code: Select all

rm -rf ~/.wine && ls -al ~/.wine 

ls: cannot access /root/.wine: No such file or directory

Nearly the same response as me or root.

Everyone,
NOTE:
Eleven wine files under:
var/lib/yum/yumdb/(hex string)-wine-????-1.1.23.fc11-i586
????=ldap, twain, cms, desktop, nas, esd, tools, capi, jake, core, pulseaudio
What are these?

[Gert van den Berg]

On Tue, Aug 4, 2009 at 05:33, Bakshara<[email protected]> wrote:

Gert van den Berg,

You're running it as the wrong user. The above deleted root's default
WINEPREFIX.

I am the only user.

What is "$HOME?" How do I get to it?

$ echo $HOME
http://en.wikibooks.org/wiki/Guide_to_U ... _Variables

There are currently six "WINEPREFIX" files: three are "shell scrip", two are "Troff documents", and one is "Gzip archive."
wineprefixcreate
wineprefixcreate.1.gz
wineprefixcreate.in
wineprefixcreate.in
wineprefixcreate.man.in
wineprefixcreate.man.in

These are related to your Wine installation not the Wine settings /
data files that I commented on

If you want to remove / upgrade Wine itself: How did you install Wine?
If it was not from source, your distribution's documentation is
probably the place to start.

[Gert van den Berg]

On Tue, Aug 4, 2009 at 05:33, Bakshara<[email protected]> wrote:

Gert van den Berg,

You're running it as the wrong user. The above deleted root's default
WINEPREFIX.

I am the only user.

What is "$HOME?" How do I get to it?

$ echo $HOME
http://en.wikibooks.org/wiki/Guide_to_U ... _Variables

There are currently six "WINEPREFIX" files: three are "shell scrip", two are "Troff documents", and one is "Gzip archive."
wineprefixcreate
wineprefixcreate.1.gz
wineprefixcreate.in
wineprefixcreate.in
wineprefixcreate.man.in
wineprefixcreate.man.in

These are related to your Wine installation not the Wine settings /
data files that I commented on

If you want to remove / upgrade Wine itself: How did you install Wine?
If it was not from source, your distribution's documentation is
probably the place to start.

[austin987]

On Mon, Aug 3, 2009 at 10:33 PM, Bakshara<[email protected]> wrote:

Eleven wine files under:
var/lib/yum/yumdb/(hex string)-wine-????-1.1.23.fc11-i586
????=ldap, twain, cms, desktop, nas, esd, tools, capi, jake, core, pulseaudio
What are these?

I don't know RPM distros well, but does:
$ sudo yum remove wine*

help?

--
-Austin

[Martin Gregorie]

On Tue, 2009-08-04 at 01:23 -0500, Austin English wrote:

On Mon, Aug 3, 2009 at 10:33 PM, Bakshara<[email protected]> wrote:

Eleven wine files under:
var/lib/yum/yumdb/(hex string)-wine-????-1.1.23.fc11-i586
????=ldap, twain, cms, desktop, nas, esd, tools, capi, jake, core, pulseaudio
What are these?

I don't know RPM distros well, but does:
$ sudo yum remove wine*

You shouldn't use the glob (*). yum expects the package name(s) you
supply to be an exact match on the initial part of the name - the
remainder of the name gives the package's target hardware, version and
the Fedora distribution containing it. To check that wine, rpm and rpm
development tools are installed via Fedora packages:

$ sudo yum list wine rpm rpm-devel
Installed Packages
rpm.i386 4.4.2.2-7.fc8 installed
rpm-devel.i386 4.4.2.2-7.fc8 installed
wine.i386 1.1.9-2.fc8 installed
$

Use the same name to install, uninstall or upgrade packages:

sudo yum remove wine # uninstall wine
sudo yum install wine # (re)install wine
sudo yum upgrade wine # make sure you have the latest package wine

Install and upgrade will automatically handle dependencies.


Martin

[Martin Gregorie]

On Tue, 2009-08-04 at 10:38 +0100, Martin Gregorie wrote:

You shouldn't use the glob (*)

Correction - the glob does act on the package name:

$ sudo yum list wine rpm*
Password:
Installed Packages
rpm.i386 4.4.2.2-7.fc8 installed
rpm-build.i386 4.4.2.2-7.fc8 installed
rpm-devel.i386 4.4.2.2-7.fc8 installed
rpm-libs.i386 4.4.2.2-7.fc8 installed
rpm-python.i386 4.4.2.2-7.fc8 installed
rpmdevtools.noarch 6.4-1.fc8 installed
rpmlint.noarch 0.83-1.fc8 installed
wine.i386 1.1.9-2.fc8 installed
Available Packages
rpm-apidocs.i386 4.4.2.2-7.fc8 updates-newkey
rpmreaper.i386 0.1.5-1.fc8 updates-newkey
rpmrebuild.noarch 2.2.2-1.fc8 updates-newkey

.... but, you'll notice has no effect on wins as there are no related
packages - in the Fedora distro anyway. I should have checked that
earlier. Apologies.

Martin

[Bakshara]

Gert van den Berg,

Code: Select all

[Bakshara@Bakshara ~]$ echo $HOME
/home/Bakshara
[Bakshara@Bakshara ~]$ 

Under that I found

/download/wine-1.1.24.tar.bz2
/download/WineInstallLog
/Misc/Need2Scan/Linux/Wine/x86
50ComUpd.Exe
ReadMe.Txt
License.Txt
redist.txt
.config/menus/applications-merged
win-Programs-???
.local/share/applications/wine/Programs/???

???=Fantasy Grounds, M$ Office Powerpoint. M$ XML Parser, WinRAR

austin987,
I tried this:

Code: Select all

[Bakshara@Bakshara ~]$ sudo yum remove wine*
[sudo] password for Bakshara: 
Bakshara is not in the sudoers file.  This incident will be reported.

...and this: (It is VERY LOOOOOOOOOOOOOOOOOOOOONG, so I cut A LOT!)

Code: Select all

[root@Bakshara ~]# sudo yum remove wine*

Loaded plugins: dellsysidplugin2, refresh-packagekit
Setting up Remove Process
Resolving Dependencies
There are unfinished transactions remaining. You might consider running yum-complete-transaction first to finish them.
--> Running transaction check
---> Package wine-capi.i586 0:1.1.23-1.fc11 set to be erased
...
---> Package wine-twain.i586 0:1.1.23-1.fc11 set to be erased
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
Package Arch Version Repository Size
================================================================================
Removing:
wine-capi i586 1.1.23-1.fc11 installed 79 k
...
wine-twain i586 1.1.23-1.fc11 installed 203 k

Transaction Summary
================================================================================
Install 0 Package(s)
Update 0 Package(s)
Remove 11 Package(s)

Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Erasing : wine-capi-1.1.23-1.fc11.i586 1/11
...
Erasing : wine-desktop-1.1.23-1.fc11.i586 11/11

Removed:
wine-capi.i586 0:1.1.23-1.fc11 wine-cms.i586 0:1.1.23-1.fc11
...
wine-twain.i586 0:1.1.23-1.fc11

Complete!
[root@Bakshara ~]#

That did it!

Thank you!!!

[James McKenzie]

Bakshara wrote:

Gert van den Berg,

Code:

[Bakshara@Bakshara ~]$ echo $HOME
/home/Bakshara
[Bakshara@Bakshara ~]$



Under that I found

/download/wine-1.1.24.tar.bz2
/download/WineInstallLog
/Misc/Need2Scan/Linux/Wine/x86
50ComUpd.Exe
ReadMe.Txt
License.Txt
redist.txt
.config/menus/applications-merged
win-Programs-???
.local/share/applications/wine/Programs/???

???=Fantasy Grounds, M$ Office Powerpoint. M$ XML Parser, WinRAR

austin987,
I tried this:

Code:

[Bakshara@Bakshara ~]$ sudo yum remove wine*
[sudo] password for Bakshara:
Bakshara is not in the sudoers file. This incident will be reported.



...and this: (It is VERY LOOOOOOOOOOOOOOOOOOOOONG, so I cut A LOT!)

Code:

[root@Bakshara ~]# sudo yum remove wine*

Sudo is not required if you are logged in as root. Now go back and
install, run and do whatever else you need to do as a non-root user.

If Wine will not install for a non-root user, install it as root, but DO
NOT RUN IT AS ROOT! This causes many problems.

James McKenzie