Ubuntu
lapack package

package liblapack3gf 3.2.1-2 failed to install/upgrade: el paquete liblapack3gf ya está instalado y configurado

Bug #793657 reported by Julian Gaitan Arias on 2011-06-06

This bug report is a duplicate of: Bug #541595: [Master] package failed to install/upgrade: package is already installed and configured. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	lapack (Ubuntu)	New	Undecided	Unassigned

Bug Description

Estaba ejecutando el "Encargado de limpieza" y despues salio el error

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: liblapack3gf 3.2.1-2
ProcVersionSignature: Ubuntu 2.6.32-32.62-generic 2.6.32.38+drm33.16
Uname: Linux 2.6.32-32-generic i686
NonfreeKernelModules: fglrx
Architecture: i386
Date: Mon Jun 6 12:07:02 2011
ErrorMessage: el paquete liblapack3gf ya está instalado y configurado
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
SourcePackage: lapack
Title: package liblapack3gf 3.2.1-2 failed to install/upgrade: el paquete liblapack3gf ya está instalado y configurado

Tags:

Revision history for this message

Julian Gaitan Arias (guatajuk) wrote on 2011-06-06:

AptOrdering.txt Edit (162 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (548 bytes, text/plain; charset="utf-8")
Df.txt Edit (596 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (45.0 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.gz Edit (32.5 KiB, application/x-gzip)

Ubuntu Foundations Team Bug Bot (crichton) on 2011-06-06

affects:

ubuntu → lapack (Ubuntu)

Revision history for this message

Brian Murray (brian-murray) wrote on 2011-07-27:

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 541595, 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. Please continue to report any other bugs you may find.