Bug#812309: [PKG-Openstack-devel] Bug#812309: python-trollius: upgrade to version 2.0
On Fri, Feb 5, 2016 at 2:52 PM, Thomas Goirand wrote: > On 02/05/2016 05:23 PM, Sandro Tosi wrote: >>> I've been working on this, and there's an issue when running unit tests >> >> i see you just pushed the changes for 2.0 (they were not there when I >> sent my emails/bug) > > Yes, and the version 2.1~b1 currently in the Git should work. Though I > still prefer to wait for upstream to release before uploading to Debian. > Hopefully, this will happen today. If not, I'll upload 2.1~b1. any idea why the release has been delayed? just lack of time or some tech issues? Also, I would like to have that version in Jessie: would you like to take care of the backport yourself or prefer me to do it? Regards, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
Bug#812309: [PKG-Openstack-devel] Bug#812309: python-trollius: upgrade to version 2.0
On 02/05/2016 05:23 PM, Sandro Tosi wrote: >> I've been working on this, and there's an issue when running unit tests > > i see you just pushed the changes for 2.0 (they were not there when I > sent my emails/bug) Yes, and the version 2.1~b1 currently in the Git should work. Though I still prefer to wait for upstream to release before uploading to Debian. Hopefully, this will happen today. If not, I'll upload 2.1~b1. >> in Python 3.5. I'm working on this with upstream (who's a friend of >> mine, and who I'm chatting with on IRC). Please hold on. > > do you have any reference (or more details to share) about the problem > running tests with 3.5, like an upstream bug report? Sorry, I don't, all was informal on IRC. But you can check the trollius branch of: https://github.com/haypo/trollius What fixed the issue was the last 5 commits. Cheers, Thomas Goirand (zigo)
Bug#812309: [PKG-Openstack-devel] Bug#812309: python-trollius: upgrade to version 2.0
On 02/03/2016 06:13 PM, Sandro Tosi wrote: >> trollius 2.0 has been released: https://pypi.python.org/pypi/trollius , >> please >> package it. > > In the next few days, I will prepare the new upstream release and > upload it to unstable; if you prefer to handle it yourself, please do > that asap. > > Thanks, FYI, I already tested the latest commit from what's going to be released as version 2.1, fixing the Python 3.5 issues. If you want to test it, it's already in the git repository on Alioth, which I tagged as version 2.1~b1 (ie: 2.1_b1 as tag for the upstream branch, as git doesn't support the ~ char). This is what I'm going to upload (ie: 2.1) when Victor Stinner releases it in a few hours, not 2.0. By the way, upstream isn't very happy with this project, and would like to find another person for maintaining it. I thought you may be interested by reading this thread: https://groups.google.com/forum/#!topic/python-tulip/mecVwhnVP0A Though after a conversation with him on IRC, he still pushed the fixes for Python 3.5. So I'm not sure what's going to be the faith of this package upstream. Cheers, Thomas Goirand (zigo)
Bug#812309: [PKG-Openstack-devel] Bug#812309: python-trollius: upgrade to version 2.0
> I've been working on this, and there's an issue when running unit tests i see you just pushed the changes for 2.0 (they were not there when I sent my emails/bug) > in Python 3.5. I'm working on this with upstream (who's a friend of > mine, and who I'm chatting with on IRC). Please hold on. do you have any reference (or more details to share) about the problem running tests with 3.5, like an upstream bug report? -- Sandro "morph" Tosi My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
Bug#812309: [PKG-Openstack-devel] Bug#812309: python-trollius: upgrade to version 2.0
On 02/03/2016 06:13 PM, Sandro Tosi wrote: >> trollius 2.0 has been released: https://pypi.python.org/pypi/trollius , >> please >> package it. > > In the next few days, I will prepare the new upstream release and > upload it to unstable; if you prefer to handle it yourself, please do > that asap. > > Thanks, I've been working on this, and there's an issue when running unit tests in Python 3.5. I'm working on this with upstream (who's a friend of mine, and who I'm chatting with on IRC). Please hold on. Cheers, Thomas Goirand (zigo)
