Ubuntu
resolvconf package

package resolvconf 1.63ubuntu14 failed to install/upgrade: error writing to '<standard output>': Success

Bug #1006939 reported by Chandan Thakur on 2012-05-31

This bug report is a duplicate of: Bug #545790: package PACKAGE failed to install/upgrade: error writing to '<standard output>': Success. Edit Remove

This bug affects 1 person

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

Bug Description

I am getting error during updating the system.

please fix this issue ASAP.

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: resolvconf 1.63ubuntu14
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
Uname: Linux 3.2.0-24-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
Date: Thu May 31 19:40:38 2012
ErrorMessage: error writing to '<standard output>': Success
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
PackageArchitecture: all
SourcePackage: resolvconf
Title: package resolvconf 1.63ubuntu14 failed to install/upgrade: error writing to '<standard output>': Success
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Chandan Thakur (er-chandanthakur) wrote on 2012-05-31:

AptOrdering.txt Edit (9.3 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.8 KiB, text/plain; charset="utf-8")
Df.txt Edit (454 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (49.9 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt Edit (117.8 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.gz Edit (39.1 KiB, application/x-gzip)

Revision history for this message

Brian Murray (brian-murray) wrote on 2012-05-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 545790, 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.