Package: linux-patch-tomoyo,linux-patch-tomoyo1.7 Version: linux-patch-tomoyo/1.6.8-20100120-1 Version: linux-patch-tomoyo1.7/1.7.1-20100214-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite
Date: 2010-02-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! patch dctrl-tools tomoyo-ccstools linux-patch-tomoyo linux-patch-tomoyo1.7 W: cowdancer: unsupported operation flock, read-only open and fchown/fchmod/flock are not supported: tried openning dev:inode of 2055:5406874 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:5406878 Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Setting up libpam0g (1.1.1-2) ... W: cowdancer: unsupported operation flock, read-only open and fchown/fchmod/flock are not supported: tried openning dev:inode of 2055:5406874 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:5406878 Checking for services that may need to be restarted...Checking init scripts... Restarting services possibly affected by the upgrade: cron: stopping...starting...done. Services restarted successfully. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously deselected package patch. (Reading database ... 12304 files and directories currently installed.) Unpacking patch (from .../archives/patch_2.6-2_amd64.deb) ... Selecting previously deselected package dctrl-tools. Unpacking dctrl-tools (from .../dctrl-tools_2.14_amd64.deb) ... Selecting previously deselected package tomoyo-ccstools. Unpacking tomoyo-ccstools (from .../tomoyo-ccstools_1.6.8-20100115-2_amd64.deb) ... Selecting previously deselected package linux-patch-tomoyo. Unpacking linux-patch-tomoyo (from .../linux-patch-tomoyo_1.6.8-20100120-1_all.deb) ... Selecting previously deselected package linux-patch-tomoyo1.7. Unpacking linux-patch-tomoyo1.7 (from .../linux-patch-tomoyo1.7_1.7.1-20100214-1_all.deb) ... dpkg: error processing /var/cache/apt/archives/linux-patch-tomoyo1.7_1.7.1-20100214-1_all.deb (--unpack): trying to overwrite '/usr/src/kernel-patches/all/unpatch/tomoyo', which is also in package linux-patch-tomoyo 0:1.6.8-20100120-1 dpkg-deb: subprocess paste killed by signal (Broken pipe) Processing triggers for man-db ... W: cowdancer: unsupported operation flock, read-only open and fchown/fchmod/flock are not supported: tried openning dev:inode of 2055:5407760 Errors were encountered while processing: /var/cache/apt/archives/linux-patch-tomoyo1.7_1.7.1-20100214-1_all.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/src/kernel-patches/all/apply/tomoyo /usr/src/kernel-patches/all/unpatch/tomoyo /usr/src/kernel-patches/diffs/tomoyo/ccs-patch-2.4.34.diff.gz /usr/src/kernel-patches/diffs/tomoyo/ccs-patch-2.4.35.diff.gz /usr/src/kernel-patches/diffs/tomoyo/ccs-patch-2.6.18.diff.gz /usr/src/kernel-patches/diffs/tomoyo/ccs-patch-2.6.22.diff.gz /usr/src/kernel-patches/diffs/tomoyo/ccs-patch-2.6.23.diff.gz /usr/src/kernel-patches/diffs/tomoyo/ccs-patch-2.6.24.diff.gz /usr/src/kernel-patches/diffs/tomoyo/ccs-patch-2.6.25.diff.gz /usr/src/kernel-patches/diffs/tomoyo/ccs-patch-2.6.26.diff.gz /usr/src/kernel-patches/diffs/tomoyo/ccs-patch-2.6.27.diff.gz /usr/src/kernel-patches/diffs/tomoyo/ccs-patch-2.6.28.diff.gz /usr/src/kernel-patches/diffs/tomoyo/ccs-patch-2.6.29.diff.gz /usr/src/kernel-patches/diffs/tomoyo/ccs-patch-2.6.30.diff.gz /usr/src/kernel-patches/diffs/tomoyo/ccs-patch-2.6.31.diff.gz This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. -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 debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
