Ubuntu
freetds package

TDSODBC Packet bug

Bug #292883 reported by obelisk001 on 2008-11-03

This bug report is a duplicate of: Bug #254953: package update-manager 1:0.93.1 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1). Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	freetds (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Intrepid Upgrade from the Hardy 8.04 found one error that halted the overall installation toward the end of the process. The package uninstalled/that caused the problem was the TDSODBC. I expected the installation to finish the installation process and the clean-up and a restart. Unfortunately that did not happen. I am reluctant to restart my system as it may have an incomplete install and will require hours and hours of debugging via the old kernel.

ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 8.10
ErrorMessage:
ErrorMessage: subprocess post-installation script returned error exit status 1
NonfreeKernelModules: nvidia
Package: tdsodbc 0.82-3
SourcePackage: freetds
Title: package tdsodbc 0.82-3 failed to install/upgrade:
Uname: Linux 2.6.24-21-generic i686

Tags:

Revision history for this message

obelisk001 (eduard-baba) wrote on 2008-11-03:

Dependencies.txt Edit (396 bytes, text/plain; charset="utf-8")
VarLogDistupgradeAptlog.gz Edit (20.5 KiB, application/x-gzip)
VarLogDistupgradeApttermlog.gz Edit (67.7 KiB, application/x-gzip)
VarLogDistupgradeMainlog.gz Edit (13.7 KiB, application/x-gzip)
VarLogDistupgradeTermlog.gz Edit (68.8 KiB, application/x-gzip)

Revision history for this message

Jean-Baptiste Lallement (jibel) wrote on 2008-11-03:

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