Package: libconcord-dev Version: 0.23-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite
Architecture: amd64
Distribution: squeeze->wheezy (partial) upgrade
Hi,
automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:
Selecting previously deselected package libconcord1.
(Reading database ... 6286 files and directories currently installed.)
Unpacking libconcord1 (from .../libconcord1_0.22-3_amd64.deb) ...
Selecting previously deselected package libconcord1-dev.
Unpacking libconcord1-dev (from .../libconcord1-dev_0.22-3_amd64.deb) ...
Setting up libconcord1 (0.22-3) ...
Setting up libconcord1-dev (0.22-3) ...
Selecting previously deselected package libconcord2.
(Reading database ... 6372 files and directories currently installed.)
Unpacking libconcord2 (from .../libconcord2_0.24-1_amd64.deb) ...
Selecting previously deselected package libconcord-dev.
Unpacking libconcord-dev (from .../libconcord-dev_0.24-1_amd64.deb) ...
dpkg: error processing
/var/cache/apt/archives/libconcord-dev_0.24-1_amd64.deb (--unpack):
trying to overwrite '/usr/include/libconcord.h', which is also in package
libconcord1-dev 0.22-3
This is a serious bug as it makes installation/upgrade fail, and
violates sections 7.6.1 and 10.1 of the policy.
As this problem can be demonstrated during partial upgrades from squeeze
to wheezy (but not within squeeze or wheezy itself), this indicates a
missing or insufficiently versioned Replaces+Breaks relationship.
But since this particular upgrade ordering is not forbidden by any
dependency relationship, it is possible that apt (or $PACKAGE_MANAGER)
will use this erroneus path on squeeze->wheezy upgrades.
Here is a list of files that are known to be shared by both packages
(according to the Contents files for squeeze and wheezy on amd64, which
may be slightly out of sync):
usr/include/libconcord.h
usr/lib/libconcord.a
usr/lib/libconcord.so
The -dev package was renamed recently:
concordance (0.23-1) unstable; urgency=low
* debian/control: bump soname version in package name for libs, also
drop the soname version number in the development package name.
* debian/libconcord1-dev.install: renamed to libconcord-dev.install.
The following relationships are currently defined:
Package: libconcord-dev
Conflicts: n/a
Breaks: n/a
Replaces: n/a
The following relationships should be added for a clean takeover of
these files
(http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces):
Package: libconcord-dev
Breaks: libconcord1-dev
Replaces: libconcord1-dev
(unversioned, since libconcord1-dev no longer exists)
Cheers,
Andreas
PS: for more information about the detection of file overwrite errors
of this kind see http://edos.debian.net/file-overwrites/.
libconcord1-dev=0.22-3_libconcord-dev=0.24-1.log.gz
Description: GNU Zip compressed data
