[Pkg-swan-devel] Bug#767561: [Pkg-freeipa-devel] Bug#767561: pki-tools, strongswan-starter: error when trying to install together

[Timo Aaltonen]

On 01.11.2014 05:44, Andreas Beckmann wrote:
> Package: pki-tools,strongswan-starter
> Version: 10.2.0-2
> Severity: serious
> User: treinen at debian.org
> Usertags: edos-file-overwrite
> Control: found -1 5.2.1-4
> 
> 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:
> 
>   Selecting previously unselected package strongswan-starter.
>   Preparing to unpack .../strongswan-starter_5.2.1-4_amd64.deb ...
>   Unpacking strongswan-starter (5.2.1-4) ...
>   dpkg: error processing archive /var/cache/apt/archives/strongswan-starter_5.2.1-4_amd64.deb (--unpack):
>    trying to overwrite '/usr/bin/pki', which is also in package pki-tools 10.2.0-2
>   dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
>   Errors were encountered while processing:
>    /var/cache/apt/archives/strongswan-starter_5.2.1-4_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/pki
>   usr/share/man/man1/pki.1.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. You may
> also register in the BTS that the other package is affected by the bug.

I don't mind adding a Conflicts. On Fedora though strongswan changed the
binary/manpage name to strongswan-pki:

http://pkgs.fedoraproject.org/cgit/strongswan.git/commit/strongswan.spec?id=710e5ac47162230da3e715a5117a8bb269e4af6d




-- 
t