[Debian-med-packaging] Bug#584194: tclcl-dev and libctapimkt0-dev: error when trying to install together

[Andreas Tille]

Hi Claudia,

the naming conflicts with ctapimkt become worse as you see.  Both
header files

   /usr/include/config.h in this bug report and
   /usr/include/ctapi.h  in #557495

have naming conflicts.  Putting a header file with such a generic name
like config.h into a default directory is bad and should be changed.  So
my advise to solve both issues by creating a subdirectory

   /usr/include/ctapimkt

and move both files to this location.  This is one suggestion I made
previousely according to #557495 and the reason to follow this
suggestion now, after Simon Richter who tried to provide a general
ctapi.h has resigned from most of his Debian work, becomes much
stronger.  So please fix this in your upstream code.  Otherwise the
library will not make it into the next Debian release and I will ask
ftpmaster for removal of this package because it causes other packages
to fail.

Remark: IMHO also tclcl-dev should not provide a file
         /usr/include/config.h
        and I would consider this also as very bad style.

Kind regards

         Andreas.

On Wed, Jun 02, 2010 at 08:27:32AM +0200, Ralf Treinen wrote:
> Package: libctapimkt0-dev,tclcl-dev
> Version: libctapimkt0-dev/1.0.1-1
> Version: tclcl-dev/1.20~RC2-1
> Severity: serious
> User: treinen at debian.org
> Usertags: edos-file-overwrite
> 
> Date: 2010-06-02
> 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:
> 
> 
> WARNING: The following packages cannot be authenticated!
>   libc-dev-bin linux-libc-dev libc6-dev libctapimkt0 libctapimkt0-dev
>   tclcl-dev
> Authentication warning overridden.
> Can not write log, openpty() failed (/dev/pts not mounted?)
> Selecting previously deselected package libc-dev-bin.
> (Reading database ... 12205 files and directories currently installed.)
> Unpacking libc-dev-bin (from .../libc-dev-bin_2.11.1-2_amd64.deb) ...
> Selecting previously deselected package linux-libc-dev.
> Unpacking linux-libc-dev (from .../linux-libc-dev_2.6.32-15_amd64.deb) ...
> Selecting previously deselected package libc6-dev.
> Unpacking libc6-dev (from .../libc6-dev_2.11.1-2_amd64.deb) ...
> Selecting previously deselected package libctapimkt0.
> Unpacking libctapimkt0 (from .../libctapimkt0_1.0.1-1_amd64.deb) ...
> Selecting previously deselected package libctapimkt0-dev.
> Unpacking libctapimkt0-dev (from .../libctapimkt0-dev_1.0.1-1_amd64.deb) ...
> Selecting previously deselected package tclcl-dev.
> Unpacking tclcl-dev (from .../tclcl-dev_1.20~RC2-1_amd64.deb) ...
> dpkg: error processing /var/cache/apt/archives/tclcl-dev_1.20~RC2-1_amd64.deb (--unpack):
>  trying to overwrite '/usr/include/config.h', which is also in package libctapimkt0-dev 0:1.0.1-1
> dpkg-deb: subprocess paste killed by signal (Broken pipe)
> Processing triggers for man-db ...
> Errors were encountered while processing:
>  /var/cache/apt/archives/tclcl-dev_1.20~RC2-1_amd64.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/include/config.h
> 
> 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.
> 
> -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/mailman/listinfo/debian-med-packaging
> 

-- 
http://fam-tille.de