Ubuntu
texlive-base package

package texlive-base 2009-7 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

Bug #622637 reported by tiphergane on 2010-08-23

This bug report is a duplicate of: Bug #618229: package texlive-base 2009-7 failed to install/upgrade: problemas de dependência - deixando desconfigurado. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	texlive-base (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: texlive-base

don't know what to wrote

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: texlive-base 2009-7
ProcVersionSignature: Ubuntu 2.6.32-24.41-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Mon Aug 23 12:06:37 2010
ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
PackageArchitecture: all
SourcePackage: texlive-base
Title: package texlive-base 2009-7 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

Tags:

Revision history for this message

tiphergane (tiphergane) wrote on 2010-08-23:

AptOrdering.txt Edit (2.0 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.5 KiB, text/plain; charset="utf-8")
Df.txt Edit (619 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (63.0 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.gz Edit (14.9 KiB, application/x-gzip)

Revision history for this message

Hsn (alshawaf) wrote on 2010-08-31:

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 618229, 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.