From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] bootstrap failure: /usr/bin/uname
Date: Fri, 08 Dec 2023 02:47:01 +0100 [thread overview]
Message-ID: <20231208014701.8zpppXJ0FbLatY9C3zo6KjR09xwQSOwXzbUNVkQI8iQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45758@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 682 bytes --]
Closed issue by leahneukirchen on void-packages repository
https://github.com/void-linux/void-packages/issues/45758
Description:
<!--
if you are creating a bug report or package request, please fill out one of the forms here:
https://github.com/void-linux/void-packages/issues/new/choose
Don't request an update of a package, We have a script for that:
https://repo-default.voidlinux.org/void-updates/void-updates.txt
However, a quality pull request may help.
-->
The uname wrapper in `common/wrappers/uname.sh` assumes uname is in `usr/bin`.
This is not true for non-UsrMerge Debian, for example.
I think, instead `command -p -v uname` should be used.
prev parent reply other threads:[~2023-12-08 1:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 15:57 [ISSUE] " leahneukirchen
2023-11-24 1:46 ` github-actions
2023-12-08 1:47 ` github-actions [this message]
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=20231208014701.8zpppXJ0FbLatY9C3zo6KjR09xwQSOwXzbUNVkQI8iQ@z \
--to=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).