Bug#767554: python-persistent and python-zodb: error when trying to install together

2014-12-08 Thread Barry Warsaw
On Dec 08, 2014, at 01:47 PM, Arnaud Fontaine wrote:

 Arnaud Fontaine wrote (26 Nov 2014 09:03:09 GMT) :
 Really sorry about  that. FTR, I have not uploaded  anything yet because
 the release  team would prefer  to avoid  the Conflicts if  possible and
 make python-zodb depends upon  python-persistent instead. AFAIK, it does
 not seem to be an issue but I have just sent an email to upstream author
 to confirm it's not going to be an issue...

 Any answer from them?

Yes, sorry about  the lag. The upstream said there  should be no problem
for  python-zodb  to  Depends  on  python-persistent  (and  thus  remove
persistent module from python-zodb). Barry:  if that's ok, I will upload
python-persistent  with  the   Breaks/Replaces  and  upload  python-zodb
without persistent module?

+1, and thanks!


pgpshxyGCDV83.pgp
Description: OpenPGP digital signature


Bug#767554: python-persistent and python-zodb: error when trying to install together

2014-12-07 Thread Arnaud Fontaine
Hi,

 Arnaud Fontaine wrote (26 Nov 2014 09:03:09 GMT) :
 Really sorry about  that. FTR, I have not uploaded  anything yet because
 the release  team would prefer  to avoid  the Conflicts if  possible and
 make python-zodb depends upon  python-persistent instead. AFAIK, it does
 not seem to be an issue but I have just sent an email to upstream author
 to confirm it's not going to be an issue...

 Any answer from them?

Yes, sorry about  the lag. The upstream said there  should be no problem
for  python-zodb  to  Depends  on  python-persistent  (and  thus  remove
persistent module from python-zodb). Barry:  if that's ok, I will upload
python-persistent  with  the   Breaks/Replaces  and  upload  python-zodb
without persistent module?

Cheers,
-- 
Arnaud Fontaine


signature.asc
Description: PGP signature


Bug#767554: python-persistent and python-zodb: error when trying to install together

2014-12-06 Thread intrigeri
Hi Arnaud,

Arnaud Fontaine wrote (26 Nov 2014 09:03:09 GMT) :
 Really sorry about  that. FTR, I have not uploaded  anything yet because
 the release  team would prefer  to avoid  the Conflicts if  possible and
 make python-zodb depends upon  python-persistent instead. AFAIK, it does
 not seem to be an issue but I have just sent an email to upstream author
 to confirm it's not going to be an issue...

Any answer from them?

Cheers,
--
intrigeri


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#767554: python-persistent and python-zodb: error when trying to install together

2014-11-26 Thread Arnaud Fontaine
Hello,

Andreas Beckmann a...@debian.org writes:

 Followup-For: Bug #767554
 Control: found -1 767554 4.0.8-2

 The Conflicts does not work ... without the proper epoch ... you need

   Conflicts: python-zodb ( 1:3.11.0~)


   Selecting previously unselected package python-persistent.
   Unpacking python-persistent (from .../python-persistent_4.0.8-2_amd64.deb) 
 ...
   dpkg: error processing 
 /var/cache/apt/archives/python-persistent_4.0.8-2_amd64.deb (--unpack):
trying to overwrite '/usr/lib/python2.7/dist-packages/persistent/dict.py', 
 which is also in package python-zodb 1:3.9.7-2
   Errors were encountered while processing:
/var/cache/apt/archives/python-persistent_4.0.8-2_amd64.deb

Really sorry about  that. FTR, I have not uploaded  anything yet because
the release  team would prefer  to avoid  the Conflicts if  possible and
make python-zodb depends upon  python-persistent instead. AFAIK, it does
not seem to be an issue but I have just sent an email to upstream author
to confirm it's not going to be an issue...

Cheers,
-- 
Arnaud Fontaine


signature.asc
Description: PGP signature


Bug#767554: python-persistent and python-zodb: error when trying to install together

2014-11-19 Thread Andreas Beckmann
Followup-For: Bug #767554
Control: found -1 767554 4.0.8-2

The Conflicts does not work ... without the proper epoch ... you need

  Conflicts: python-zodb ( 1:3.11.0~)


  Selecting previously unselected package python-persistent.
  Unpacking python-persistent (from .../python-persistent_4.0.8-2_amd64.deb) ...
  dpkg: error processing 
/var/cache/apt/archives/python-persistent_4.0.8-2_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/python2.7/dist-packages/persistent/dict.py', 
which is also in package python-zodb 1:3.9.7-2
  Errors were encountered while processing:
   /var/cache/apt/archives/python-persistent_4.0.8-2_amd64.deb


Andreas


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#767554: python-persistent and python-zodb: error when trying to install together

2014-11-16 Thread Arnaud Fontaine
Hi,

Gediminas Paulauskas mene...@pov.lt writes:

 If that's ok with you, I'm going to upload both packages to fix this bug:

 * python-persistent:
   Conflicts: python-zodb ( 3.11.0~)

 * python-zodb:
   Conflicts: python-persistent


 Since ZODB3 before the split included persistent, it should provide it:

 Provides: python-persistent

 One package that Build-Depends on python-persistent but should be
 installable with only python-zodb is zope.component.

Thank you very much for pointing this out. I will upload now with the
Provides then.

Cheers,
-- 
Arnaud Fontaine


signature.asc
Description: PGP signature


Bug#767554: python-persistent and python-zodb: error when trying to install together

2014-11-14 Thread Arnaud Fontaine
Barry Warsaw ba...@debian.org writes:

 On Nov 12, 2014, at 05:50 PM, Arnaud Fontaine wrote:

From upstream point  of view, ZODB3 (aka python-zodb in  Debian) used to
include persistent, BTrees,  ZODB and ZEO modules.  However, since ZODB3
3.11.0a1, upstream  has split it  up into  4 distinct packages  (one for
each module),  bump the version  to 4.0  and made ZODB3  a metapackage
depending on all of them.

 It looks like Debian still has zodb 3.9.7, right?

Unfortunately, yes.

As of  fixing this RC  bug for Jessie:  Among the four,  only persistent
package is currently available in Debian, so  there is no way to get rid
of  ZODB3 (at  least for  Jessie). Barry:  If persistent  = 4.0  Debian
package is useful on  its own to anyone (and thus  should not be removed
From testing),  then can I  add a Conflict  on both packages  and upload
them to fix this bug?

 IIRC, I needed to update python-persistent for the Python 3 zope.component
 transition, as it's a build-dep.  There are no other reverse dependencies that
 I know of.

 I think a Conflicts is the right way to handle this for now, given where we
 are in the Jessie release cycle.  Arnaud, thanks for handling this!

If that's ok with you, I'm going to upload both packages to fix this bug:

* python-persistent:
  Conflicts: python-zodb ( 3.11.0~)

* python-zodb:
  Conflicts: python-persistent

Cheers,
-- 
Arnaud Fontaine


signature.asc
Description: PGP signature


Bug#767554: python-persistent and python-zodb: error when trying to install together

2014-11-14 Thread Gediminas Paulauskas
2014-11-14 11:43 GMT+02:00 Arnaud Fontaine ar...@debian.org:

 Barry Warsaw ba...@debian.org writes:

  On Nov 12, 2014, at 05:50 PM, Arnaud Fontaine wrote:
 
 From upstream point  of view, ZODB3 (aka python-zodb in  Debian) used to
 include persistent, BTrees,  ZODB and ZEO modules.  However, since ZODB3
 3.11.0a1, upstream  has split it  up into  4 distinct packages  (one for
 each module),  bump the version  to 4.0  and made ZODB3  a metapackage
 depending on all of them.
 
  It looks like Debian still has zodb 3.9.7, right?

 Unfortunately, yes.

 As of  fixing this RC  bug for Jessie:  Among the four,  only persistent
 package is currently available in Debian, so  there is no way to get rid
 of  ZODB3 (at  least for  Jessie). Barry:  If persistent  = 4.0  Debian
 package is useful on  its own to anyone (and thus  should not be removed
 From testing),  then can I  add a Conflict  on both packages  and upload
 them to fix this bug?
 
  IIRC, I needed to update python-persistent for the Python 3
 zope.component
  transition, as it's a build-dep.  There are no other reverse
 dependencies that
  I know of.
 
  I think a Conflicts is the right way to handle this for now, given where
 we
  are in the Jessie release cycle.  Arnaud, thanks for handling this!

 If that's ok with you, I'm going to upload both packages to fix this bug:

 * python-persistent:
   Conflicts: python-zodb ( 3.11.0~)

 * python-zodb:
   Conflicts: python-persistent


Since ZODB3 before the split included persistent, it should provide it:

Provides: python-persistent

One package that Build-Depends on python-persistent but should be
installable with only python-zodb is zope.component.

-- 
Gediminas


Bug#767554: python-persistent and python-zodb: error when trying to install together

2014-11-12 Thread Arnaud Fontaine
Hello,

Andreas Beckmann a...@debian.org writes:

  Package: python-persistent,python-zodb
  Version: 4.0.8-1
  Severity: serious
  User: trei...@debian.org
  Usertags: edos-file-overwrite
  Control: found -1 1:3.9.7-2

First of all, thanks for finding and reporting such issues, it's greatly
appreciated!

   Selecting previously unselected package python-zodb.
   Preparing to unpack .../python-zodb_1%3a3.9.7-2_amd64.deb ...
   Unpacking python-zodb (1:3.9.7-2) ...
   dpkg: error processing archive 
 /var/cache/apt/archives/python-zodb_1%3a3.9.7-2_amd64.deb (--unpack):
trying to overwrite '/usr/lib/python2.7/dist-packages/persistent/wref.py', 
 which is also in package python-persistent 4.0.8-1
   Errors were encountered while processing:
/var/cache/apt/archives/python-zodb_1%3a3.9.7-2_amd64.deb

 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.7/dist-packages/persistent/__init__.py
   [...]

From upstream point  of view, ZODB3 (aka python-zodb in  Debian) used to
include persistent, BTrees,  ZODB and ZEO modules.  However, since ZODB3
3.11.0a1, upstream  has split it  up into  4 distinct packages  (one for
each module),  bump the version  to 4.0  and made ZODB3  a metapackage
depending on all of them.

As of  fixing this RC  bug for Jessie:  Among the four,  only persistent
package is currently available in Debian, so  there is no way to get rid
of  ZODB3 (at  least for  Jessie). Barry:  If persistent  = 4.0  Debian
package is useful on  its own to anyone (and thus  should not be removed
From testing),  then can I  add a Conflict  on both packages  and upload
them to fix this bug?

Cheers,
-- 
Arnaud Fontaine


signature.asc
Description: PGP signature


Bug#767554: python-persistent and python-zodb: error when trying to install together

2014-11-12 Thread Barry Warsaw
On Nov 12, 2014, at 05:50 PM, Arnaud Fontaine wrote:

From upstream point  of view, ZODB3 (aka python-zodb in  Debian) used to
include persistent, BTrees,  ZODB and ZEO modules.  However, since ZODB3
3.11.0a1, upstream  has split it  up into  4 distinct packages  (one for
each module),  bump the version  to 4.0  and made ZODB3  a metapackage
depending on all of them.

It looks like Debian still has zodb 3.9.7, right?

As of  fixing this RC  bug for Jessie:  Among the four,  only persistent
package is currently available in Debian, so  there is no way to get rid
of  ZODB3 (at  least for  Jessie). Barry:  If persistent  = 4.0  Debian
package is useful on  its own to anyone (and thus  should not be removed
From testing),  then can I  add a Conflict  on both packages  and upload
them to fix this bug?

IIRC, I needed to update python-persistent for the Python 3 zope.component
transition, as it's a build-dep.  There are no other reverse dependencies that
I know of.

I think a Conflicts is the right way to handle this for now, given where we
are in the Jessie release cycle.  Arnaud, thanks for handling this!


signature.asc
Description: PGP signature


Bug#767554: python-persistent and python-zodb: error when trying to install together

2014-10-31 Thread Andreas Beckmann
Package: python-persistent,python-zodb
Version: 4.0.8-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 1:3.9.7-2

Architecture: amd64
Distribution: jessie

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:

  Selecting previously unselected package python-zodb.
  Preparing to unpack .../python-zodb_1%3a3.9.7-2_amd64.deb ...
  Unpacking python-zodb (1:3.9.7-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-zodb_1%3a3.9.7-2_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/python2.7/dist-packages/persistent/wref.py', 
which is also in package python-persistent 4.0.8-1
  Errors were encountered while processing:
   /var/cache/apt/archives/python-zodb_1%3a3.9.7-2_amd64.deb

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.7/dist-packages/persistent/__init__.py
  usr/lib/python2.7/dist-packages/persistent/cPersistence.h
  usr/lib/python2.7/dist-packages/persistent/dict.py
  usr/lib/python2.7/dist-packages/persistent/interfaces.py
  usr/lib/python2.7/dist-packages/persistent/list.py
  usr/lib/python2.7/dist-packages/persistent/mapping.py
  usr/lib/python2.7/dist-packages/persistent/ring.h
  usr/lib/python2.7/dist-packages/persistent/tests/__init__.py
  usr/lib/python2.7/dist-packages/persistent/tests/test_list.py
  usr/lib/python2.7/dist-packages/persistent/tests/test_mapping.py
  usr/lib/python2.7/dist-packages/persistent/tests/test_wref.py
  usr/lib/python2.7/dist-packages/persistent/tests/utils.py
  usr/lib/python2.7/dist-packages/persistent/wref.py

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.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see http://edos.debian.net/file-overwrites/.


python-persistent=4.0.8-1_python-zodb=1%3.9.7-2.log.gz
Description: application/gzip