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

Reply via email to