Re: updating packages
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 update packages have been converted to gbp pq. Cheers, -- Michael Fladischer Fladi.at signature.asc Description: OpenPGP digital signature
Re: updating packages
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
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-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#security >> >> which makes me reluctant to proceed until the Celery Project confirms >> that they're using a different key pair. > > I checked with upstream on the new signing key[0] and they confirmed it. > > amqp, kombu and celery have been updated and uploaded to experimental. > > [0] https://github.com/celery/kombu/issues/773 > > Cheers, > -- > Michael Fladischer > Fladi.at
Re: updating packages
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#security > > which makes me reluctant to proceed until the Celery Project confirms > that they're using a different key pair. I checked with upstream on the new signing key[0] and they confirmed it. amqp, kombu and celery have been updated and uploaded to experimental. [0] https://github.com/celery/kombu/issues/773 Cheers, -- Michael Fladischer Fladi.at
Re: updating packages
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 python-ampq this > weekend, but the upstream tarballs have been signed by a different key > pair than the one advertised at: :-( Please keep me up-to-date on developments. Thanks! -- Brian May
Re: updating packages
> 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/packages/kombu.git?h=debian%2Fexperimental 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#security which makes me reluctant to proceed until the Celery Project confirms that they're using a different key pair. Christopher
Re: updating packages
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 old or too new? # Build the HTML documentation. mkdir /<>/docs.debian LC_ALL=C.UTF-8 PYTHONPATH=/usr/share/mkdocs/themes mkdocs build && mv site docs.debian/html INFO- Building documentation to directory: /<>/site Traceback (most recent call last): File "/usr/bin/mkdocs", line 9, in load_entry_point('mkdocs==0.15.3', 'console_scripts', 'mkdocs')() File "/usr/lib/python3/dist-packages/click/core.py", line 722, in __call__ return self.main(*args, **kwargs) File "/usr/lib/python3/dist-packages/click/core.py", line 697, in main rv = self.invoke(ctx) File "/usr/lib/python3/dist-packages/click/core.py", line 1066, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) File "/usr/lib/python3/dist-packages/click/core.py", line 895, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/lib/python3/dist-packages/click/core.py", line 535, in invoke return callback(*args, **kwargs) File "/usr/lib/python3/dist-packages/mkdocs/__main__.py", line 137, in build_command ), clean_site_dir=clean) File "/usr/lib/python3/dist-packages/mkdocs/commands/build.py", line 290, in build build_pages(config) File "/usr/lib/python3/dist-packages/mkdocs/commands/build.py", line 234, in build_pages build_template('404.html', env, config, site_navigation) File "/usr/lib/python3/dist-packages/mkdocs/commands/build.py", line 149, in build_template output_content = template.render(context) File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 1008, in render return self.environment.handle_exception(exc_info, True) File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 780, in handle_exception reraise(exc_type, exc_value, tb) File "/usr/lib/python3/dist-packages/jinja2/_compat.py", line 37, in reraise raise value.with_traceback(tb) File "/<>/docs_theme/404.html", line 1, in top-level template code {% extends "main.html" %} File "/<>/docs_theme/main.html", line 7, in top-level template code {% if page.title %}{{ page.title }} - {% endif %}{{ config.site_name }} File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 430, in getattr return getattr(obj, attribute) jinja2.exceptions.UndefinedError: 'page' is undefined debian/rules:12: recipe for target 'override_dh_auto_build' failed make[1]: *** [override_dh_auto_build] Error 1 make[1]: Leaving directory '/<>' debian/rules:9: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 -- Brian May
Re: updating packages
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 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 detail why. > * celery: requires cyanide (including docs) and sphinx_celery to be packaged > in Debian. > > Thanks. > -- > Brian May > https://linuxpenguins.xyz/brian/ >
Re: updating packages
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
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 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. Cheers, Michael
updating packages
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 detail why. * celery: requires cyanide (including docs) and sphinx_celery to be packaged in Debian. Thanks. -- Brian May https://linuxpenguins.xyz/brian/