[Debian-med-packaging] Bug#730751: seqan-apps and mason: error when trying to install together

[Holtgrewe, Manuel]

This sounds good, in the next major seqan release, we will have mason version 2 which has binaries called mason_* and no "mason" any more.

Cheers,
Manuel
________________________________________
From: Andreas Tille [andreas at an3as.eu]
Sent: Friday, November 29, 2013 11:13 AM
To: 730751 at bugs.debian.org
Cc: Holtgrewe, Manuel; Filippo Rusconi
Subject: Re: Bug#730751: seqan-apps and mason: error when trying to install together

Hi Manuel,

here we are with another naming conflict (thanks to Ralf for your
checking bot which only needed 12h to detect a problem ;-)).

Manuel, if I understood you correctly it is OK to rename the symlink
from

   /usr/bin/mason     to     /usr/bin/seqan-mason  .

Is this correct?  I think we could leave the original name in
/usr/lib/seqan/bin/mason ?

Please confirm this or make better suggestions.

Kind regards

        Andreas.

PS: To the mason maintainer: I think we can deal with the problem
    in the seqan package - no action from your side is required.

On Fri, Nov 29, 2013 at 07:48:59AM +0100, Ralf Treinen wrote:
> Package: mason,seqan-apps
> Version: mason/1.0.0-12.3
> Version: seqan-apps/1.4.01-1
> Severity: serious
> User: treinen at debian.org
> Usertags: edos-file-overwrite
>
> Date: 2013-11-29
> 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:
>
>
> Preconfiguring packages ...
> Selecting previously unselected package libgomp1:amd64.
> (Reading database ... 10882 files and directories currently installed.)
> Unpacking libgomp1:amd64 (from .../libgomp1_4.8.2-6_amd64.deb) ...
> Selecting previously unselected package seqan-apps.
> Unpacking seqan-apps (from .../seqan-apps_1.4.1-1_amd64.deb) ...
> Selecting previously unselected package mason.
> Unpacking mason (from .../mason_1.0.0-12.3_all.deb) ...
> dpkg: error processing /var/cache/apt/archives/mason_1.0.0-12.3_all.deb (--unpack):
>  trying to overwrite '/usr/share/man/man1/mason.1.gz', which is also in package seqan-apps 1.4.1-1
> dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
> Processing triggers for man-db ...
> Errors were encountered while processing:
>  /var/cache/apt/archives/mason_1.0.0-12.3_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/bin/mason
>   /usr/share/man/man1/mason.1.gz
>
> This bug has been filed against 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 then
> also register in the BTS that the other package is affected by the bug.
>
> -Ralf.
>
> PS: for more information about the detection of file overwrite errors
> of this kind see http://edos.debian.net/file-overwrites/.
>
> _______________________________________________
> Debian-med-packaging mailing list
> Debian-med-packaging at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
>

--
http://fam-tille.de