From: notramo <notramo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] New package: osmin-1.8.7
Date: Sun, 08 Jan 2023 00:04:57 +0100 [thread overview]
Message-ID: <20230107230457.7zk_ks77gmJ3F10T8bE6hbV3rs-05YIEawR7I1-r8Q0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37298@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 313 bytes --]
New comment by notramo on void-packages repository
https://github.com/void-linux/void-packages/pull/37298#issuecomment-1374646263
Comment:
@Eloitor, the file exists on x64. But the error message is not clear, what is wrong with the reference? Is it not permitted to reference this file, or is the file missing?
next prev parent reply other threads:[~2023-01-07 23:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 6:40 [PR PATCH] " Eloitor
2022-05-26 6:45 ` [PR PATCH] [Updated] " Eloitor
2022-05-26 6:48 ` Eloitor
2022-05-26 7:12 ` Eloitor
2022-05-26 7:13 ` Eloitor
2022-05-26 7:15 ` Eloitor
2022-05-26 7:34 ` Eloitor
2022-05-26 9:18 ` [PR REVIEW] " wael444
2022-05-26 9:18 ` wael444
2022-05-26 9:18 ` wael444
2022-05-26 9:19 ` wael444
2022-05-26 9:32 ` [PR PATCH] [Updated] " Eloitor
2022-05-26 14:50 ` [PR REVIEW] " classabbyamp
2022-05-26 14:50 ` classabbyamp
2022-05-26 14:50 ` classabbyamp
2022-05-26 14:50 ` classabbyamp
2022-05-26 14:50 ` classabbyamp
2022-05-26 18:25 ` Eloitor
2022-05-26 18:30 ` [PR PATCH] [Updated] " Eloitor
2022-05-27 2:57 ` [PR REVIEW] " classabbyamp
2022-06-02 16:34 ` [PR PATCH] [Updated] " Eloitor
2022-07-27 9:22 ` Eloitor
2022-07-27 9:26 ` Eloitor
2022-07-27 9:43 ` Eloitor
2022-07-28 13:29 ` [PR PATCH] [Updated] " Eloitor
2022-09-09 9:41 ` Eloitor
2022-12-09 2:32 ` github-actions
2022-12-24 1:52 ` [PR PATCH] [Closed]: " github-actions
2023-01-07 23:04 ` notramo [this message]
2023-01-07 23:12 ` Eloitor
2023-01-07 23:29 ` notramo
2023-01-10 5:17 ` 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=20230107230457.7zk_ks77gmJ3F10T8bE6hbV3rs-05YIEawR7I1-r8Q0@z \
--to=notramo@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).