From: Goorzhel <Goorzhel@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: salt: upgrade to 3001.1; convert depends to py3
Date: Sun, 09 Aug 2020 03:29:40 +0200 [thread overview]
Message-ID: <20200809012940.pRc7Yv2qhjUjlCiFFdN5_6nxMvWGGdGxw0_gfmtTpes@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24136@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 767 bytes --]
New comment by Goorzhel on void-packages repository
https://github.com/void-linux/void-packages/pull/24136#issuecomment-670962101
Comment:
Hmm:
```
ag@server $ sudo salt-key -L
Password:
Error: The 'pycryptodomex>=3.9.7' distribution was not found and is required by salt
ag@server $ xbps-query -f salt | grep requires | tee $(tty) | xargs cat
/usr/lib/python3.8/site-packages/salt-3001.1-py3.8.egg-info/requires.txt
Jinja2
msgpack>=0.5,!=0.5.5
PyYAML
MarkupSafe
requests>=1.0.0
distro
pycryptodomex>=3.9.7
pyzmq>=17.0.0
```
We have `pycryptodome` in void-packages, but not `pycryptodomex` (~~I imagine that's deliberate~~ per comments below, I should Be the Change). For the time being I've papered over this with `sudo pip install pycryptodomex`.
next prev parent reply other threads:[~2020-08-09 1:29 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-08 5:41 [PR PATCH] " Goorzhel
2020-08-08 5:49 ` Goorzhel
2020-08-08 5:49 ` Goorzhel
2020-08-08 5:49 ` [PR PATCH] [Updated] " Goorzhel
2020-08-08 18:57 ` Goorzhel
2020-08-09 1:08 ` fosslinux
2020-08-09 1:13 ` ericonr
2020-08-09 1:29 ` Goorzhel [this message]
2020-08-09 2:26 ` [PR PATCH] [Updated] " Goorzhel
2020-08-09 2:43 ` [PR PATCH] [Updated] salt: to 3001.1; python{,3}-pycryptodomex: new package Goorzhel
2020-08-09 2:53 ` Goorzhel
2020-08-09 3:08 ` [PR PATCH] [Updated] " Goorzhel
2020-08-09 4:49 ` fosslinux
2020-08-09 4:53 ` Goorzhel
2020-08-09 4:56 ` fosslinux
2020-08-09 5:06 ` Goorzhel
2020-08-09 5:06 ` [PR PATCH] [Updated] " Goorzhel
2020-08-09 5:13 ` ericonr
2020-08-09 5:17 ` [PR REVIEW] " fosslinux
2020-08-09 5:18 ` Goorzhel
2020-08-09 5:47 ` [PR PATCH] [Updated] " Goorzhel
2020-08-09 5:47 ` Goorzhel
2020-08-09 18:41 ` Goorzhel
2020-08-09 21:43 ` Vaelatern
2020-08-09 21:54 ` Vaelatern
2020-08-09 23:50 ` Goorzhel
2020-08-09 23:56 ` [PR PATCH] [Updated] " Goorzhel
2020-08-10 3:28 ` [PR PATCH] [Closed]: " Vaelatern
2020-08-10 3:29 ` Vaelatern
2020-08-10 3:29 ` Goorzhel
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=20200809012940.pRc7Yv2qhjUjlCiFFdN5_6nxMvWGGdGxw0_gfmtTpes@z \
--to=goorzhel@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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;
as well as URLs for NNTP newsgroup(s).