<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Hi,<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">I haven't been following this thread too closely, and I'm not familiar with debian packaging related stuff. But I can help write code :)<br><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">From what I see, we need people to help port python-git?<br><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">From a search on debian packages, this is the package we're talking about: <a href="https://packages.debian.org/wheezy/python-git">https://packages.debian.org/wheezy/python-git</a><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">The homepage no longer exist (<a href="https://gitorious.org/projects/git-python/">https://gitorious.org/projects/git-python/</a>), and I think it got rename as GitPython, which exists here (<a href="https://pypi.python.org/pypi/GitPython/1.0.0">https://pypi.python.org/pypi/GitPython/1.0.0</a>)<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">I'm not sure how we should proceed, either we can port python-git, or package gitpython up (a search for it on <a href="http://packages.debian.org">packages.debian.org</a> turned up empty) and change the dependency.<br></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr">Best,<div>Zhi An</div></div></div></div>
<br><div class="gmail_quote">On Thu, Apr 23, 2015 at 10:55 AM, Paul Tagliamonte <span dir="ltr"><<a href="mailto:paultag@debian.org" target="_blank">paultag@debian.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Thu, Apr 23, 2015 at 02:52:33PM +0200, Enrico Zini wrote:<br>
> On Mon, Apr 20, 2015 at 11:14:28AM -0400, Paul Tagliamonte wrote:<br>
><br>
> > So, round one of all of this is getting the critical path *under* each<br>
> > of our services ready, so that when we need to migrate, we don't need<br>
> > to scramble.<br>
><br>
> There is another constraint that I forgot: the production environment is<br>
> Debian Stable, which will soon mean Jessie. If a python2-only module<br>
> gets ported to python3 in jessie+1, to use it for <a href="http://debian.org" target="_blank">debian.org</a> services<br>
> the python3 version also needs to be maintained in backports.<br>
<br>
Yep! So, my plan that I outlined on d-d-a was to basically attack that --<br>
the depends chains -- first. Since we are doing this before strictly<br>
needed (that is, nearly two cycles out), we can ensure everything is<br>
working and migrated a cycle before we are forced to.<br>
<br>
This gives us a relaxing pace and also lets us target things<br>
pragmatically. You're right, and I'd be happy to help with backporting<br>
stuff for services porting to Python 3 as needed, but there's no urgent<br>
rush to move everything over today.<br>
<br>
That's the idea behind porting now, so that everything's totally tight.<br>
<br>
> For example, I am about to add python-git as a dependency to<br>
> <a href="http://nm.debian.org" target="_blank">nm.debian.org</a>, as I need it to parse the stream of changes that I get<br>
> via the <a href="http://keyring.debian.org" target="_blank">keyring.debian.org</a> git changelog, and python-git is python2-only<br>
> in Jessie[1]. Having python3-git in jessie+1 won't be enough to make<br>
> <a href="http://nm.debian.org" target="_blank">nm.debian.org</a> deployable with python3: python3-git will also need to be<br>
> in jessie-backports, and with a commitment to keep it up to date with<br>
> security uploads, because I'm going to run it every night to parse git<br>
> logs that are obtained via potentially insecure network connections.<br>
<br>
Aye. Yep.<br>
<br>
> Enrico<br>
><br>
> [1] I've recently been really sad to figure out that python-git is<br>
> python2-only, and so is dulwich. As a personal policy, if I start a<br>
> new python project now I start it with python 3.4. I had to start a<br>
> new project with python2 because of that, and I felt dirty.<br>
<br>
Yeah, ditto. I talked with Jelmer about this, there was a patch for Py3,<br>
but it fell too far behind development's trunk. If anyone on the<br>
py3porters wants to do that, it'd seriously help me out too.<br>
<br>
Cheers,<br>
Paul<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
.''`. Paul Tagliamonte <<a href="mailto:paultag@debian.org">paultag@debian.org</a>> | Proud Debian Developer<br>
: :' : 4096R / 8F04 9AD8 2C92 066C 7352 D28A 7B58 5B30 807C 2A87<br>
`. `'` <a href="http://people.debian.org/~paultag" target="_blank">http://people.debian.org/~paultag</a><br>
`- <a href="http://people.debian.org/~paultag/conduct-statement.txt" target="_blank">http://people.debian.org/~paultag/conduct-statement.txt</a><br>
</font></span><br>_______________________________________________<br>
py3porters-devel mailing list<br>
<a href="mailto:py3porters-devel@lists.alioth.debian.org">py3porters-devel@lists.alioth.debian.org</a><br>
<a href="https://lists.alioth.debian.org/mailman/listinfo/py3porters-devel" target="_blank">https://lists.alioth.debian.org/mailman/listinfo/py3porters-devel</a><br>
<br></blockquote></div><br></div>