package gdb-msp430 7.2~mspgcc-7.2-20110612-1ubuntu1 failed to install/upgrade: intentando sobreescribir `/usr/share/gdb/python/gdb/__init__.py', que está también en el paquete gdb 7.4-2012.04-0ubuntu2.1

[Jorge Rodríguez]

Bug report

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: gdb-msp430 7.2~mspgcc-7.2-20110612-1ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-48.74-generic-pae 3.2.46
Uname: Linux 3.2.0-48-generic-pae i686
NonfreeKernelModules: wl
ApportVersion: 2.0.1-0ubuntu17.3
AptOrdering:
 gdb-msp430: Install
 gdb-msp430: Configure
Architecture: i386
Date: Wed Jun 19 22:37:25 2013
DpkgTerminalLog:
 Desempaquetando gdb-msp430 (de .../gdb-msp430_7.2~mspgcc-7.2-20110612-1ubuntu1_i386.deb) ...
 dpkg: error al procesar /var/cache/apt/archives/gdb-msp430_7.2~mspgcc-7.2-20110612-1ubuntu1_i386.deb (--unpack):
  intentando sobreescribir `/usr/share/gdb/python/gdb/__init__.py', que está también en el paquete gdb 7.4-2012.04-0ubuntu2.1
DuplicateSignature: package:gdb-msp430:7.2~mspgcc-7.2-20110612-1ubuntu1:intentando sobreescribir `/usr/share/gdb/python/gdb/__init__.py', que está también en el paquete gdb 7.4-2012.04-0ubuntu2.1
ErrorMessage: intentando sobreescribir `/usr/share/gdb/python/gdb/__init__.py', que está también en el paquete gdb 7.4-2012.04-0ubuntu2.1
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
MarkForUpload: True
SourcePackage: gdb-msp430
Title: package gdb-msp430 7.2~mspgcc-7.2-20110612-1ubuntu1 failed to install/upgrade: intentando sobreescribir `/usr/share/gdb/python/gdb/__init__.py', que está también en el paquete gdb 7.4-2012.04-0ubuntu2.1
UpgradeStatus: No upgrade log present (probably fresh install)

[Hans Joachim Desserud (hjd)]

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.