Bug#916468: dune: /usr/bin/dune is already provided by the whitedune package
Hi whitedune maintainers, On Mon, 7 Jan 2019 14:00:45 +0100 =?UTF-8?Q?St=c3=a9phane_Glondu?= wrote: > reassign 916468 whitedune 0.30.10-2.1 > thanks > > Le 14/12/2018 à 20:24, Andreas Beckmann a écrit : > > 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 unselected package dune. > > Preparing to unpack .../dune_1.6.2-1_amd64.deb ... > > Unpacking dune (1.6.2-1) ... > > dpkg: error processing archive > > /var/cache/apt/archives/dune_1.6.2-1_amd64.deb (--unpack): > >trying to overwrite '/usr/bin/dune', which is also in package whitedune > > 0.30.10-2.1+b2 > > Errors were encountered while processing: > >/var/cache/apt/archives/dune_1.6.2-1_amd64.deb > > > > > > 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/bin/dune > > usr/share/man/man1/dune.1.gz > > As discussed on debian-devel, I propose that the whitedune package drops > /usr/bin/dune, which is a symlink to whitedune. Is anybody against dropping the symlink? If not, I can prepare an upload to fix this RC bug. This bug affecting my package view3dscene, because I use whitedunes files in its tests. I could drop the dependency but I'd rather not. Paul signature.asc Description: OpenPGP digital signature
Bug#916468: dune: /usr/bin/dune is already provided by the whitedune package
reassign 916468 whitedune 0.30.10-2.1 thanks Le 14/12/2018 à 20:24, Andreas Beckmann a écrit : > 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 unselected package dune. > Preparing to unpack .../dune_1.6.2-1_amd64.deb ... > Unpacking dune (1.6.2-1) ... > dpkg: error processing archive > /var/cache/apt/archives/dune_1.6.2-1_amd64.deb (--unpack): >trying to overwrite '/usr/bin/dune', which is also in package whitedune > 0.30.10-2.1+b2 > Errors were encountered while processing: >/var/cache/apt/archives/dune_1.6.2-1_amd64.deb > > > 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/bin/dune > usr/share/man/man1/dune.1.gz As discussed on debian-devel, I propose that the whitedune package drops /usr/bin/dune, which is a symlink to whitedune. Cheers, -- Stéphane
Bug#916468: dune: /usr/bin/dune is already provided by the whitedune package
Package: dune Version: 1.6.2-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite 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 unselected package dune. Preparing to unpack .../dune_1.6.2-1_amd64.deb ... Unpacking dune (1.6.2-1) ... dpkg: error processing archive /var/cache/apt/archives/dune_1.6.2-1_amd64.deb (--unpack): trying to overwrite '/usr/bin/dune', which is also in package whitedune 0.30.10-2.1+b2 Errors were encountered while processing: /var/cache/apt/archives/dune_1.6.2-1_amd64.deb 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/bin/dune usr/share/man/man1/dune.1.gz Cheers, Andreas PS: for more information about the detection of file overwrite errors of this kind see https://qa.debian.org/dose/file-overwrites.html whitedune=0.30.10-2.1+b2_dune=1.6.2-1.log.gz Description: application/gzip