Your message dated Sun, 22 Jan 2012 22:04:38 +0100
with message-id <4f1c79e6.3010...@gmail.com>
and subject line axis2c -dev conflicts solved with 1.6.0-4
has caused the Debian Bug report #655838,
regarding libaxis2c0 and libaxis2c-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 ow...@bugs.debian.org
immediately.)
--
655838: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655838
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libaxis2c-dev,libaxis2c0
Version: libaxis2c-dev/1.6.0-2.2
Version: libaxis2c0/1.6.0-2.2
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Date: 2012-01-14
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!
libxml2 libapr1 libc-dev-bin linux-libc-dev libc6-dev uuid-dev libapr1-dev
libaxis2c0 libxml2-dev libaxis2c-dev
Authentication warning overridden.
Can not write log, openpty() failed (/dev/pts not mounted?)
Selecting previously unselected package libxml2.
(Reading database ... 10520 files and directories currently installed.)
Unpacking libxml2 (from .../libxml2_2.7.8.dfsg-5.1_amd64.deb) ...
Selecting previously unselected package libapr1.
Unpacking libapr1 (from .../libapr1_1.4.5-1.1_amd64.deb) ...
Selecting previously unselected package libc-dev-bin.
Unpacking libc-dev-bin (from .../libc-dev-bin_2.13-24_amd64.deb) ...
Selecting previously unselected package linux-libc-dev.
Unpacking linux-libc-dev (from .../linux-libc-dev_3.1.8-2_amd64.deb) ...
Selecting previously unselected package libc6-dev.
Unpacking libc6-dev (from .../libc6-dev_2.13-24_amd64.deb) ...
Selecting previously unselected package uuid-dev.
Unpacking uuid-dev (from .../uuid-dev_2.20.1-1.1_amd64.deb) ...
Selecting previously unselected package libapr1-dev.
Unpacking libapr1-dev (from .../libapr1-dev_1.4.5-1.1_amd64.deb) ...
Selecting previously unselected package libaxis2c0.
Unpacking libaxis2c0 (from .../libaxis2c0_1.6.0-2.2_amd64.deb) ...
Selecting previously unselected package libxml2-dev.
Unpacking libxml2-dev (from .../libxml2-dev_2.7.8.dfsg-5.1_amd64.deb) ...
Selecting previously unselected package libaxis2c-dev.
Unpacking libaxis2c-dev (from .../libaxis2c-dev_1.6.0-2.2_amd64.deb) ...
dpkg: error processing
/var/cache/apt/archives/libaxis2c-dev_1.6.0-2.2_amd64.deb (--unpack):
trying to overwrite '/usr/lib/axis2/lib/libaxis2_xpath.so', which is also in
package libaxis2c0 1.6.0-2.2
configured to not write apport reports
Processing triggers for man-db ...
Errors were encountered while processing:
/var/cache/apt/archives/libaxis2c-dev_1.6.0-2.2_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/lib/axis2/lib/libaxis2_axiom.so
/usr/lib/axis2/lib/libaxis2_engine.so
/usr/lib/axis2/lib/libaxis2_http_common.so
/usr/lib/axis2/lib/libaxis2_http_receiver.so
/usr/lib/axis2/lib/libaxis2_http_sender.so
/usr/lib/axis2/lib/libaxis2_parser.so
/usr/lib/axis2/lib/libaxis2_xpath.so
-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 ---
It was just accepted in unstable.
Thanks
Steffen
--- End Message ---
