Github messages for voidlinux
 help / color / mirror / Atom feed
From: gc-user <gc-user@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] ERROR: libelogind-252.9_2: SHA256 hash is not valid: No such file or directory
Date: Sat, 24 Feb 2024 13:53:19 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48913@inbox.vuxu.org> (raw)

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

New issue by gc-user on void-packages repository

https://github.com/void-linux/void-packages/issues/48913

Description:
### Is this a new report?

Yes

### System Info

Void 6.6.17_1 x86_64 GenuineIntel uptodate hold rrmDDDDFFFFFFFF

### Package(s) Affected

libelogind-252.9_2

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

_No response_

### Expected behaviour

Building libfreerdp-server-2.10.0_3 locally using xbps-src should run through without issues.

### Actual behaviour

When trying to build libfreerdp-server-2.10.0-3 xbps-src fails and gives out the following error message:

ERROR: libelogind-252.9_2: SHA256 hash is not valid: No such file or directory

### Steps to reproduce

1. Try building locally freerdp (it doesn't matter if 2.10.0_3 or 2.11.4_1 nor if it's freerdp or libfreerdp-server)
2. See xbps-src failing with the above error message.

             reply	other threads:[~2024-02-24 12:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-24 12:53 gc-user [this message]
2024-02-24 13:07 ` chrysos349
2024-02-24 13:29 ` gc-user
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48913@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).