Package: libmeep-mpich-dev Version: libmeep-mpich-dev/1.1.1-4 Severity: serious User: [email protected] Usertags: edos-file-overwrite
Date: 2010-01-18 Architecture: amd64 Distribution: sid 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: WARNING: The following packages cannot be authenticated! libgfortran3 libatlas3gf-base libfftw3-3 libgsl0ldbl libharminv2 libhdf5-mpich-1.8.3 libmeep6 libmeep-dev libmeep-mpich6 libmeep-mpich-dev W: cowdancer: unsupported operation flock, read-only open and fchown/fchmod/flock are not supported: tried openning dev:inode of 2055:5407970 W: cowdancer: unsupported operation flock, read-only open and fchown/fchmod/flock are not supported: tried openning dev:inode of 2055:5407760 W: cowdancer: unsupported operation flock, read-only open and fchown/fchmod/flock are not supported: tried openning dev:inode of 2055:5407950 Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously deselected package libgfortran3. (Reading database ... 10452 files and directories currently installed.) Unpacking libgfortran3 (from .../libgfortran3_4.4.2-9_amd64.deb) ... Selecting previously deselected package libatlas3gf-base. Unpacking libatlas3gf-base (from .../libatlas3gf-base_3.6.0-24_amd64.deb) ... Selecting previously deselected package libfftw3-3. Unpacking libfftw3-3 (from .../libfftw3-3_3.2.2-1_amd64.deb) ... Selecting previously deselected package libgsl0ldbl. Unpacking libgsl0ldbl (from .../libgsl0ldbl_1.13+dfsg-1_amd64.deb) ... Selecting previously deselected package libharminv2. Unpacking libharminv2 (from .../libharminv2_1.3.1-3_amd64.deb) ... Selecting previously deselected package libhdf5-mpich-1.8.3. Unpacking libhdf5-mpich-1.8.3 (from .../libhdf5-mpich-1.8.3_1.8.3-2.1_amd64.deb) ... Selecting previously deselected package libmeep6. Unpacking libmeep6 (from .../libmeep6_1.1.1-3_amd64.deb) ... Selecting previously deselected package libmeep-dev. Unpacking libmeep-dev (from .../libmeep-dev_1.1.1-3_amd64.deb) ... Selecting previously deselected package libmeep-mpich6. Unpacking libmeep-mpich6 (from .../libmeep-mpich6_1.1.1-4_amd64.deb) ... Selecting previously deselected package libmeep-mpich-dev. Unpacking libmeep-mpich-dev (from .../libmeep-mpich-dev_1.1.1-4_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/libmeep-mpich-dev_1.1.1-4_amd64.deb (--unpack): trying to overwrite '/usr/include/meep.hpp', which is also in package libmeep-dev 0:1.1.1-3 dpkg-deb: subprocess paste killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libmeep-mpich-dev_1.1.1-4_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/include/meep.hpp Exactly the same problem occurs for the conjunction of the packages libmeep-mpi-dev and libmeep-mpich-dev. Since, at least according to my script, it does not occur between libmeep-dev and libmeep-mpi-dev I assume that libmeep-mpich-dev is at fault here. If this is not the case then please reassign the bug report. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
