From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Nomad 1.3.1_1 aarch64 corrupted
Date: Thu, 14 Jul 2022 08:52:13 +0200 [thread overview]
Message-ID: <20220714065213.LEE4JUc9jkBCYznacFoVemhioPEqfemkodgd2YNzDIQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38056@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1367 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/issues/38056#issuecomment-1184064708
Comment:
happens for me too
```
doas env XBPS_TARGET_ARCH=aarch64 xbps-install -M --repository=https://repo-default.voidlinux.org/current/aarch64 -r ./test nomad
`https://repo-default.voidlinux.org/current/aarch64' repository has been RSA signed by "Void Linux"
Fingerprint: 60:ae:0c:d6:f0:95:17:80:bc:93:46:7a:89:af:a3:2d
Do you want to import this public key? [Y/n] y
Name Action Version New version Download size
glibc install - 2.32_2 7666KB
nomad install - 1.3.1_1 15MB
Size to download: 23MB
Size required on disk: 83MB
Space available on disk: 16GB
Do you want to continue? [Y/n]
[*] Downloading packages
glibc-2.32_2.aarch64.xbps.sig: 512B [avg rate: 61MB/s]
glibc-2.32_2.aarch64.xbps: 7666KB [avg rate: 21MB/s]
glibc-2.32_2: verifying RSA signature...
nomad-1.3.1_1.aarch64.xbps.sig: 512B [avg rate: 38MB/s]
nomad-1.3.1_1.aarch64.xbps: 15MB [avg rate: 26GB/s]
nomad-1.3.1_1: verifying RSA signature...
ERROR: nomad-1.3.1_1: the RSA signature is not valid!
ERROR: nomad-1.3.1_1: removed pkg archive and its signature.
Transaction failed! see above for errors.
```
next prev parent reply other threads:[~2022-07-14 6:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 6:37 [ISSUE] " adrian-bl
2022-07-14 6:52 ` classabbyamp [this message]
2022-10-14 6:25 ` adrian-bl
2022-10-14 6:25 ` [ISSUE] [CLOSED] " adrian-bl
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=20220714065213.LEE4JUc9jkBCYznacFoVemhioPEqfemkodgd2YNzDIQ@z \
--to=classabbyamp@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).