| Author |
Message |
Luis_P
|
|
|
Post subject: [Solved] Upgrading wine
Posted: 29.06.2012, 13:06
|
|

Joined: 2010-09-11
Posts: 142
Location: Barcelona, Spain
Status: Offline
|
|
From a while, when I do dist-upgrade, I get:
Code:
The following NEW packages will be instaled:
libeveldb1 ...
The following packages have been kept back:
wine
The following packages will be upgraded:
aspell-ca, audacity...
But wine is not on hold:
Code:
dpkg --get-selections| grep wine
libwine install
libwine-alsa install
libwine-bin install
libwine-cms install
libwine-gecko-unstable install
libwine-gl install
libwine-gphoto2 install
libwine-ldap install
libwine-openal install
libwine-print install
libwine-sane install
wine install
wine-bin install
wine-doc install
And
Code:
apt-cache policy wine
wine:
Installed: 1.2.3-0.3
Candidate: 1.4.1-1
Version table:
1.4.1-1.1 0
1 ftp://ftp.rediris.es/debian/ experimental/main amd64 Packages
1.4.1-1 0
500 ftp://ftp.rediris.es/debian/ sid/main amd64 Packages
*** 1.2.3-0.3 0
100 /var/lib/dpkg/status
I.e., there is a new version of wine trying to gain access my computer, but it cannot do.
Why?
The question is not rhetorical because I use wine a lot.
Best regards.
Luis_P |
Last edited by Luis_P on 02.07.2012, 10:03; edited 1 time in total
|
| |
|
|
|
 |
slh
|
|
Post subject: RE: Upgrading wine
Posted: 29.06.2012, 13:14
|
|

Joined: 2010-08-25
Posts: 585
Status: Offline
|
|
|
|
|
 |
Luis_P
|
|
Post subject:
Posted: 29.06.2012, 14:34
|
|

Joined: 2010-09-11
Posts: 142
Location: Barcelona, Spain
Status: Offline
|
|
Thanks, slh, for the information.
I've read the beginning of DonKult's post, but when I read the big and red warning: possibly breaking your system! I get away.
Then, I am into a dilemma: I need use wine, but I don't want break my system. What must I do?
Well, the world is not for timid people; therefore I will install i386 architecture. I suppose I can revert it if necessary. Will it be possible?
Will be continued. |
|
|
| |
|
|
|
 |
slh
|
|
Post subject:
Posted: 29.06.2012, 17:36
|
|

Joined: 2010-08-25
Posts: 585
Status: Offline
|
|
| Recent wine packages on amd64 require multi-arch, there is no alternative. Wine was one of the driving factors for multi-arch, because of the nastiness of its dependencies (ia32libs, which is now gone for good and replaced by pulling in the i386 packages directly via multi-arch). |
|
|
| |
|
|
|
 |
oldie
|
|
Post subject:
Posted: 29.06.2012, 21:18
|
|

Joined: 2010-09-12
Posts: 23
Status: Offline
|
|
| right - but not easy for apt-get |
|
|
| |
|
|
|
 |
slh
|
|
Post subject:
Posted: 30.06.2012, 00:25
|
|

Joined: 2010-08-25
Posts: 585
Status: Offline
|
|
| It is not apt's job to configure the systems for multi-arch, that is a decision which has to be done manually by the system administrator. apt can just, based on the package interdepencies, try to avoid the big boom (not upgrading wine on itself, while not removing the old versions) before multi-arch is enabled - and try to recover once multi-arch has been enabled by the local administrator. If that fails, the involved packages and their stated dependencies are to be blamed, not apt. |
|
|
| |
|
|
|
 |
DonKult
|
|
Post subject:
Posted: 01.07.2012, 15:55
|
|
Team Member

Joined: 2010-09-02
Posts: 417
Status: Offline
|
|
|
Luis_P wrote:
I've read the beginning of DonKult's post, but when I read the big and red warning: possibly breaking your system! I get away.
Then, I am into a dilemma: I need use wine, but I don't want break my system. What must I do?
I have expanded the topic a bit, hopefully its clearer now what i meant. It is unlikely that you break your system behind repair - or at all - if you are careful. If you are just hitting Enter every time APT asks a question on the other hand …
It is also more likely that you will hit bugs in packaging given that this is new and many maintainers have to learn this. wine went through quiet a few iterations before it reached the current state - which works fine on my system for the record.
You are running an unstable, so you have to expect a few bugs here and there. If you are prepared for this, go ahead. With more time and more people using it the chance to hit a bug in this configuration will be as low as hitting a bug before MultiArch.
Luis_P wrote:
Well, the world is not for timid people; therefore I will install i386 architecture. I suppose I can revert it if necessary. Will it be possible?
No, you can't (easily) revert that step. You have to remove all packages of the "foreign" architectures and only then you can remove the architecture from dpkg. Otherwise bad things will happen - but you don't want that anyway. MultiArch is the way to go, it is just the new kid on the block, so we have to be a bit more careful than usual before we all know each other better.  |
_________________ MfG. DonKult
"I never make stupid mistakes. Only very, very clever ones." ~ The Doctor
|
| |
|
|
|
 |
Luis_P
|
|
Post subject:
Posted: 02.07.2012, 10:02
|
|

Joined: 2010-09-11
Posts: 142
Location: Barcelona, Spain
Status: Offline
|
|
I've carried out i386 architecture and installed wine 1.4.1-1: all ran smoothly.
If I well understood it, the only package with "odd" architecture is now wine (and its brother wine-bin). If so, apt-get dist-upgrade will update also wine and only bugs on these packages can affect my system (affection due to new arch, I mean).
Thanks everybody for your support.
Luis_P |
|
|
| |
|
|
|
 |
|
|