Ubuntu
gst-plugins-bad0.10 package

package gstreamer0.10-plugins-bad 0.10.21-1ubuntu11 failed to install/upgrade: 正试图覆盖 /usr/share/locale/ja/LC_MESSAGES/.mo，它同时被包含于软件包 gstreamer0.10-plugins-ugly 0.10.17-1ubuntu1

Bug #752140 reported by d0ngd0ng on 2011-04-06

This bug report is a duplicate of: Bug #751334: i was executing sudo apt-get update; sudo apt-get upgrade. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	gst-plugins-bad0.10 (Ubuntu)	New	Undecided	Unassigned

Bug Description

I don't know why.

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: gstreamer0.10-plugins-bad 0.10.21-1ubuntu11
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
NonfreeKernelModules: nvidia
AptOrdering:
gstreamer0.10-plugins-bad: Install
gstreamer0.10-plugins-bad: Configure
Architecture: amd64
Date: Tue Apr 5 23:32:51 2011
ErrorMessage: 正试图覆盖 /usr/share/locale/ja/LC_MESSAGES/.mo，它同时被包含于软件包 gstreamer0.10-plugins-ugly 0.10.17-1ubuntu1
SourcePackage: gst-plugins-bad0.10
Title: package gstreamer0.10-plugins-bad 0.10.21-1ubuntu11 failed to install/upgrade: 正试图覆盖 /usr/share/locale/ja/LC_MESSAGES/.mo，它同时被包含于软件包 gstreamer0.10-plugins-ugly 0.10.17-1ubuntu1
UpgradeStatus: Upgraded to natty on 2011-03-25 (11 days ago)

Tags:

Revision history for this message

d0ngd0ng (agile-java) wrote on 2011-04-06:

Dependencies.txt Edit (3.5 KiB, text/plain; charset="utf-8")
Df.txt Edit (571 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (69.4 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (1.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Robert Roth (evfool) wrote on 2011-05-20:

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 #751405, 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.