Ubuntu
wvstreams package

unable to install libuniconf4.6

Bug #442537 reported by stefano.fraccaro on 2009-10-04

This bug report is a duplicate of: Bug #441846: package libuniconf4.6 (not installed) failed to install/upgrade: trying to overwrite '/etc/uniconf.conf', which is also in package libuniconf4.4 0:4.4.1-1.1. Edit Remove

This bug affects 1 person

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

Bug Description

Binary package hint: libuniconf4.6

The package try to replace "/etc/uniconf.conf" but this action throw an exception because the same file is present in libuniconf4.4.

(Lettura del database... 282716 file e directory attualmente installati.)
Estrazione di libuniconf4.6 (da .../libuniconf4.6_4.6-1_i386.deb)...
dpkg: errore nell'elaborare /var/cache/apt/archives/libuniconf4.6_4.6-1_i386.deb (--unpack):
tentata sovrascrittura di "/etc/uniconf.conf" presente anche nel pacchetto libuniconf4.4 0:4.4.1-1.1
Si sono verificati degli errori nell'elaborazione:
/var/cache/apt/archives/libuniconf4.6_4.6-1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Bug
Architecture: i386
Date: Sun Oct 4 22:11:02 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/yelp
Package: yelp 2.28.0-0ubuntu1
ProcEnviron:
LANGUAGE=it_IT.UTF-8
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SourcePackage: yelp
Uname: Linux 2.6.31-11-generic i686

Tags:

Revision history for this message

stefano.fraccaro (sf-1) wrote on 2009-10-04:

Dependencies.txt Edit (4.2 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (38.7 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (752 bytes, text/plain; charset="utf-8")
XsessionErrors.txt Edit (43.1 KiB, text/plain; charset="utf-8")

Revision history for this message

Lars Ljung (larslj) wrote on 2009-10-04:

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