| Author |
Message |
Luis_P
|
|
Post subject: Problem with libwine [Solved]
 Posted: 25.05.2015, 08:43
|
|
Joined: 2010-09-11
Posts: 171
Location: Barcelona, Spain
Status: Offline
|
|
Now another issue has appeared. From two or three days ago, doing d-u I get:
Code:
Reading package lists...
Building dependency tree...
Reading state information...
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
libwine : Breaks: libwine:i386 (!= 1.6.2-20) but 1.6.2-21 is installed
libwine:i386 : Breaks: libwine (!= 1.6.2-21) but 1.6.2-20 is installed
And the process stops. It implies that d-u does not finish its work, making the system almost unusable. apt-get -f install does not solve this.
Regards. |
Last edited by Luis_P on 07.06.2015, 11:17; edited 1 time in total
|
| |
|
|
|
 |
|
slh
|
|
|
Post subject: RE: Problem with libwine
Posted: 25.05.2015, 14:51
|
|
Joined: 2010-08-25
Posts: 962
Status: Offline
|
|
| For multi-arch to work, the package versions need to be (exactly) in sync between all involved architectures. It's pretty normal for them to be temporarily out of sync in Debian/unstable after new versions got uploaded to the archive, it's normal and the only solution is to wait until the lagging arch has caught up. |
|
|
| |
|
|
|
|
|
Luis_P
|
|
|
Post subject:
Posted: 30.05.2015, 10:03
|
|
Joined: 2010-09-11
Posts: 171
Location: Barcelona, Spain
Status: Offline
|
|
| To wait is not the solution, I'm afraid. I've been waiting for eight days and the problem is not solved yet. |
|
|
| |
|
|
|
|
|
Luis_P
|
|
|
Post subject:
Posted: 02.06.2015, 08:37
|
|
Joined: 2010-09-11
Posts: 171
Location: Barcelona, Spain
Status: Offline
|
|
Really, to wait wasn't the solution. The solution was to delete-purge libwine and libwine:i386, wine32:i386 and wine64. After that, I could do d-u smoothly.
Wine and its dependencies were installed again, but now wine does not run. Now I can't run any windows program, some of which I need for my regular work. Worse: if I try to run wincfg, it appears:
Code:
$ winecfg
/usr/bin/winecfg: 32: exec: wine32: not found
apt-get install wine32
Reading package lists... Done
Building dependency tree
Reading state information... Done
wine32:i386 is already the newest version.
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
wine32:i386 : Depends: libwine:i386 but it is not going to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).
root@aptosidbox1:/home/lluis1# apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following extra packages will be installed:
libwine:i386
Suggested packages:
cups-bsd:i386
The following NEW packages will be installed:
libwine:i386
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 0 B/15.2 MB of archives.
After this operation, 116 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
(Reading database ... 204301 files and directories currently installed.)
Preparing to unpack .../libwine_1.6.2-21_i386.deb ...
Unpacking libwine:i386 (1.6.2-21) ...
dpkg: error processing archive /var/cache/apt/archives/libwine_1.6.2-21_i386.deb (--unpack):
trying to overwrite shared '/usr/share/wine/wine/fonts/smae1257.fon', which is different from other instances of package libwine:i386
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/libwine_1.6.2-21_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@aptosidbox1:/home/lluis1#
Any idea?
Thanks for your time.
Luis_P, |
|
|
| |
|
|
|
|
|
slh
|
|
|
Post subject:
Posted: 02.06.2015, 16:13
|
|
Joined: 2010-08-25
Posts: 962
Status: Offline
|
|
| Removing the offending multi-arch packages, thereby effectively disabling multi-arch, is always an alternative - usually just not one the enduser wants. |
|
|
| |
|
|
|
|
|
Luis_P
|
|
|
Post subject:
Posted: 03.06.2015, 08:34
|
|
Joined: 2010-09-11
Posts: 171
Location: Barcelona, Spain
Status: Offline
|
|
|
slh wrote:
Removing the offending multi-arch packages, thereby effectively disabling multi-arch, is always an alternative - usually just not one the enduser wants.
Well, seemingly there is a problem with the package libwine_1.6.2-21_i386.deb. Maybe we (as I do not know how to do) should put a bug warning on Debian. |
|
|
| |
|
|
|
|
|
Luis_P
|
|
|
Post subject:
Posted: 07.06.2015, 11:17
|
|
Joined: 2010-09-11
Posts: 171
Location: Barcelona, Spain
Status: Offline
|
|
| The newest version of libwine (1.6.2-22) has not this issue. Then I think this problem has been solved. |
|
|
| |
|
|
|
|
|
slh
|
|
|
Post subject:
Posted: 07.06.2015, 17:20
|
|
Joined: 2010-08-25
Posts: 962
Status: Offline
|
|
| Keep in mind that version mismatches are a pretty normal issue with multi-arch, which particularly affects wine packages (as those are the most likely ones to be affected on an enduser system). It's likely to happen (temporarily) after each upload of the wine (or its reverse dependencies) packages. |
|
|
| |
|
|
|
|
|
|
