Re: ITP persistent and merging zope and python teams?
On Jun 27, 2014, at 12:06 PM, Arnaud Fontaine wrote: I'm not really active lately but I think it would be a good idea to move most of packages (the ones listed by Brian in his previous email seems fine to me) to DPMT. Note that there appears to be 48 packages maintained by the Zope team: http://qa.debian.org/developer.php?login=pkg-zope-developers%40lists.alioth.debian.orgcomaint=yes I'm not so sure about zope2.12 and zope2.13 but it looks like most of the others could be moved over to DPMT. BTW, even if this document is not up-to-date, we used to target ZTK version: https://wiki.debian.org/Zope/ZTK . Shall we keep doing that? That's a good question. I've been using the assumption that if it's available on PyPI, then it must be blessed for general purpose use. Maybe that's a bad assumption. Even the ZTK trunk page is out of date: http://docs.zope.org/zopetoolkit/releases/overview-trunk.html since at least I know that most of the latest versions on PyPI now support Python 3.4. Are either the Debian wiki or the docs.zope.org pages still relevant? We still haven't heard from Gediminas yet, so I think we should wait a little longer. Should we ask for opinions on debian-devel or just let them know once/if the deed is done? -Barry signature.asc Description: PGP signature
Re: ITP persistent and merging zope and python teams?
Hi, Barry Warsaw ba...@debian.org writes: As a side question, I wonder if it still makes sense to continue to segregate the ZTK packages under pkg-zope-developers. Why not fold all/most/some of those packages into DPMT? They're both under svn so it should be pretty easy to do, and the DPMT seems to be the much more active team than p-z-d. Thoughts? I'm not really active lately but I think it would be a good idea to move most of packages (the ones listed by Brian in his previous email seems fine to me) to DPMT. BTW, even if this document is not up-to-date, we used to target ZTK version: https://wiki.debian.org/Zope/ZTK . Shall we keep doing that? Cheers, -- Arnaud Fontaine -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87a98z2gre@duckcorp.org
ITP persistent and merging zope and python teams?
AFAICT, the persistent library is not yet packaged for Debian. https://pypi.python.org/pypi/persistent/4.0.8 I've search for existing packages and wnpp/ITP and not found anything. I think this is also required as a build dependency for zope.component. It's possible I've missed it though, so I'm going to file an ITP and work on the packaging, but please do let me know if it's already available. I'm aware of python-zope.component-persistentregistry, but that's a metapackage and not specifically related to the above. I plan on naming the source package `python-persistent` since claiming `persistent` seems a bit presumptuous. I'm going to put it under DPMT. As a side question, I wonder if it still makes sense to continue to segregate the ZTK packages under pkg-zope-developers. Why not fold all/most/some of those packages into DPMT? They're both under svn so it should be pretty easy to do, and the DPMT seems to be the much more active team than p-z-d. Thoughts? Cheers, -Barry -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140625105058.6716d...@anarchist.wooz.org
Re: ITP persistent and merging zope and python teams?
On Wed, Jun 25, 2014 at 10:50:58AM -0400, Barry Warsaw wrote: AFAICT, the persistent library is not yet packaged for Debian. https://pypi.python.org/pypi/persistent/4.0.8 I've search for existing packages and wnpp/ITP and not found anything. I think this is also required as a build dependency for zope.component. It's possible I've missed it though, so I'm going to file an ITP and work on the packaging, but please do let me know if it's already available. I'm aware of python-zope.component-persistentregistry, but that's a metapackage and not specifically related to the above. I plan on naming the source package `python-persistent` since claiming `persistent` seems a bit presumptuous. I'm going to put it under DPMT. As a side question, I wonder if it still makes sense to continue to segregate the ZTK packages under pkg-zope-developers. Why not fold all/most/some of those packages into DPMT? They're both under svn so it should be pretty easy to do, and the DPMT seems to be the much more active team than p-z-d. Thoughts? As I mentioned before, I think it's a great idea :) I think that you should give it some time for any objections to be raised. If none are, you should go ahead. Perhaps seek out Gediminas' opinion. As he is the next most active member of pkg-zope-developers and would probably have to join DPMT to carry on with the ZRK package maintenance. Cheers, -Barry ___ pkg-zope-developers mailing list pkg-zope-develop...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-zope-developers -- Brian Sutherland -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140625193113.GA60845@Brians-MacBook-Air.local
