[Debian-astro-maintainers] Bug#756469: libfuntools-dev and libbsd-dev: error when trying to install together

[Guillem Jover]

Hi!

On Wed, 2014-07-30 at 08:57:06 +0200, Ralf Treinen wrote:
> Package: libbsd-dev,libfuntools-dev
> Version: libbsd-dev/0.7.0-1
> Version: libfuntools-dev/1.4.4+dfsg-1
> Severity: serious
> User: treinen at debian.org
> Usertags: edos-file-overwrite

> Date: 2014-07-30
> Architecture: amd64
> Distribution: sid

> 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:

[file conflict log…]

> 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/share/man/man3/funopen.3.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.

Thanks! I fixed this locally, just need to upload the packages. I
think it also should be fixed in funtools (upstream), because it will
collide with system man pages on BSD systems, even if this was caused
by introducing this in libbsd.

BTW Ralf, it seems due to the bug being assigned to two packages,
britney didn't notice which versions this was affecting, and let it
migrate to testing. I don't think tools in general handle very well
bugs assigned to multiple packages, so maybe you might need to
reconsider that practice? Either that or talk with relevant teams to
see what can be done (debbugs perhaps, and release-team at least).

Thanks,
Guillem