Github messages for voidlinux
 help / color / mirror / Atom feed
From: adrian-bl <>
Subject: [ISSUE] Nomad 1.3.1_1 aarch64 corrupted
Date: Thu, 14 Jul 2022 08:37:49 +0200	[thread overview]
Message-ID: <> (raw)

[-- Attachment #1: Type: text/plain, Size: 1665 bytes --]

New issue by adrian-bl on void-packages repository

### Is this a new report?


### System Info

Void 5.10.92_1 aarch64 Unknown notuptodate rFFFFF

### Package(s) Affected


### Does a report exist for this bug with the project's home (upstream) and/or another distro?


### Expected behaviour

Nomad 1.3.1_1 can not be installed/upgraded on aarch64 since the package seems to be corrupt: xbps complains about an invalid RSA signature.

Note that this does not affect AMD64 or 32-bit ARM builds of void: it just seems like the aarch64 package file somehow got corrupted. (This happens on 2 AARCH64 machines for me)

# xbps-install -Su nomad
[*] Updating repository `' ...

Name  Action    Version           New version            Download size
nomad update    1.3.0_1           1.3.1_1                15MB 

Size to download:               15MB
Size required on disk:          55MB
Space available on disk:        13GB

Do you want to continue? [Y/n] y

[*] Downloading packages
nomad-1.3.1_1.aarch64.xbps.sig: 512B [avg rate: 2907KB/s]
nomad-1.3.1_1.aarch64.xbps: 15MB [avg rate: 1718KB/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.


### Actual behaviour

Installation of Nomad 1.3.1_1 fails due to RSA check failure

### Steps to reproduce

$ xbps-remove -O
$ xbps-install -Su nomad
-> RSA verification failure

             reply	other threads:[~2022-07-14  6:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-14  6:37 adrian-bl [this message]
2022-07-14  6:52 ` classabbyamp
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).