From 6b3e0ea6bdff15aa24a42f1f5938785460a323a7 Mon Sep 17 00:00:00 2001 From: David Robertson Date: Thu, 14 Apr 2022 11:03:24 +0100 Subject: Use `poetry` to manage the virtualenv in debian packages (#12449) * Use `poetry` to build venv in debian packages Co-authored-by: Dan Callahan Co-authored-by: Shay * Changelog * Only pull in from requirements.txt Addresses the same problem as #12439. * Include `test` and `all` extras `poetry export` helpfully silently ignores an unknown extra Haven't seen this before because it's the only place we export `all` and `test`. I could have __sworm__ that the syntax `--extra "all test"` worked for `poetry install`... * Clean up requirements file on subsequence builds * Fix shell syntax Co-authored-by: Dan Callahan Co-authored-by: Shay --- debian/clean | 1 + 1 file changed, 1 insertion(+) create mode 100644 debian/clean (limited to 'debian/clean') diff --git a/debian/clean b/debian/clean new file mode 100644 index 0000000000..d488f298d5 --- /dev/null +++ b/debian/clean @@ -0,0 +1 @@ +exported_requirements.txt -- cgit 1.5.1