Commit 8d835d78 authored by Neil Williams's avatar Neil Williams 💬

Python3 changes needed for lava-server

This moves lava-server to Python3 only. Packaging changes
are available in the python3 packaging branch.
Some helpers still need updates for Python3.
Update ./ci-run to not run Python2 unit tests.
Update validate_pipeline_devices XMLRPC API call to return
a valid xmlrpc Binary object using Python3.
Use Django from Stretch - stretch-backports is also
supported.
Update docs for removal of Python2 support and
therfore Jessie.

Change-Id: I60c4d5092aef4555cf01b193bda917f473906dd7
parent 33c5f72f
......@@ -4,7 +4,7 @@ set -x
set -e
PEP8=1
ALL=0
ALL=1
while getopts ":pa" opt; do
case $opt in
......@@ -13,13 +13,13 @@ while getopts ":pa" opt; do
PEP8=2
;;
a)
# python3 and python2
# python3 - python2 support dropped
ALL=1
;;
\?)
echo "Usage:"
echo "-p - pep8 only"
echo "-a - run all tests: pep8, python2 and python3"
echo "-a - run all tests: pep8 and python3"
echo "Invalid option: -$OPTARG" >&2
exit 1
;;
......@@ -51,15 +51,6 @@ if [[ (-z "$1") || (("$1" == -v*) && ($# -eq 1)) ]]; then
VERBOSE=$1
fi
if [ -n "$NOINPUT" ] || [ -n "$VERBOSE" ]; then
./lava_server/manage.py test $NOINPUT $VERBOSE \
lava_scheduler_app \
linaro_django_xmlrpc.tests \
lava_results_app
else
./lava_server/manage.py test "$@"
fi
if [ ${ALL} = 1 ]; then
if [ -n "$NOINPUT" ] || [ -n "$VERBOSE" ]; then
python3 ./lava_server/manage.py test $NOINPUT $VERBOSE \
......
......@@ -541,7 +541,7 @@ context may be ignored.
The version of ``qemu`` installed on the dispatcher is a choice made by the
admin. Generally, this will be the same as the version of ``qemu`` available
from Debian in the same suite as the rest of the packages installed on the
dispatcher, e.g. ``jessie``. Information on the available versions of ``qemu``
dispatcher, e.g. ``stretch``. Information on the available versions of ``qemu``
in Debian is available at http://tracker.debian.org/qemu
.. seealso:: :ref:`essential_components` and :ref:`qemu-iso boot method
......@@ -580,7 +580,7 @@ option in the job context may be ignored.
The version of ``qemu`` installed on the dispatcher is a choice made by the
admin. Generally, this will be the same as the version of ``qemu`` available
from Debian in the same suite as the rest of the packages installed on the
dispatcher, e.g. ``jessie``. Information on the available versions of ``qemu``
dispatcher, e.g. ``stretch``. Information on the available versions of ``qemu``
in Debian is available at http://tracker.debian.org/qemu
QEMU can be used with an NFS using the ``qemu-nfs`` method and the ``nfs``
......@@ -628,7 +628,7 @@ modification using the :term:`job context`.
The version of ``qemu`` installed on the dispatcher is a choice made by the
admin. Generally, this will be the same as the version of ``qemu`` available
from Debian in the same suite as the rest of the packages installed on the
dispatcher, e.g. ``jessie``. Information on the available versions of ``qemu``
dispatcher, e.g. ``stretch``. Information on the available versions of ``qemu``
in Debian is available at http://tracker.debian.org/qemu
.. seealso:: :ref:`essential_components` and :ref:`boot method qemu
......
......@@ -344,7 +344,7 @@ colon. In the YAML, all values containing a colon **must** be quoted:
.. code-block:: yaml
persistent_nfs:
address: "127.0.0.1:/var/lib/lava/dispatcher/tmp/armhf/jessie"
address: "127.0.0.1:/var/lib/lava/dispatcher/tmp/armhf/stretch"
.. index:: deploy to tmpfs
......@@ -357,7 +357,7 @@ Used to support QEMU device types which run on a dispatcher. The file is
downloaded to a temporary directory and made available as one or more images,
appending specified arguments to a predetermined QEMU command line:
.. include:: examples/test-jobs/qemu-amd64-standard-jessie.yaml
.. include:: examples/test-jobs/qemu-amd64-standard-stretch.yaml
:code: yaml
:start-after: actions:
:end-before: # BOOT_BLOCK
......@@ -389,7 +389,7 @@ QEMU would include ``-drive format=raw,file=/tmp/tmp.rG542e/large-stable-6.img``
.. note:: Take note of the syntax. Single brace before and after the label and
**no whitespace**. This is test job syntax, not Jinja.
.. include:: examples/test-jobs/qemu-amd64-standard-jessie.yaml
.. include:: examples/test-jobs/qemu-amd64-standard-stretch.yaml
:code: yaml
:start-after: to: tmpfs
:end-before: url:
......@@ -475,7 +475,7 @@ potential problems such as misconfigured caching or corrupted downloads. If
compression is used, the checksum to specify is the checksum of the compressed
file, irrespective of whether that file is decompressed later.:
.. include:: examples/test-jobs/qemu-amd64-standard-jessie.yaml
.. include:: examples/test-jobs/qemu-amd64-standard-stretch.yaml
:code: yaml
:start-after: rootfs:
:end-before: os: debian
......
......@@ -86,7 +86,7 @@ First steps using LAVA
explain_first_job
lava-tool
standard-test-jobs
standard-qemu-jessie
standard-qemu-stretch
standard-qemu-kernel
standard-armmp-ramdisk-bbb
......
......@@ -14,8 +14,9 @@ Packages for LAVA are available for:
* Debian Sid (unstable)
Packages will remain available for Debian Jessie (oldstable) with backports
until June 2018 as security support for Jessie will end. Developers are
recommended to use Debian Stretch or Buster for development.
until June 2018 as security support for Jessie will end. The last production
release with Jessie support was 2018.2. Developers need to use Debian Stretch
or Buster for development.
When using the packages to develop LAVA, there is a change to the workflow
compared to the old lava-deployment-tool buildouts.
......@@ -65,13 +66,10 @@ Developer package build
.. seealso:: :ref:`developer_preparations` and
:ref:`development_pre_requisites`
.. note:: The recommended suite for LAVA development is now Stretch. The
developer package build now defaults to expecting Stretch and therefore
enables Python2 and Python3 support. If you are building on Jessie, use the
``-b backports`` branch option to only build for Python2. When support for
Python2 is removed, the ``master`` branch will change to only building
Python3 and building on Jessie will be disabled. To install lava-server,
lava-dispatcher must also be built and installed with Python3 support. See
.. note:: The supported suite for LAVA development is now Stretch. The
developer package build now defaults to expecting Stretch and therefore uses
Python3 exclusively. Support for building Python2 has been removed, the
``master`` branch only builds Python3. See
https://lists.linaro.org/pipermail/lava-announce/2018-January/000046.html
The ``lava-dev`` package includes a helper script which is also present in the
......@@ -86,12 +84,6 @@ from the directory containing the code for that package::
$ /usr/share/lava-server/debian-dev-build.sh -p lava-server
If you are building a package to be installed on Jessie, ensure that the
``backports`` packaging branch is used so that the packaging scripts can allow
for differences between unstable and jessie::
$ /usr/share/lava-server/debian-dev-build.sh -p lava-server -b backports
The packages will be built in a temporary directory using a version string
based on the current git tag and the time of the build. The helper outputs the
location of all the built packages at the end of a successful build, ready for
......@@ -104,9 +96,7 @@ use with ``$ sudo dpkg -i``.
To install any package, including the developer build packages, the
corresponding package **must** already be installed at the current production
release version (or better), on the same machine. This ensures that all of the
runtime dependencies already exist on the system. (If you are building for
installation on Jessie, you will need a fully installed Jessie VM to test the
packages built for Jessie.)
runtime dependencies already exist on the system.
.. _devel_branches:
......@@ -165,17 +155,6 @@ the short hash can be used to lookup the commit in the master branch, e.g.::
Distribution differences
========================
LAVA uses a date-based release scheme and PEP440_ imposes constraints on how
local versions can be named and still work reliably with python-setuptools_,
yet these constraints differ between jessie and unstable::
jessie: lava-server-2015.12-5451.f9304da
unstable: lava-server-2015.12+5451.f9304da
There are also changes internally in the *egg* information used by setuptools
when built on jessie and when built on unstable. Binary packages built on
unstable will fail to install on jessie.
**Always** build packages on the suite you expect to use for installation.
Packages available from the :ref:`lava_repositories` are built on
......@@ -235,40 +214,15 @@ number, in accordance with PEP440, so the git tag will be ``2015.8`` instead of
Development using Python3
*************************
LAVA has been moving towards Python3 support as an integral part of the
migration to V2 and with the completion of the migration and the removal of the
V1 codebase, `the announcement has been made
<https://lists.linaro.org/pipermail/lava-announce/2017-June/000032.html>`_ that
all LAVA packages will move exclusively to Python3 support.
Both lava-server and lava-dispatcher optionally support running the unit tests
with Python3 using the ``-a`` option to ``./ci-run``.
In due course, the internal CI within LAVA (called ``lavabot``) will support
running the Python3 unit tests for lava-server as well as lava-dispatcher. At
this point, **all** reviews **must** pass the unit tests when run with Python3.
LAVA has moved to exclusive Python3 support as the final stage of the
migration to V2. See
<https://lists.linaro.org/pipermail/lava-announce/2017-June/000032.html>`_
Once builds for Debian Jessie cease, support for Python2 will be dropped and
**only** Python3 will be supported.
Both lava-server and lava-dispatcher only support running the unit tests with
Python3. **All** reviews **must** pass the unit tests when run with Python3.
The 2018.2 release of LAVA will enable both Python2 and Python3, so that
installations will bring in both sets of dependencies to allow both sets of
unit tests to be run. At runtime, LAVA will still use Python2 for the 2018.1
release but will switch over when support for Jessie ceases.
In the meantime, the :ref:`dev_builds` can support Python3 by using the ``-b``
option to specify the ``python3`` branch::
$ /usr/share/lava-server/debian-dev-build.sh -p lava-server -b python3
$ /usr/share/lava-server/debian-dev-build.sh -p lava-dispatcher -b python3
.. note:: The first time you install a package built using the ``python3``
branch, you are likely to see dependency failures which block the install.
Check the information about the newly built packages and ensure that the
relevant dependencies are installed. In particular,
``python3-django-auth-ldap`` will need to be installed from
``stretch-backports``.
Builds for Debian Jessie have ceased, support for Python2 has been dropped and
**only** Python3 is be supported.
Python3 dependencies include:
......@@ -538,10 +492,6 @@ branch and passing the ``-b`` option to :file:`debian-dev-build-sh`::
$ /usr/share/lava-server/debian-dev-build.sh -p lava-server -b docs
or for installation on jessie::
$ /usr/share/lava-server/debian-dev-build.sh -p lava-server -b backports
.. _architecture_builds:
Building for other architectures
......
# Standard Jessie amd64 JOB definition for QEMU
# Standard Stretch amd64 JOB definition for QEMU
device_type: qemu
job_name: qemu amd64 standard build, Debian Jessie
job_name: qemu amd64 standard build, Debian Stretch
timeouts:
job:
......@@ -14,10 +14,10 @@ visibility: public
metadata:
source: https://git.linaro.org/lava-team/refactoring.git
path: doc/v2/examples/test-jobs/qemu-amd64-standard-jessie.yaml
build-readme: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/jessie/amd64/7/debian-jessie-amd64-readme.html
build-console: https://ci.linaro.org/view/lava-ci/job/lava-debian-stable-amd64-vm/7/console
build-log: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/jessie/amd64/7/vmdebootstrap.log
path: doc/v2/examples/test-jobs/qemu-amd64-standard-stretch.yaml
build-readme: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/stretch/amd64/2/debian-stretch-amd64-readme.html
build-console: https://ci.linaro.org/view/lava-ci/job/lava-debian-stretch-amd64-vm/console
build-log: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/stretch/amd64/2/vmdebootstrap.log
# CONTEXT_BLOCK
context:
......@@ -34,8 +34,8 @@ actions:
images:
rootfs:
image_arg: -drive format=raw,file={rootfs}
url: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/jessie/amd64/7/large-stable.img.gz
sha256sum: 4ab50cc69fc61faa9bf48edada8bc1a317247f77ced5a815f40e75cef1d62cc7
url: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/standard/debian/stretch/amd64/2/stretch.img.gz
sha256sum: b5cdb3b9e65fec2d3654a05dcdf507281f408b624535b33375170d1e852b982c
compression: gz
os: debian
root_partition: 1
......
......@@ -29,10 +29,12 @@ Software Requirements
directly from a git directory**. See :ref:`debian_installation` for
detailed instructions.
We currently recommend installing LAVA on `Debian`_ jessie, stretch or
We currently recommend installing LAVA on `Debian`_ stretch, buster or
unstable. Installations using stretch (the current Debian stable
release) or jessie (the previous stable release) should use updates
available in ``backports``.
release) should use updates available in ``backports``.
LAVA software has now moved to Python3 support. This also means that Jessie
is no longer supported.
Contributions to support other distributions are welcome as long as there is a
commitment to maintain LAVA on those distributions.
......
......@@ -20,7 +20,7 @@ These instructions cover installation on Debian. The supported versions are:
+---------------+------------------------+--------+----------------------+
| Debian | Stretch (stable) | 9.0 | Yes [#f2]_ |
+---------------+------------------------+--------+----------------------+
| Debian | Jessie (oldstable) | 8.0 | Deprecated [#f3]_ |
| Debian | Jessie (oldstable) | 8.0 | **No** [#f3]_ |
+---------------+------------------------+--------+----------------------+
Debian uses codenames for releases (buster, stretch, jessie, wheezy,
......@@ -57,18 +57,15 @@ that codename in the table.
:ref:`lava_repositories`.
.. [#f3] Jessie was released on April 25th, 2015 and security support for
Jessie is expected to terminate in June 2018. All instances using
Jessie are recommended to upgrade to Debian Stretch as soon as
possible. Remaining updates to LAVA packages for Jessie will be made
using `jessie-backports`_.
Jessie is expected to terminate in June 2018. LAVA software has
removed support for building and installing in Jessie as part of the
move to Python3.
.. [#f4] `buster` is the name of the next Debian release after Stretch, which
is supported automatically via uploads to Sid (unstable).
.. _experimental: https://wiki.debian.org/DebianExperimental
.. _jessie-backports: http://backports.debian.org/
.. _stretch-backports: http://backports.debian.org/
You can track the versions of LAVA packages in the various Debian suites by
......@@ -91,9 +88,8 @@ repository.
.. _production-repo: https://images.validation.linaro.org/production-repo/
In times when the current production release has not made it into either
``stretch-backports`` or ``jessie-backports`` (e.g. due to a migration issue
or a pre-release package freeze in Debian), this repository can be used
instead.
``stretch-backports`` (e.g. due to a migration issue or a pre-release package
freeze in Debian), this repository can be used instead.
The :file:`services-trace.txt` file in the repository shows the latest update
timestamp and is accompanied by a GnuPG signature of the trace file, signed
......@@ -104,14 +100,8 @@ repository, using the same suites::
deb https://images.validation.linaro.org/staging-repo stretch-backports main
deb https://images.validation.linaro.org/staging-repo jessie-backports main
This repository uses the same key as the production repository.
There are differences in how the packages are built between
``jessie-backports`` and ``stretch-backports`` but the contents are otherwise
the same for the same upstream version.
Stretch users
-------------
......@@ -124,14 +114,8 @@ Stretch users
Jessie users
-------------
.. caution:: Deprecated - please upgrade Jessie systems to Stretch.
::
deb https://images.validation.linaro.org/production-repo jessie-backports main
.. note:: The packages formerly in the ``sid`` suite in the repository are
not being updated after 2017.6.
.. caution:: Unsupported - please upgrade Jessie systems to Stretch. No new
releases or developer builds are available for Jessie.
.. _archive_repository:
......@@ -156,7 +140,7 @@ usable backup of the postgresql database exists from the period
For the sake of users needing this archive functionality, packages of
the 2017.10 LAVA release will also remain available in a dedicated
LAVA repository. The archive machine will need to be configured
**not** to use the default apt sources for either stretch or jessie
**not** to use the default apt sources for stretch or jessie
above. The archive **must instead use** the archive repository, for
stretch or jessie respectively::
......@@ -368,60 +352,16 @@ require updates from backports.
Installing on Debian Jessie
===========================
.. caution:: Deprecated - new LAVA instances should no longer use Debian
Jessie.
.. caution:: Unsupported - Instances using Jessie must upgrade to Stretch
Debian Jessie was released on April 25th, 2015, containing a full set of
packages to install LAVA at version 2014.9. Debian stable releases of LAVA do
not receive updates to LAVA directly, so a simple install on Jessie will only
get you ``2014.9``. All admins of LAVA instances are **strongly** advised to
update all software on the instance on a regular basis to receive security
updates to the base system.
For packages which need larger changes, the official Debian method is to
provide those updates using ``backports``. Backports **do not install
automatically** even after the apt source is added - this is because backports
are rebuilt from the current ``testing`` suite, so automatic upgrades would
move the base system to testing as well. Instead, the admin selects which
backported packages to add to the base stable system. Only those packages (and
dependencies, if not available in stable already) will then be installed from
backports.
The ``lava-server`` backports and dependencies are **fully supported** by the
LAVA software team and admins of **all** LAVA instances need to update the base
``2014.9`` to the version available in current backports. Subscribe to the
:ref:`lava_announce` mailing list for details of when new releases are made.
Backports will be available about a week after the initial release.
Updates for LAVA on Debian Jessie are uploaded to `jessie-backports
<http://backports.debian.org/>`_
upgrade the instance to Stretch to receive security updates to the base system
and to be able to install LAVA.
Create an apt source for backports, either by editing ``/etc/apt/sources.list``
or adding a file with a ``.list`` suffix into ``/etc/apt/sources.list.d/``.
Create a line like the one below (using your preferred Debian mirror)::
deb http://deb.debian.org/debian jessie-backports main
Remember to update your apt cache whenever add a new apt source::
$ sudo apt update
Then install ``lava-server`` from ``jessie-backports`` using the ``-t`` option::
$ sudo apt -t jessie-backports install lava-server
$ sudo a2dissite 000-default
$ sudo a2enmod proxy
$ sudo a2enmod proxy_http
$ sudo a2ensite lava-server.conf
$ sudo service apache2 restart
Once backports are enabled, the packages which the admin has selected from
backports (using the ``-t`` switch) will continue to upgrade using backports.
Other packages will only be added from backports if the existing backports
require updates from backports. For example, when ``lava-server 2016.8`` moved
to requiring Django1.8, new installations and updates to ``2016.8`` using
backports automatically bring in Django1.8 and associated support, also from
backports.
.. seealso:: :ref:`install_debian_stretch`
Installing just lava-server
===========================
......@@ -513,16 +453,8 @@ support for some time and will be dropping Python2 support in the next LTS.
(The current non-LTS release of django, version 2.0, has already dropped
support for Python2.)
LAVA has been moving towards Python3 support as an integral part of the
migration to V2 and with the completion of the migration and the removal of the
V1 codebase, `the announcement has been made
<https://lists.linaro.org/pipermail/lava-announce/2017-June/000032.html>`_ that
all LAVA packages will move exclusively to Python3 support.
Supporting LAVA with Python3 on Debian Jessie is awkward and as Jessie is now
deprecated and will have security support dropped in 2018, the decision has
been taken to **not** support Python3 in Jessie for LAVA packages. The move to
Python3 will therefore happen with the move to Stretch.
LAVA has moved to exclusive Python3 support as the completion of the
migration to V2.
Setting up a reverse proxy
==========================
......
.. index:: standard jessie qemu
.. index:: standard stretch qemu
.. _standard_amd64_jessie_qemu:
.. _standard_amd64_stretch_qemu:
Standard test job for QEMU - Jessie amd64
#########################################
Standard test job for QEMU - Stretch amd64
##########################################
The first standard job to look at is a small step on from the first example
job:
.. include:: examples/test-jobs/qemu-amd64-standard-jessie.yaml
.. include:: examples/test-jobs/qemu-amd64-standard-stretch.yaml
:code: yaml
:end-before: metadata:
`Download / view full job definition <examples/test-jobs/qemu-amd64-standard-jessie.yaml>`_
`Download / view full job definition <examples/test-jobs/qemu-amd64-standard-stretch.yaml>`_
Context
=======
......@@ -23,7 +23,7 @@ test job submission to dictate how the test job is executed. The first example
test job included the use of ``context`` and the standard test job for QEMU
extends this:
.. include:: examples/test-jobs/qemu-amd64-standard-jessie.yaml
.. include:: examples/test-jobs/qemu-amd64-standard-stretch.yaml
:code: yaml
:start-after: CONTEXT_BLOCK
:end-before: # ACTIONS_BLOCK
......@@ -55,7 +55,7 @@ This is also familiar from the first job. The addition here is that the
standard image build exports the SHA256sum of the prepared files to allow the
checksum to be passed to LAVA to verify that the download is the correct file:
.. include:: examples/test-jobs/qemu-amd64-standard-jessie.yaml
.. include:: examples/test-jobs/qemu-amd64-standard-stretch.yaml
:code: yaml
:start-after: ACTIONS_BLOCK
:end-before: # BOOT_BLOCK
......@@ -67,7 +67,7 @@ Here is another small change from the first example job. The standard build
also outputs details of the prompts which will be output by the image upon
boot. This information is then used in the test job submission:
.. include:: examples/test-jobs/qemu-amd64-standard-jessie.yaml
.. include:: examples/test-jobs/qemu-amd64-standard-stretch.yaml
:code: yaml
:start-after: BOOT_BLOCK
:end-before: # TEST_BLOCK
......@@ -75,10 +75,10 @@ boot. This information is then used in the test job submission:
Test
====
The standard QEMU test job for jessie adds an :term:`inline` test definition as
The standard QEMU test job for stretch adds an :term:`inline` test definition as
the only change from the example first job:
.. include:: examples/test-jobs/qemu-amd64-standard-jessie.yaml
.. include:: examples/test-jobs/qemu-amd64-standard-stretch.yaml
:code: yaml
:start-after: TEST_BLOCK
......
......@@ -57,7 +57,7 @@ Ensure that you change the **metadata** to point at your local repository so
that you can easily distinguish between the results with and without your
modifications:
.. include:: examples/test-jobs/qemu-amd64-standard-jessie.yaml
.. include:: examples/test-jobs/qemu-amd64-standard-stretch.yaml
:code: yaml
:start-after: visibility: public
:end-before: # CONTEXT_BLOCK
......
......@@ -7,7 +7,7 @@ Type=simple
Environment=LOGLEVEL=DEBUG WORKERS=4 LOGFILE=/var/log/lava-server/gunicorn.log RELOAD=
EnvironmentFile=-/etc/default/lava-server-gunicorn
EnvironmentFile=-/etc/lava-server/lava-server-gunicorn
ExecStart=/usr/bin/gunicorn lava_server.wsgi --log-level $LOGLEVEL --log-file $LOGFILE -u lavaserver -g lavaserver --workers $WORKERS $RELOAD
ExecStart=/usr/bin/python3 -m gunicorn.app.wsgiapp lava_server.wsgi --log-level $LOGLEVEL --log-file $LOGFILE -u lavaserver -g lavaserver --workers $WORKERS $RELOAD
Restart=always
[Install]
......
......@@ -1271,7 +1271,7 @@ class SchedulerAPI(ExposedAPI):
results[key] = {'Invalid': exc}
continue
results[key] = {'Valid': None}
return xmlrpclib.Binary(yaml.dump(results))
return xmlrpclib.Binary(yaml.dump(results).encode('UTF-8'))
def get_publisher_event_socket(self):
"""
......
......@@ -71,15 +71,15 @@ setup(
""",
url='https://www.linaro.org/initiatives/lava/',
install_requires=[
'django >= 1.8',
'django-restricted-resource >= 2015.09',
'django >= 1.10',
'django-restricted-resource >= 2016.8',
'django-tables2 >= 1.2',
'docutils >= 0.6',
'markdown >= 2.0.3',
'psycopg2',
'pyzmq',
'jinja2',
'django-auth-ldap >= 1.1.8',
'django-auth-ldap >= 1.2.12',
'voluptuous >= 0.8.8',
# scheduler
"lava-dispatcher",
......@@ -104,7 +104,7 @@ setup(
'share/render-template.py']),
].extend(DEVICE_TYPE_TEMPLATES),
tests_require=[
'django-testscenarios >= 0.7.2',
'django-testscenarios >= 0.9.1',
],
zip_safe=False,
include_package_data=True)
......@@ -43,14 +43,14 @@ if [ -z "$NAME" ]; then
exit 1
fi
if [ -x ./version.py ]; then
VERSION=`python ./version.py`
VERSION=`python3 ./version.py`
else
VERSION=`python setup.py --version`
VERSION=`python3 setup.py --version`
fi
if [ -d './dist/' ]; then
rm -f ./dist/*
fi
python setup.py sdist
python3 setup.py sdist
if [ -d .git ]; then
LOG=`git log -n1 --pretty=format:"Last change %h by %an, %ar. %s%n" --no-merges`
fi
......
debian:
- python_dir: debian/lava-server/usr/lib/python2.7/dist-packages/
- python_dir: debian/lava-server/usr/lib/python3/dist-packages/
- package: libjs-jquery
directory: /usr/share/javascript/jquery/
lava_directory: lava_server/static/lava_server/js/
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment