package libmono-webbrowser4.0-cil (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/mono/4.0/Mono.WebBrowser.dll', which is also in package libmono-webbrowser0.5-cil 2.10.1-4ubuntu1

Bug #824858 reported by userdce
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
mono (Ubuntu)
Confirmed
Wishlist
Unassigned

Bug Description

package libmono-webbrowser4.0-cil (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/mono/4.0/Mono.WebBrowser.dll', which is also in package libmono-webbrowser0.5-cil 2.10.1-4ubuntu1

ProblemType: Package
DistroRelease: Ubuntu 11.10
Package: libmono-webbrowser4.0-cil (not installed)
ProcVersionSignature: Ubuntu 3.0.0-8.10-generic 3.0.1
Uname: Linux 3.0.0-8-generic x86_64
NonfreeKernelModules: wl fglrx
Architecture: amd64
Date: Thu Aug 11 19:02:03 2011
ErrorMessage: trying to overwrite '/usr/lib/mono/4.0/Mono.WebBrowser.dll', which is also in package libmono-webbrowser0.5-cil 2.10.1-4ubuntu1
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110716)
SourcePackage: mono
Title: package libmono-webbrowser4.0-cil (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/mono/4.0/Mono.WebBrowser.dll', which is also in package libmono-webbrowser0.5-cil 2.10.1-4ubuntu1
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
userdce (userdce) wrote :
tags: added: package-conflict
Changed in mono (Ubuntu):
status: New → Confirmed
Revision history for this message
Micah Gersten (micahg) wrote :

This just needs a Breaks/Replaces, will attach a patch shortly.

Changed in mono (Ubuntu):
assignee: nobody → Micah Gersten (micahg)
importance: Undecided → Wishlist
status: Confirmed → In Progress
Revision history for this message
Micah Gersten (micahg) wrote :

This patch adds the appropriate breaks/replaces

Changed in mono (Ubuntu):
assignee: Micah Gersten (micahg) → nobody
status: In Progress → Confirmed
Revision history for this message
Iain Lane (laney) wrote :

Thanks for the patch, but this will be fixed by syncing the new version from exp: marking the bug as a dupe of that one.

Revision history for this message
userdce (userdce) wrote :

So what to do with this bug now?

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.