From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: hwids-20200813.1_1: the RSA signature is not valid
Date: Mon, 31 Aug 2020 12:33:24 +0200 [thread overview]
Message-ID: <20200831103324.rE_0-eJMHb26IkZp64Te-auF52XoFBo5mHs7X1x7J2A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24577@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 832 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/issues/24577#issuecomment-683699615
Comment:
This should be resolved for hwids at least, there seems to be some race between aarch64 and aarch64-musl for noarch packages. Both builders have to build the package, but the second to finish sees the there is already the same package and just adds the existing package to its repository index. For some reason in this case, the second (aarch64-musl in this case) overwrote the package that was already indexed for aarch64 so the checksum changed.
The build logs containing both hwids builds:
* https://build.voidlinux.org/builders/aarch64-musl_builder/builds/28519/steps/shell_3/logs/stdio
* https://build.voidlinux.org/builders/aarch64_builder/builds/28132/steps/shell_3/logs/stdio
next prev parent reply other threads:[~2020-08-31 10:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 1:44 [ISSUE] " valadaa48
2020-08-31 2:01 ` flexibeast
2020-08-31 2:08 ` valadaa48
2020-08-31 2:48 ` flexibeast
2020-08-31 6:21 ` fosslinux
2020-08-31 10:33 ` Duncaen [this message]
2020-09-02 20:11 ` Chocimier
2020-09-02 21:23 ` Duncaen
2020-09-29 21:40 ` ericonr
2020-12-18 0:51 ` sgn
2020-12-18 0:51 ` [ISSUE] [CLOSED] " sgn
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=20200831103324.rE_0-eJMHb26IkZp64Te-auF52XoFBo5mHs7X1x7J2A@z \
--to=duncaen@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).