Control: tag -1 help lava-server does not install with django1.7 - the error blames a problem with django-tables2, although it would seem to be a django1.7 migration issue inside lava-server.
This is the principle problem with django1.7 for me - I need to use lava-server as the principle test of django-restricted-resource, and django-testscenarios. (django-testproject appears unaffected). ./lava_server/manage.py fails with django.core.exceptions.ImproperlyConfigured: Application labels aren't unique, duplicates: django_tables2 I can't find a duplicate within lava-server. A search turns up the docs on AppConfig (which lava-server doesn't yet use) and the example in the docs doesn't seem to fix the issue. The example also doesn't seem backwards compatible, so that would need to be supported in any prospective change. After reinstalling with django1.6, upgrading to django1.7 under a working lava-server install results in a broken lava-server with the same error. (At this stage, I'd need to add a Conflicts: python-django (>= 1.7) until the fix is incorporated upstream.) If someone can help with a fix for this stage, it would be very much appreciated. The following steps will make up the basis of the tests for lava-server with django1.7: * unit-tests: ./ci-run or the autopkgtest support * a complete UI test - this would need quite a bit of data to ensure that the filters and reports work correctly. Tests would need to include adding users, devices, filters and reports and modifying user access to ensure that the restricted resource functionality is working. * functional tests - ensuring that the scheduler works underneath. These involve running test jobs on real devices and checking for successful completion of tests which are known to work. This isn't easy for someone else to verify without a local LAVA lab with real devices (I'm working on something which will make this easier and I have a talk on that subject at DebConf). http://staging.validation.linaro.org/ If the lava-server unit tests complete, upstream can continue with the integration of any changes into a production release. Currently, that would likely be 2014-10 (due for release the first week of November) or 2014-11 (first week of December). Upstream are working on django1.7 support - another member of the team is investigating. I'm currently involved in a major refactoring of the lava-dispatcher package and less on lava-server. Django1.7 support is not a priority for the pending or subsequent upstream release - especially as 1.7 has not yet been released. Therefore, upstream are working on issues of higher priority. Any contributions to this bug report will be fed back upstream (the bug is already linked to an internal feature tracker) but that might not result in a fix for this bug being successfully incorporated into a production release in time for the Jessie freeze. -- Neil Williams ============= http://www.linux.codehelp.co.uk/
signature.asc
Description: PGP signature
