From: gc-user <gc-user@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: ERROR: libelogind-252.9_2: SHA256 hash is not valid: No such file or directory
Date: Sat, 24 Feb 2024 14:29:54 +0100 [thread overview]
Message-ID: <20240224132954.4F6FF229C3@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48913@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 500 bytes --]
New comment by gc-user on void-packages repository
https://github.com/void-linux/void-packages/issues/48913#issuecomment-1962364615
Comment:
Found the cause of the issue. /void-packages/hostdir/binpkgs/x86_64-repodata had apparently libelogind-252.9_2.x86_64.xbps listed, but the file was missing, thus the error. Putting the file in that folder and re-indexing the folder fixed the issue.
From the error message and output before it, it seemed as if xbps-src was looking online for the file...
next prev parent reply other threads:[~2024-02-24 13:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-24 12:53 [ISSUE] " gc-user
2024-02-24 13:07 ` chrysos349
2024-02-24 13:29 ` gc-user [this message]
2024-02-24 13:29 ` [ISSUE] [CLOSED] " gc-user
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=20240224132954.4F6FF229C3@inbox.vuxu.org \
--to=gc-user@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).