package sun-javadb-client (not installed) failed to install/upgrade: trying to overwrite '/usr/share/java/derbyclient.jar', which is also in package libderbyclient-java 10.10.1.1-1

Bug #1276353 reported by Chris West
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
derby (Ubuntu)
Fix Released
Undecided
Unassigned
Trusty
Won't Fix
Undecided
Unassigned
Xenial
Incomplete
Undecided
Unassigned
Yakkety
Won't Fix
Undecided
Unassigned
sun-javadb (Ubuntu)
Fix Released
Undecided
Unassigned
Trusty
Won't Fix
Undecided
Unassigned
Xenial
Incomplete
Undecided
Unassigned
Yakkety
Won't Fix
Undecided
Unassigned

Bug Description

Pretty clean system, fresh install then just dist-upgraded a couple of times.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: sun-javadb-client (not installed)
ProcVersionSignature: Ubuntu 3.13.0-1.16-generic 3.13.0-rc7
Uname: Linux 3.13.0-1-generic x86_64
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
Date: Tue Feb 4 22:07:19 2014
DuplicateSignature: package:sun-javadb-client:(not installed):trying to overwrite '/usr/share/java/derbyclient.jar', which is also in package libderbyclient-java 10.10.1.1-1
ErrorMessage: trying to overwrite '/usr/share/java/derbyclient.jar', which is also in package libderbyclient-java 10.10.1.1-1
InstallationDate: Installed on 2014-01-10 (25 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140110)
SourcePackage: sun-javadb
Title: package sun-javadb-client (not installed) failed to install/upgrade: trying to overwrite '/usr/share/java/derbyclient.jar', which is also in package libderbyclient-java 10.10.1.1-1
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Chris West (faux) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in sun-javadb (Ubuntu):
status: New → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package derby - 10.13.1.1-2ubuntu1

---------------
derby (10.13.1.1-2ubuntu1) zesty; urgency=medium

  * Add transitional packages to take over unmaintained sun-javadb
  * Add Breaks/Replaces against sun-javadb packages that shipped
    the same filenames (LP: #1276353)

 -- Jeremy Bicha <email address hidden> Tue, 20 Dec 2016 12:22:52 -0500

Changed in derby (Ubuntu):
status: New → Fix Released
Jeremy Bícha (jbicha)
Changed in sun-javadb (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Adam Bell (arbell) wrote :

This appears to still be an issue with the Xenial package, though it also appears to have been corrected by the Bionic package. Please update this bug report if there are any plans to backport the corrected package to Xenial.

Changed in derby (Ubuntu Yakkety):
status: New → Won't Fix
Changed in sun-javadb (Ubuntu Yakkety):
status: New → Won't Fix
Changed in sun-javadb (Ubuntu Trusty):
status: New → Won't Fix
Changed in derby (Ubuntu Trusty):
status: New → Won't Fix
Changed in derby (Ubuntu Xenial):
status: New → Incomplete
Changed in sun-javadb (Ubuntu Xenial):
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.