Re: updating packages

2017-08-02 Thread Michael Fladischer
On 2017-08-01 11:58, Christopher Hoskin wrote: > What's the plan for moving them to unstable? Are they still using git > pq rather than git-dpm? No plan yet for an upload to unstable. amqp and kombu have quite a few reverse dependencies and I did no have the time yet to try a rebuild on them. All

Re: updating packages

2017-08-01 Thread Brian May
Christopher Hoskin writes: > What's the plan for moving them to unstable? Are they still using git > pq rather than git-dpm? I have updated celery to use git pq. Not done kombu or python-amqp yet however. -- Brian May

Re: updating packages

2017-08-01 Thread Christopher Hoskin
Great, thanks! What's the plan for moving them to unstable? Are they still using git pq rather than git-dpm? Christopher On 1 August 2017 at 09:22, Michael Fladischer wrote: > Hi guys, > > On 2017-07-29 12:48, Christopher Hoskin wrote: >> I was going to look at updating vine, kombu and python-

Re: updating packages

2017-08-01 Thread Michael Fladischer
Hi guys, On 2017-07-29 12:48, Christopher Hoskin wrote: > I was going to look at updating vine, kombu and python-ampq this > weekend, but the upstream tarballs have been signed by a different key > pair than the one advertised at: > > http://docs.celeryproject.org/en/latest/contributing.html#secu

Re: updating packages

2017-07-30 Thread Brian May
Christopher Hoskin writes: > As sphinx is used for documentation, even if you're building a python2 > package, you can use the python3 sphinx. Build-depends on > python3-sphinx and Build-Conflicts on python-sphinx. Yes, was wondering that. > I was going to look at updating vine, kombu and pytho

Re: updating packages

2017-07-29 Thread Christopher Hoskin
> Only has a Python 3 version. Not sure if this matters. > As sphinx is used for documentation, even if you're building a python2 package, you can use the python3 sphinx. Build-depends on python3-sphinx and Build-Conflicts on python-sphinx. See e.g. https://anonscm.debian.org/cgit/python-modules

Re: updating packages

2017-07-29 Thread Brian May
Christopher Hoskin writes: > sphinx_celery is already packaged as sphinx-celery: > > https://packages.qa.debian.org/s/sphinx-celery.html Only has a Python 3 version. Not sure if this matters. At the moment, when I try to build djangorestframework I get the following error. Maybe jinja2 is too o

Re: updating packages

2017-07-29 Thread Christopher Hoskin
Dear Brian, sphinx_celery is already packaged as sphinx-celery: https://packages.qa.debian.org/s/sphinx-celery.html Christopher On 3 July 2017 at 23:23, Brian May wrote: > Hello, > > I have started updating packages, trying to fix Django 1.11 issues where > applicable, but seem t

Re: updating packages

2017-07-29 Thread Brian May
fladischermich...@fladi.at writes: > I made some changes to the django-filter package in git. Could you check > if it fixes your issues? Right now 1.0.4-1 builds fine for me with the > current version of DRF in unstable. Looks fine to me, uploaded. Thanks -- Brian May

Re: updating packages

2017-07-25 Thread FladischerMichael
Hi Brian, Quoting Brian May : I have started updating packages, trying to fix Django 1.11 issues where applicable, but seem to be running into road blocks for everything I try. Have updated git. Help appreciated: * django-filter, requires djangorestframework. I made some changes to the

updating packages

2017-07-03 Thread Brian May
Hello, I have started updating packages, trying to fix Django 1.11 issues where applicable, but seem to be running into road blocks for everything I try. Have updated git. Help appreciated: * django-filter, requires djangorestframework. * djangorestframework, tests fail, not yet investigated in