You are not logged in.
Solved: I did "aptitude search wine" and found out i had "wine-bin" installed. When I removed it it also removed lmms. So I guess my installation of lmms also installed wine.
I don't recall installing it and when I do 'sudo apt-get remove wine' it just says 0 files removed. How do I remove it? I know I can just delete /usr/bin/wine but at least on windows that is an incorrect way to remove software.
Last edited by WASD (2011-08-02 22:59:53)
Offline
That's the output of
apt-cache policy wineSweaty lads picking up the soap | I love the new "Ignore user" button
Offline
Output of "apt-cache policy wine":
wine:
Installed: (none)
Candidate: 1.0.1-3.1
Version table:
1.0.1-3.1 0
100 http://ftp.de.debian.org/debian/ squeeze/main amd64 Packages
Output of "sudo apt-get remove wine":
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package wine is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Last edited by WASD (2011-08-02 01:01:49)
Offline
doesn't look like it's installed or your apt-cache policy would look like
Installed: 1.0.1-3.1
Candidate: 1.0.1-3.1
Version table:
*** 1.0.1-3.1 0
100 http://ftp.de.debian.org/debian/ squeeze/main amd64 Packages
My guess is it got installed somehow and you used "apt-get remove" rather than "apt-get purge wine" (which also deletes configuration files/folders). If you try "apt-get purge wine", it should delete the folder automatically (though I can't remember if this works if it's already uninstalled)...
Last edited by punk_physicist (2011-08-02 02:56:38)
Offline
What i would recommend you do is reinstall the meta package and then use deb foster to purge it our completely. Ive had to do it a couple of times when i was first starting to use linux thinking that removing the meta removed the program.
"'If fighting is to result in victory, then you must fight'...Sun Tzu said that and id say he knows a little more about fighting then you do pal."
- TF2 Soldier
Offline
Also good practice is to run 'apt-get autoremove' after removing a package, this will remove any dependencies or recommended packages that were installed automatically with a package you installed that has since been removed...
For instance if I apt-get install wine, then APT will install 19 new packages. Now if I apt-get remove (or purge) wine only 1 package will be removed leaving 18 that I don't need... now if after removing wine I "apt-get autoremove" the other 18 packages will be removed for me (so I don't have to search and find packages... and not all of them will have wine in the name so searching will be difficult to find them all manually anyways)
Offline
Or, what you could do is use Aptitude (it's not installed by default I believe). It's much better than apt-get ;D
Check out Musik - an easy-to-use text-to-music converter!
Join SpiderOak using this link and get an extra 1 GB free: https://spideroak.com/download/referral … 660e787ff1
Offline
Could you please mark the thread as solved by editing the title of your initial post? Thanks! 
Check out Musik - an easy-to-use text-to-music converter!
Join SpiderOak using this link and get an extra 1 GB free: https://spideroak.com/download/referral … 660e787ff1
Offline
Or, what you could do is use Aptitude (it's not installed by default I believe). It's much better than apt-get ;D
Of course aptitude is part of a standard CrunchBang install, as it is in just about all other Debian-based distros; apt-get just seems to be the preferred front-end for apt right now. The curses interface for aptitude is kinda nice though, if butt-ugly; it's sorta like Synaptic, but in a terminal. Some prefer aptitude, some prefer apt-get; general consensus is that you should commit to one or the other, because they don't keep track installed packages exactly the same way.
Anyway, yes, it's good practice to run both `apt-get autoremove` (or `apt-get autoremove --purge` if you want to get rid of config files as well) and `apt-get clean` after removing a package using apt-get. (If you use aptitude, it automatically removes unnecessary dependencies, so it doesn't have an autoremove option.)
Offline
Some prefer aptitude, some prefer apt-get; general consensus is that you should commit to one or the other, because they don't keep track installed packages exactly the same way.
AFAIK this is no longer true, as it says here:
...I want to make it clear that you can use both [apt-get and aptitude] and mix them without problems. It used to be annoying when apt-get did not track which packages were automatically installed while aptitude did, but now that both packages share this list, there’s no reason to avoid switching back and forth.
In general, I've always liked (and prefer) apt-get, but this article makes a good (and unbiased) quick explanation of the relative strengths and merits of either method of package management...
Offline
Could you please mark the thread as solved by editing the title of your initial post? Thanks!
I've done that already. But I put [Solved] in the end of the title. I'll move it to the front now 
Offline
Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.