Re: Bug#785275: ITP: python-ipaddress -- Backport of the ipaddress module from Python 3.3
On Friday, May 22, 2015 12:34:02 AM Brian May wrote: > On Fri, 22 May 2015 at 07:14 Scott Kitterman wrote: > > I was considering the idea of porting things from ipaddr to ipaddress for > > python2, but there's a lot more of that then there is for ipaddress (which > > is > > up to only two packages we know about). > > As it is a goal to have everything Python3 compliant, and as Jessie no > longer has python3-ipaddr (it was in wheezy), everything is going to have > to support ipaddress for python3 anyway. > > I don't see why we don't drop python-ipaddr, and replace it with > python-ipaddress. I dropped python3-ipaddr once python3.3 was default since it comes with ipaddress. For python3, everthing should use ipaddress. At some point it might make sense to switch. There's about 20 packages in the archive that use python-ipaddr versus none with one or two candidates using python-ipaddress in python2. Porting two is easier than porting 20. I'm also concerned that because of type processing differences (strings versus bytes and UTF-8 by default versus not) there is potential for subtle incompatibilities in the backported ipaddress. I had complaints on an upstream project that uses ipaddress with python3 when it was available failing with ipaddress in python2. Scott K -- 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/2512839.pZrC1BOzKj@kitterma-e6430
Re: Bug#785275: ITP: python-ipaddress -- Backport of the ipaddress module from Python 3.3
On Fri, 22 May 2015 at 07:14 Scott Kitterman wrote: > I was considering the idea of porting things from ipaddr to ipaddress for > python2, but there's a lot more of that then there is for ipaddress (which > is > up to only two packages we know about). > As it is a goal to have everything Python3 compliant, and as Jessie no longer has python3-ipaddr (it was in wheezy), everything is going to have to support ipaddress for python3 anyway. I don't see why we don't drop python-ipaddr, and replace it with python-ipaddress.
Re: Bug#785275: ITP: python-ipaddress -- Backport of the ipaddress module from Python 3.3
On Thursday, May 21, 2015 04:07:24 PM Barry Warsaw wrote: > On May 21, 2015, at 03:44 PM, Scott Kitterman wrote: > >>ipaddress is apparently also a new dependency of pip. > > > >For python2? > > Yes, sorry, just for Python 2. > > -Barry So far for python-ipaddress (for python 2), that's two packages. Here's the reverse depends/build-depends for python-ipaddr in sid: Reverse-Build-Depends-Indep === * python-wsme Reverse-Build-Depends = * ganeti * ooniprobe * rtslib * txtorcon root@kitterma-E6430:/# reverse-depends python-ipaddr Reverse-Depends === * automx * bley * blockfinder * criu [amd64 armhf] * ganeti-2.12 [amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd- i386 mips mipsel powerpc ppc64el s390x] * hash-slinger * isso * ooniprobe * python-rtslib * python-spf * python-txtorcon * python-wsme * tcos-core [amd64 arm64 armel armhf i386 mips mipsel powerpc ppc64el s390x sparc] * tcosmonitor-common * virt-manager * web2ldap I was considering the idea of porting things from ipaddr to ipaddress for python2, but there's a lot more of that then there is for ipaddress (which is up to only two packages we know about). I don't think we want the duplication in Debian and so pip ought to be patched to use ipaddr. Scott K -- 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/39806477.qUvlhOcsiX@kitterma-e6430
Re: Bug#785275: ITP: python-ipaddress -- Backport of the ipaddress module from Python 3.3
On May 21, 2015, at 03:44 PM, Scott Kitterman wrote: >>ipaddress is apparently also a new dependency of pip. > >For python2? Yes, sorry, just for Python 2. -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/20150521160724.69f36...@limelight.wooz.org
Re: Bug#785275: ITP: python-ipaddress -- Backport of the ipaddress module from Python 3.3
On May 21, 2015 3:37:46 PM EDT, Barry Warsaw wrote: >On May 14, 2015, at 12:04 AM, Scott Kitterman wrote: > >>On Thursday, May 14, 2015 05:42:56 AM Tristan Seligmann wrote: >>> Package: wnpp >>> Severity: wishlist >>> Owner: Tristan Seligmann >>> >>> * Package name: python-ipaddress >>> Version : 1.0.7 >>> Upstream Author : Philipp Hagemeister >>> * URL : https://github.com/phihag/ipaddress >>> * License : PSF >>> Programming Lang: Python >>> Description : Backport of the ipaddress module from Python 3.3 >>> >>> This is a new dependency of python-cryptography. I intend to >maintain the >>> package in DPMT. >> >>Why can't python-cryptography use python-ipaddr that's already in the >>archive? > >ipaddress is apparently also a new dependency of pip. For python2? Scott K -- 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/cf32eff6-95aa-4296-b5b4-41ebd9a8a...@kitterman.com
Re: Bug#785275: ITP: python-ipaddress -- Backport of the ipaddress module from Python 3.3
On May 14, 2015, at 12:04 AM, Scott Kitterman wrote: >On Thursday, May 14, 2015 05:42:56 AM Tristan Seligmann wrote: >> Package: wnpp >> Severity: wishlist >> Owner: Tristan Seligmann >> >> * Package name: python-ipaddress >> Version : 1.0.7 >> Upstream Author : Philipp Hagemeister >> * URL : https://github.com/phihag/ipaddress >> * License : PSF >> Programming Lang: Python >> Description : Backport of the ipaddress module from Python 3.3 >> >> This is a new dependency of python-cryptography. I intend to maintain the >> package in DPMT. > >Why can't python-cryptography use python-ipaddr that's already in the >archive? ipaddress is apparently also a new dependency of pip. Cheers, -Barry pgpjc0ewEdJPw.pgp Description: OpenPGP digital signature
Re: Can't create directory '/svn/python-modules/db/transactions/32752-1.txn': Permission denied
On Thu, May 21, 2015 at 12:08 PM, Ansgar Burchardt wrote: > Hi, > > On 05/21/2015 11:59 AM, Mathieu Malaterre wrote: >> Has anyone seen this lately: >> >> $ svn ci -m"prepare package" >> Sendingdebian/changelog >> Sendingdebian/control >> Sendingdebian/rules >> Sendingdebian/watch >> Transmitting file data svn: E13: Commit failed (details follow): >> svn: E13: Can't create directory >> '/svn/python-modules/db/transactions/32752-1.txn': Permission denied >> >> Who should I get in touch with ? > > The permissions for the directory look correct to me, but "malat" is not > a member of the scm_python-modules group, nor of the python-modules > group on Alioth. > > I assume you need join the Alioth project to get commit permissions. Thanks Ansgar, that was obvious :( -- Mathieu -- 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/ca+7wuszv0+shj57fetmw+khyqx4dhfspfweh+hbtrpslc+v...@mail.gmail.com
Re: Can't create directory '/svn/python-modules/db/transactions/32752-1.txn': Permission denied
On Thursday, May 21, 2015 12:08:23 PM Ansgar Burchardt wrote: > Hi, > > On 05/21/2015 11:59 AM, Mathieu Malaterre wrote: > > Has anyone seen this lately: > > > > $ svn ci -m"prepare package" > > Sendingdebian/changelog > > Sendingdebian/control > > Sendingdebian/rules > > Sendingdebian/watch > > Transmitting file data svn: E13: Commit failed (details follow): > > svn: E13: Can't create directory > > '/svn/python-modules/db/transactions/32752-1.txn': Permission denied > > > > Who should I get in touch with ? > > The permissions for the directory look correct to me, but "malat" is not > a member of the scm_python-modules group, nor of the python-modules > group on Alioth. > > I assume you need join the Alioth project to get commit permissions. Just to close out the thread, I approved his request, so it should be resolved now. AFAIR, when Alioth got split into two, all DDs having access got broken. No idea when or if it gets repaired. Scott K -- 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/5306867.jtJUp49J4h@kitterma-e6430
Re: Can't create directory '/svn/python-modules/db/transactions/32752-1.txn': Permission denied
Hi, On 05/21/2015 11:59 AM, Mathieu Malaterre wrote: > Has anyone seen this lately: > > $ svn ci -m"prepare package" > Sendingdebian/changelog > Sendingdebian/control > Sendingdebian/rules > Sendingdebian/watch > Transmitting file data svn: E13: Commit failed (details follow): > svn: E13: Can't create directory > '/svn/python-modules/db/transactions/32752-1.txn': Permission denied > > Who should I get in touch with ? The permissions for the directory look correct to me, but "malat" is not a member of the scm_python-modules group, nor of the python-modules group on Alioth. I assume you need join the Alioth project to get commit permissions. Ansgar -- 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/555dae97.5030...@debian.org
Can't create directory '/svn/python-modules/db/transactions/32752-1.txn': Permission denied
[CC me please] Has anyone seen this lately: $ svn ci -m"prepare package" Sendingdebian/changelog Sendingdebian/control Sendingdebian/rules Sendingdebian/watch Transmitting file data svn: E13: Commit failed (details follow): svn: E13: Can't create directory '/svn/python-modules/db/transactions/32752-1.txn': Permission denied Who should I get in touch with ? -- 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/ca+7wusyhwnvz7fr_j07pecwzcq0xov8pagsp1wj7ssfwjmv...@mail.gmail.com
