package gdb-msp430 (not installed) failed to install/upgrade: trying to overwrite '/usr/share/gdb/python/gdb/__init__.py', which is also in package gdb 7.4-2012.04-0ubuntu2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gdb-msp430 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
apt-get install binutils-msp430 gcc-msp430 gdb-msp430 msp430-libc msp430mcu mspdebug
Failed with an error. Looked like this:
Selecting previously unselected package gdb-msp430.
Unpacking gdb-msp430 (from .../gdb-
dpkg: error processing /var/cache/
trying to overwrite '/usr/share/
Selecting previously unselected package msp430-libc.
Unpacking msp430-libc (from .../msp430-
Selecting previously unselected package mspdebug.
Unpacking mspdebug (from .../mspdebug_
Processing triggers for man-db ...
Errors were encountered while processing:
/var/cache/
E: Sub-process /usr/bin/dpkg returned an error code (1)
$ lsb_release -rd
Description: Ubuntu 12.04.1 LTS
Release: 12.04
$ apt-cache policy gdb-msp430
gdb-msp430:
Installed: (none)
Candidate: 7.2~mspgcc-
Version table:
7.
500 http://
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: gdb-msp430 (not installed)
ProcVersionSign
Uname: Linux 3.2.0-31-generic x86_64
ApportVersion: 2.0.1-0ubuntu13
Architecture: amd64
Date: Fri Sep 28 11:19:39 2012
DuplicateSignature:
Unpacking gdb-msp430 (from .../gdb-
dpkg: error processing /var/cache/
trying to overwrite '/usr/share/
ErrorMessage: trying to overwrite '/usr/share/
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
SourcePackage: gdb-msp430
Title: package gdb-msp430 (not installed) failed to install/upgrade: trying to overwrite '/usr/share/
UpgradeStatus: Upgraded to precise on 2012-04-28 (152 days ago)
tags: | removed: need-duplicate-check |
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 860045, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.