package linphone 3.1.1-2 failed to install/upgrade: trying to overwrite `/usr/share/pixmaps/linphone/linphone2.xpm', which is also in package linphone-common

Bug #375306 reported by Max Bowsher
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linphone (Debian)
Fix Released
Unknown
linphone (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: linphone

Preparing to replace linphone 3.1.1-2 (using .../linphone_3.1.2-1_amd64.deb) ...
Unpacking replacement linphone ...
dpkg: error processing /var/cache/apt/archives/linphone_3.1.2-1_amd64.deb (--unpack):
 trying to overwrite `/usr/share/pixmaps/linphone/linphone2.xpm', which is also in package linphone-common

Looks like the file has been moved between binary packages without the suitable dependency incantations to ensure the packages upgrade without clashing.

ProblemType: Package
Architecture: amd64
Date: Tue May 12 07:56:45 2009
DistroRelease: Ubuntu 9.10
ErrorMessage: trying to overwrite `/usr/share/pixmaps/linphone/linphone2.xpm', which is also in package linphone-common
Package: linphone 3.1.1-2
SourcePackage: linphone
Title: package linphone 3.1.1-2 failed to install/upgrade: trying to overwrite `/usr/share/pixmaps/linphone/linphone2.xpm', which is also in package linphone-common
Uname: Linux 2.6.30-2-generic x86_64

Revision history for this message
Max Bowsher (maxb) wrote :
Revision history for this message
Max Bowsher (maxb) wrote :

Actually, no, the file really is erroneously present in both the linphone and linphone-common binary packages (though appropriate Conflicts+Replaces would still be needed to prevent an error once that more serious bug was fixed)

Changed in linphone (Debian):
status: Unknown → New
Revision history for this message
lunarok (lunarok) wrote :

I get the same with upgrading in Karmic. I am also on AMD64.

Changed in linphone (Debian):
status: New → Fix Released
Revision history for this message
Max Bowsher (maxb) wrote :

Fixed by sync of 3.1.2-2

Changed in linphone (Ubuntu):
status: New → Fix Released
Revision history for this message
lunarok (lunarok) wrote :

Yes I have it fixed, thanks

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.