Your message dated Sun, 28 Nov 2010 14:48:13 +0000
with message-id <[email protected]>
and subject line Bug#604626: fixed in med-fichier 2.3.6-5
has caused the Debian Bug report #604626,
regarding libmedc-dev and libmed-dev: error when trying to install together
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
604626: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604626
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libmed-dev,libmedc-dev
Version: libmed-dev/2.3.6-4
Version: libmedc-dev/2.3.6-4
Severity: serious
User: [email protected]
Usertags: edos-file-overwrite

Date: 2010-11-23
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!
  libgfortran3 libibverbs1 libnuma1 libtorque2 libopenmpi1.3
  libhdf5-openmpi-1.8.4 libmed1 libmed-dev libmedc1 libmedc-dev
Authentication warning overridden.
Can not write log, openpty() failed (/dev/pts not mounted?)
Selecting previously deselected package libgfortran3.
(Reading database ... 12297 files and directories currently installed.)
Unpacking libgfortran3 (from .../libgfortran3_4.4.5-8_amd64.deb) ...
Selecting previously deselected package libibverbs1.
Unpacking libibverbs1 (from .../libibverbs1_1.1.3-2_amd64.deb) ...
Selecting previously deselected package libnuma1.
Unpacking libnuma1 (from .../libnuma1_2.0.5-1_amd64.deb) ...
Selecting previously deselected package libtorque2.
Unpacking libtorque2 (from .../libtorque2_2.4.8+dfsg-9_amd64.deb) ...
Selecting previously deselected package libopenmpi1.3.
Unpacking libopenmpi1.3 (from .../libopenmpi1.3_1.4.2-4_amd64.deb) ...
Selecting previously deselected package libhdf5-openmpi-1.8.4.
Unpacking libhdf5-openmpi-1.8.4 (from 
.../libhdf5-openmpi-1.8.4_1.8.4-patch1-2_amd64.deb) ...
Selecting previously deselected package libmed1.
Unpacking libmed1 (from .../libmed1_2.3.6-4_amd64.deb) ...
Selecting previously deselected package libmed-dev.
Unpacking libmed-dev (from .../libmed-dev_2.3.6-4_amd64.deb) ...
Selecting previously deselected package libmedc1.
Unpacking libmedc1 (from .../libmedc1_2.3.6-4_amd64.deb) ...
Selecting previously deselected package libmedc-dev.
Unpacking libmedc-dev (from .../libmedc-dev_2.3.6-4_amd64.deb) ...
dpkg: error processing /var/cache/apt/archives/libmedc-dev_2.3.6-4_amd64.deb 
(--unpack):
 trying to overwrite '/usr/include/med_utils.h', which is also in package 
libmed-dev 0:2.3.6-4
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/libmedc-dev_2.3.6-4_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/MEDerreur.hxx
  /usr/include/med.h
  /usr/include/medC_win_dll.h
  /usr/include/med_proto.h
  /usr/include/med_utils.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. You may
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/.



--- End Message ---
--- Begin Message ---
Source: med-fichier
Source-Version: 2.3.6-5

We believe that the bug you reported is fixed in the latest version of
med-fichier, which is due to be installed in the Debian FTP archive:

libmed-dev_2.3.6-5_amd64.deb
  to main/m/med-fichier/libmed-dev_2.3.6-5_amd64.deb
libmed-doc_2.3.6-5_all.deb
  to main/m/med-fichier/libmed-doc_2.3.6-5_all.deb
libmed-tools_2.3.6-5_amd64.deb
  to main/m/med-fichier/libmed-tools_2.3.6-5_amd64.deb
libmed1_2.3.6-5_amd64.deb
  to main/m/med-fichier/libmed1_2.3.6-5_amd64.deb
libmedc-dev_2.3.6-5_amd64.deb
  to main/m/med-fichier/libmedc-dev_2.3.6-5_amd64.deb
libmedc1_2.3.6-5_amd64.deb
  to main/m/med-fichier/libmedc1_2.3.6-5_amd64.deb
libmedimport-dev_2.3.6-5_amd64.deb
  to main/m/med-fichier/libmedimport-dev_2.3.6-5_amd64.deb
libmedimport0_2.3.6-5_amd64.deb
  to main/m/med-fichier/libmedimport0_2.3.6-5_amd64.deb
libmedimportcxx-dev_2.3.6-5_amd64.deb
  to main/m/med-fichier/libmedimportcxx-dev_2.3.6-5_amd64.deb
libmedimportcxx0_2.3.6-5_amd64.deb
  to main/m/med-fichier/libmedimportcxx0_2.3.6-5_amd64.deb
med-fichier_2.3.6-5.debian.tar.gz
  to main/m/med-fichier/med-fichier_2.3.6-5.debian.tar.gz
med-fichier_2.3.6-5.dsc
  to main/m/med-fichier/med-fichier_2.3.6-5.dsc



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
"Adam C. Powell, IV" <[email protected]> (supplier of updated med-fichier 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Sun, 28 Nov 2010 08:52:54 -0500
Source: med-fichier
Binary: libmed1 libmed-dev libmedc1 libmedc-dev libmedimport0 libmedimport-dev 
libmedimportcxx0 libmedimportcxx-dev libmed-tools libmed-doc
Architecture: source all amd64
Version: 2.3.6-5
Distribution: unstable
Urgency: low
Maintainer: Debian Science Maintainers 
<[email protected]>
Changed-By: "Adam C. Powell, IV" <[email protected]>
Description: 
 libmed-dev - Development files for libmed
 libmed-doc - Documentation for the MED-fichier library
 libmed-tools - Runtime tools to handle MED files
 libmed1    - Library to exchange meshed data (Fortran version)
 libmedc-dev - Development files for libmedc
 libmedc1   - Library to exchange meshed data (C version)
 libmedimport-dev - Development files for libmedimport0
 libmedimport0 - Library to import old version files
 libmedimportcxx-dev - Development files for libmedimportcxx0 (C++ support)
 libmedimportcxx0 - Library to import old version files (C++ support)
Closes: 599052 604626
Changes: 
 med-fichier (2.3.6-5) unstable; urgency=low
 .
   * Reverted last change, added med_exit_if.h to libmedc-dev (closes: #599052).
   * Added conflict with problematic libmed-dev 2.3.6-4 (closes: #604626).
Checksums-Sha1: 
 12501d5101b9c54eef7d8dc4adee96582376c3e3 1560 med-fichier_2.3.6-5.dsc
 ac3459946fa6d3fd88e9adc0bed9722cafe69654 302560 
med-fichier_2.3.6-5.debian.tar.gz
 7c5cc795e57ec3a9f08093875657e2c567b5cf50 1361868 libmed-doc_2.3.6-5_all.deb
 d73ed45366c4ede617692a5ad340eb5dc43fc1cb 141956 libmed1_2.3.6-5_amd64.deb
 ec6a314109505d26f6897cdd5d3062387c038b30 246726 libmed-dev_2.3.6-5_amd64.deb
 590f766cbb91a41077c0afb99417099552e7d742 116084 libmedc1_2.3.6-5_amd64.deb
 8ccce5e2b9b4d63150c7521a1945de9c4ad41af1 203726 libmedc-dev_2.3.6-5_amd64.deb
 87c352d00a6d0e4b74076cdaab11ed83a300ddb6 29752 libmedimport0_2.3.6-5_amd64.deb
 a89950282ca6cd9d974f6c83ececa5ba01d2f400 37068 
libmedimport-dev_2.3.6-5_amd64.deb
 1825889700b08d1ffbf15cacca4a70bc93fb06e5 53930 
libmedimportcxx0_2.3.6-5_amd64.deb
 534b2e42660680e21196b054a0ec3b0aa3611ef5 498214 
libmedimportcxx-dev_2.3.6-5_amd64.deb
 f54195b18ee51a7dce606b4db1665295784cee11 35346 libmed-tools_2.3.6-5_amd64.deb
Checksums-Sha256: 
 3155a1bc54503fdd5264ca04ed65678f167ad4d2bffdc0145ad50311a78ed903 1560 
med-fichier_2.3.6-5.dsc
 5269792af7783708612a709f9cdb38b771c6e6f5680f89d2e1a183c4eb664db6 302560 
med-fichier_2.3.6-5.debian.tar.gz
 5148174ebacf96165457a31cc015ac4df9fc3c1d1d2b8c9387f8fa03cc5140cb 1361868 
libmed-doc_2.3.6-5_all.deb
 2617284cc5a466e36675fcf18a70135c794b4037212fa662b46f0173b38dcae5 141956 
libmed1_2.3.6-5_amd64.deb
 0a3f8ba0632dc7498909f3cce80f508419bd8ecae718920582b1f49c2b625916 246726 
libmed-dev_2.3.6-5_amd64.deb
 22c3a3ea83eca6142144d58935d6f5bac2417db2e6eae44062f03b2b4f387962 116084 
libmedc1_2.3.6-5_amd64.deb
 9ca9ff1ce1d3a3bbea2393d4a6b59ecb58d2e5267634294d5b5b396860a02fd0 203726 
libmedc-dev_2.3.6-5_amd64.deb
 f4213d8715c0fb16b63615a6033fa3f55d370ef4d77ef48fa516d7b525b41e05 29752 
libmedimport0_2.3.6-5_amd64.deb
 80200fec3a31413e2244a8b3a9bfca82df00b5ae808aca3e420f4582088d377a 37068 
libmedimport-dev_2.3.6-5_amd64.deb
 c08b3be6d1f8a28a7ca9d7906db02cbfd4805f950d7308549fdf9314ad10e4c4 53930 
libmedimportcxx0_2.3.6-5_amd64.deb
 a0ef91bd32397423e37bc8b4cc666f117dd7590444cddb18c99b8f25c1cf643a 498214 
libmedimportcxx-dev_2.3.6-5_amd64.deb
 0eca8da6d5893e819ae69305b299efa9ffe6d0cf100ccd9d1b091a9543aba8eb 35346 
libmed-tools_2.3.6-5_amd64.deb
Files: 
 98390213d2a60203789a7fe62f1933c8 1560 libs optional med-fichier_2.3.6-5.dsc
 2467643174c6246380609c449fefcca4 302560 libs optional 
med-fichier_2.3.6-5.debian.tar.gz
 f75a8a370cf91b18f93b21243d42f098 1361868 doc optional 
libmed-doc_2.3.6-5_all.deb
 14d385fb20ef2c58d3033ecd0c0abc01 141956 libs optional libmed1_2.3.6-5_amd64.deb
 e75051ffa1cd5e99c46929fef991759a 246726 libdevel optional 
libmed-dev_2.3.6-5_amd64.deb
 7c1c5dd0442a70c82a31d797487c2968 116084 libs optional 
libmedc1_2.3.6-5_amd64.deb
 c68723a3860dc8888a9b509bde78503d 203726 libdevel optional 
libmedc-dev_2.3.6-5_amd64.deb
 25e782ae83a83c935a13a6e99c567277 29752 libs optional 
libmedimport0_2.3.6-5_amd64.deb
 6dc1d4c64d9e8fc844837521e8ad5c79 37068 libdevel optional 
libmedimport-dev_2.3.6-5_amd64.deb
 b77fa019a6eef0b19bb07c7012157efb 53930 libs optional 
libmedimportcxx0_2.3.6-5_amd64.deb
 bd1700b035dabb75149e640bc000592f 498214 libdevel optional 
libmedimportcxx-dev_2.3.6-5_amd64.deb
 4269fceba0facdad0ff6ebfdbd15c624 35346 science optional 
libmed-tools_2.3.6-5_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkzyZoUACgkQUm8B6FZO5LbjogCfSPt79/2WjvUU0Xff9rl0dfM0
yu8An1UuCqgELHJV/QSYp31UPhESJkO8
=IV9O
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to