package libbluetooth-dev 4.60-0ubuntu8 failed to install/upgrade: unable to install new version of `/usr/share/doc/libbluetooth-dev/copyright': No such file or directory

[François Bertel]

Binary package hint: libbluetooth-dev

There is nothing much to say than the summary. libbluetooth-dev fails to install, apparently because it was unable to install a new version of `/usr/share/doc/libbluetooth-dev/copyright': No such file or directory

I never installed this package before. It was not an update.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: libbluetooth-dev 4.60-0ubuntu8
ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic x86_64
NonfreeKernelModules: nvidia
AptOrdering:
 libbluetooth-dev: Install
 libbluetooth-dev: Configure
Architecture: amd64
Date: Thu Aug 12 07:02:29 2010
ErrorMessage: unable to install new version of `/usr/share/doc/libbluetooth-dev/copyright': No such file or directory
InterestingModules: rfcomm sco bnep l2cap btusb bluetooth
MachineType: Dell Inc. Precision M6300
ProcCmdLine: root=UUID=06167a7c-9d08-491e-af8b-144a2d683c22 ro quiet splash
SourcePackage: bluez
Title: package libbluetooth-dev 4.60-0ubuntu8 failed to install/upgrade: unable to install new version of `/usr/share/doc/libbluetooth-dev/copyright': No such file or directory
dmi.bios.date: 11/24/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA12:bd11/24/2008:svnDellInc.:pnPrecisionM6300:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Precision M6300
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0: Type: USB
  BD Address: 00:1E:37:EC:3C:07 ACL MTU: 310:10 SCO MTU: 64:8
  UP RUNNING PSCAN
  RX bytes:969 acl:0 sco:0 events:27 errors:0
  TX bytes:361 acl:0 sco:0 commands:27 errors:0

[Konrad Zapałowicz (kzapalowicz)]

This is reported against an old version of Ubuntu and many things has changed since then. Because of that we won't fix this issue however if this behavior repeats on a modern version please fill a bug report against it and we will take it from there.