Your message dated Tue, 27 Mar 2012 18:55:30 +0200
with message-id 
<caodxvv7td+p08ah-mza3fgdntdsn+rke_vxrzn1dqmti0h1...@mail.gmail.com>
and subject line 
has caused the Debian Bug report #663510,
regarding python-factory-boy and factory-boy: 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.)


-- 
663510: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663510
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: factory-boy,python-factory-boy
Version: factory-boy/1.1.2-1
Version: python-factory-boy/1.1.3-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2012-03-11
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!
  libexpat1 libdb4.8 mime-support python2.7-minimal python2.7 python-minimal
  python factory-boy python-factory-boy
Authentication warning overridden.
Can not write log, openpty() failed (/dev/pts not mounted?)
Selecting previously unselected package libexpat1.
(Reading database ... 10555 files and directories currently installed.)
Unpacking libexpat1 (from .../libexpat1_2.0.1-7.2_amd64.deb) ...
Selecting previously unselected package libdb4.8.
Unpacking libdb4.8 (from .../libdb4.8_4.8.30-11_amd64.deb) ...
Selecting previously unselected package mime-support.
Unpacking mime-support (from .../mime-support_3.52-1_all.deb) ...
Selecting previously unselected package python2.7-minimal.
Unpacking python2.7-minimal (from .../python2.7-minimal_2.7.3~rc1-1_amd64.deb) 
...
Selecting previously unselected package python2.7.
Unpacking python2.7 (from .../python2.7_2.7.3~rc1-1_amd64.deb) ...
Selecting previously unselected package python-minimal.
Unpacking python-minimal (from .../python-minimal_2.7.2-10_all.deb) ...
Selecting previously unselected package python.
Unpacking python (from .../python_2.7.2-10_all.deb) ...
Selecting previously unselected package factory-boy.
Unpacking factory-boy (from .../factory-boy_1.1.2-1_amd64.deb) ...
Selecting previously unselected package python-factory-boy.
Unpacking python-factory-boy (from .../python-factory-boy_1.1.3-1_amd64.deb) ...
dpkg: error processing 
/var/cache/apt/archives/python-factory-boy_1.1.3-1_amd64.deb (--unpack):
 trying to overwrite '/usr/share/pyshared/factory/containers.py', which is also 
in package factory-boy 1.1.2-1
configured to not write apport reports
Processing triggers for man-db ...
Errors were encountered while processing:
 /var/cache/apt/archives/python-factory-boy_1.1.3-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/lib/python2.6/dist-packages/factory/__init__.py
  /usr/lib/python2.6/dist-packages/factory/base.py
  /usr/lib/python2.6/dist-packages/factory/containers.py
  /usr/lib/python2.6/dist-packages/factory/declarations.py
  /usr/lib/python2.7/dist-packages/factory/__init__.py
  /usr/lib/python2.7/dist-packages/factory/base.py
  /usr/lib/python2.7/dist-packages/factory/containers.py
  /usr/lib/python2.7/dist-packages/factory/declarations.py
  /usr/share/pyshared/factory/__init__.py
  /usr/share/pyshared/factory/base.py
  /usr/share/pyshared/factory/containers.py
  /usr/share/pyshared/factory/declarations.py

-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 ---
Debian binary package renamed. As soon as python-factory-boy promotes
to testing (by closing this bug), this will be fixed.


-- 
Pinky: "Gee, Brain, what do you want to do tonight?"
The Brain: "The same thing we do every night, Pinky—try to take over the world!"

 .''`.  Pienso, Luego Incordio
: :' :
`. `'
  `-    www.debian.org    www.openstack.com

GPG Key: 26F020F7
GPG fingerprint: 4986 39DA D152 050B 4699  9A71 66DB 5A36 26F0 20F7


--- End Message ---

Reply via email to