| commit | d75fa3f7c90541db51127ddff97ccf6c3f03734e | [log] [tgz] |
|---|---|---|
| author | Harald Welte <laforge@osmocom.org> | Wed May 31 20:47:55 2023 +0200 |
| committer | Harald Welte <laforge@osmocom.org> | Mon Jun 05 20:58:11 2023 +0200 |
| tree | b56154aeb7fb5dcb4a58faf1e119805d3a41de90 | |
| parent | 219a5f369c82c5ba266e1e828bd0116fca6f714b [diff] [blame] |
Switch from pycryptodome to pycryptodomex So for some weird historical reasons, the same python module is available as pycryptodome (Crypto.* namespace) and pycryptodomex (Cryptodome.* namespace). See the following information on the project homepage: https://www.pycryptodome.org/src/installation To make things extra-weird, Debian choose to package pycryptodomex as python3-pycryptodome (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886291). So in order to support both Debian-packaged and differently-installed packages, let's switch to pycryotodomex on all platforms/installers. Change-Id: I04daed01f51f9702595ef9f9e0d7fcdf1e4adb62
diff --git a/requirements.txt b/requirements.txt index fb94472..b12cb4d 100644 --- a/requirements.txt +++ b/requirements.txt
@@ -9,5 +9,5 @@ pyyaml>=5.1 termcolor colorlog -pycryptodome +pycryptodomex packaging