From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Cc: Anton Mikanovich <amikan@ilbers.de>
Subject: [PATCH v2 1/5] testsuite: Fix prepare guide for Debian 10
Date: Mon, 15 Feb 2021 12:26:31 +0300 [thread overview]
Message-ID: <20210215092635.24511-2-amikan@ilbers.de> (raw)
In-Reply-To: <20210215092635.24511-1-amikan@ilbers.de>
There is a version mismatch between avocado-framework and
avocado-framework-plugin-varianter-yaml-to-mux that require version
lock at 69.3 in Debian 10.
Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
---
testsuite/README.md | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/testsuite/README.md b/testsuite/README.md
index 5e64223..153b827 100644
--- a/testsuite/README.md
+++ b/testsuite/README.md
@@ -8,12 +8,11 @@ Then you need to install varianter yaml-to-mux plugin by following these instruc
https://github.com/avocado-framework/avocado/tree/master/optional_plugins
-## For Debian 9.x
+## For Debian (tested on Debian 10.x)
- $ sudo apt-get install python-pip
- $ pip install --user subprocess32
- $ pip install --user avocado-framework
- $ pip install --user avocado-framework-plugin-varianter-yaml-to-mux
+ $ sudo apt install python-subprocess32 python-pip
+ $ pip install --user avocado-framework==69.3
+ $ pip install --user avocado-framework-plugin-varianter-yaml-to-mux==69.3
# Pre
--
2.25.1
next prev parent reply other threads:[~2021-02-15 9:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 16:41 [PATCH v1 0/6] Update Avocado testsuite Anton Mikanovich
2021-02-12 16:41 ` [PATCH v1 1/6] testsuite: Fix prepare guide for Debian 10 Anton Mikanovich
2021-02-12 16:41 ` [PATCH v1 2/6] start_vm.py: Fix target name handling Anton Mikanovich
2021-02-12 16:41 ` [PATCH v1 3/6] testsuite: Fix format_qemu_cmdline input parameters Anton Mikanovich
2021-02-12 16:41 ` [PATCH v1 4/6] testsuite: Add Python generations for testsuite in gitignore Anton Mikanovich
2021-02-12 16:41 ` [PATCH v1 5/6] testsuite: Fix log file path in vm_boot_test Anton Mikanovich
2021-02-12 16:41 ` [PATCH v1 6/6] ci-build: Add ci_build tests cases to Avocado Anton Mikanovich
2021-02-15 9:26 ` [PATCH v2 0/5] Update Avocado testsuite Anton Mikanovich
2021-02-15 9:26 ` Anton Mikanovich [this message]
2021-02-15 9:26 ` [PATCH v2 2/5] start_vm.py: Fix target name handling Anton Mikanovich
2021-02-15 9:26 ` [PATCH v2 3/5] testsuite: Add Python generations for testsuite in gitignore Anton Mikanovich
2021-02-15 9:26 ` [PATCH v2 4/5] testsuite: Fix log file path in vm_boot_test Anton Mikanovich
2021-02-15 9:26 ` [PATCH v2 5/5] ci-build: Add ci_build tests cases to Avocado Anton Mikanovich
2021-02-15 10:42 ` [PATCH v2 0/5] Update Avocado testsuite Jan Kiszka
2021-02-15 11:41 ` Baurzhan Ismagulov
2021-02-15 13:44 ` Jan Kiszka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210215092635.24511-2-amikan@ilbers.de \
--to=amikan@ilbers.de \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox