Has Wine been removed from Debian?
Running 6.0.7. This morning, I did an aptitude update, followed by: # aptitude safe-upgrade Resolving dependencies... The following packages will be REMOVED: libwine{u} libwine-alsa{u} libwine-cms{u} libwine-gl{u} libwine-gphoto2{u} libwine-ldap{u} libwine-print{u} libwine-sane{u} wine{u} wine-bin{u} wine-utils{u} The following packages will be upgraded: libapache2-mod-php5 libpoppler-glib4 libpoppler-qt4-3 libpoppler5 php5-cli php5-common playonlinux poppler-utils 8 packages upgraded, 0 newly installed, 11 to remove and 1 not upgraded. Need to get 12.8 MB of archives. After unpacking 53.0 MB will be freed. Do you want to continue? [Y/n/?] What gives? Has Wine been removed from the distribution? Just wondering. I don't really use it, and since I use Playonlinux for what little Wine-based stuff I dork around with (which will download and install various versions of Wine under your home directory), I'm not that worried. But I did think it kind of odd that aptitude now wants to remove it. --Dave smime.p7s Description: S/MIME Cryptographic Signature
Re: Has Wine been removed from Debian?
David Guntner grabbed a keyboard and wrote: Running 6.0.7. This morning, I did an aptitude update, followed by: # aptitude safe-upgrade Resolving dependencies... The following packages will be REMOVED: libwine{u} libwine-alsa{u} libwine-cms{u} libwine-gl{u} libwine-gphoto2{u} libwine-ldap{u} libwine-print{u} libwine-sane{u} wine{u} wine-bin{u} wine-utils{u} The following packages will be upgraded: libapache2-mod-php5 libpoppler-glib4 libpoppler-qt4-3 libpoppler5 php5-cli php5-common playonlinux poppler-utils 8 packages upgraded, 0 newly installed, 11 to remove and 1 not upgraded. Need to get 12.8 MB of archives. After unpacking 53.0 MB will be freed. Do you want to continue? [Y/n/?] What gives? Has Wine been removed from the distribution? Just wondering. I don't really use it, and since I use Playonlinux for what little Wine-based stuff I dork around with (which will download and install various versions of Wine under your home directory), I'm not that worried. But I did think it kind of odd that aptitude now wants to remove it. Well, heck. I just noticed that one of the things being upgraded is the afore-mentioned Playonlinux. Maybe there's something about that package upgrade that decided to remove the system-wide Wine since it'll work with the version(s) of Wine it will install for you. Sorry for the list clutter. :-) --Dave smime.p7s Description: S/MIME Cryptographic Signature
Re: Has Wine been removed from Debian?
David Guntner: Running 6.0.7. This morning, I did an aptitude update, followed by: # aptitude safe-upgrade Resolving dependencies... The following packages will be REMOVED: libwine{u} libwine-alsa{u} libwine-cms{u} libwine-gl{u} libwine-gphoto2{u} libwine-ldap{u} libwine-print{u} libwine-sane{u} wine{u} wine-bin{u} wine-utils{u} Wow. So much for the safe in safe-upgrade. Looks like a reason to ditch aptitude. And, just BTW: even if a package is removed from Debian's repositories, that doesn't mean apt(itude) automatically removes it from your system. That would be really horrible behaviour. J. -- I feel yawning hollowness whilst talking to people at parties. [Agree] [Disagree] http://www.slowlydownward.com/NODATA/data_enter2.html signature.asc Description: Digital signature
Re: Has Wine been removed from Debian?
Jochen Spieker grabbed a keyboard and wrote: David Guntner: Running 6.0.7. This morning, I did an aptitude update, followed by: # aptitude safe-upgrade Resolving dependencies... The following packages will be REMOVED: libwine{u} libwine-alsa{u} libwine-cms{u} libwine-gl{u} libwine-gphoto2{u} libwine-ldap{u} libwine-print{u} libwine-sane{u} wine{u} wine-bin{u} wine-utils{u} Wow. So much for the safe in safe-upgrade. Looks like a reason to ditch aptitude. And, just BTW: even if a package is removed from Debian's repositories, that doesn't mean apt(itude) automatically removes it from your system. That would be really horrible behaviour. Hopefully, by now you'll have read my followup to myself. :-) I think it may be related to the Playonlinux package, for reasons mentioned there. And aptitude works just fine. :-) --Dave smime.p7s Description: S/MIME Cryptographic Signature
Re: Has Wine been removed from Debian?
On 2013-07-18 17:38 +0200, Jochen Spieker wrote: David Guntner: Running 6.0.7. This morning, I did an aptitude update, followed by: # aptitude safe-upgrade Resolving dependencies... The following packages will be REMOVED: libwine{u} libwine-alsa{u} libwine-cms{u} libwine-gl{u} libwine-gphoto2{u} libwine-ldap{u} libwine-print{u} libwine-sane{u} wine{u} wine-bin{u} wine-utils{u} Wow. So much for the safe in safe-upgrade. Looks like a reason to ditch aptitude. Absolutely not, the correct thing is to run aptitude unmarkauto wine. Removing unused packages automatically is usually what you want. And, just BTW: even if a package is removed from Debian's repositories, that doesn't mean apt(itude) automatically removes it from your system. That would be really horrible behaviour. Right. Cheers, Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87zjtjkgov@turtle.gmx.de
Re: Has Wine been removed from Debian?
Sven Joachim grabbed a keyboard and wrote: Absolutely not, the correct thing is to run aptitude unmarkauto wine. Removing unused packages automatically is usually what you want. Thanks for that - handy information to have for future reference! --Dave smime.p7s Description: S/MIME Cryptographic Signature
Re: Has Wine been removed from Debian?
Hi, Le 18/07/2013 16:53, David Guntner a écrit : Running 6.0.7. This morning, I did an aptitude update, followed by: # aptitude safe-upgrade Resolving dependencies... The following packages will be REMOVED: libwine{u} libwine-alsa{u} libwine-cms{u} libwine-gl{u} libwine-gphoto2{u} libwine-ldap{u} libwine-print{u} libwine-sane{u} wine{u} wine-bin{u} wine-utils{u} {u} means that the wine package has been installed to resolve a dependency and now that this dependency is gone it wants to remove wine. To fix this you could do: aptitude unmarkauto wine. If you want to know why it is installed: aptitude why wine. Cheers, Jérôme -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51e80e5e.9080...@actimage.com
Re: Has Wine been removed from Debian?
Jérôme Heil grabbed a keyboard and wrote: {u} means that the wine package has been installed to resolve a dependency and now that this dependency is gone it wants to remove wine. To fix this you could do: aptitude unmarkauto wine. If you want to know why it is installed: aptitude why wine. AH! Another good command to know about. Thanks for that! (*long*-time *NIX Linux user, but fairly new to Debian) --Dave smime.p7s Description: S/MIME Cryptographic Signature
Re: Has Wine been removed from Debian?
Sven Joachim: On 2013-07-18 17:38 +0200, Jochen Spieker wrote: David Guntner: Running 6.0.7. This morning, I did an aptitude update, followed by: # aptitude safe-upgrade Resolving dependencies... The following packages will be REMOVED: libwine{u} libwine-alsa{u} libwine-cms{u} libwine-gl{u} libwine-gphoto2{u} libwine-ldap{u} libwine-print{u} libwine-sane{u} wine{u} wine-bin{u} wine-utils{u} Wow. So much for the safe in safe-upgrade. Looks like a reason to ditch aptitude. Absolutely not, the correct thing is to run aptitude unmarkauto wine. Removing unused packages automatically is usually what you want. Thanks, you are right. I missed the {u} flags. J. -- Scientists know what they are talking about. [Agree] [Disagree] http://www.slowlydownward.com/NODATA/data_enter2.html signature.asc Description: Digital signature