From: AnInternetTroll <AnInternetTroll@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: iamb-0.0.9
Date: Sun, 07 Apr 2024 22:18:29 +0200 [thread overview]
Message-ID: <20240407201829.CD1B42138E@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49652@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 715 bytes --]
New comment by AnInternetTroll on void-packages repository
https://github.com/void-linux/void-packages/pull/49652#issuecomment-2041597505
Comment:
> I guess we should report the test failure om i686 upstream?
I've let them know on matrix that the one test is failing on 32bit (I assume it would fail on armv* as well if the CI would run those tests)
--
About my earlier comment on the manpage, what I meant to say is that maybe the manpage should be vsed'd to change that one line. Something like this for example
```sh
vsed -i docs/iamb.5 -e 's#/usr/share/iamb/config.example.toml#/usr/share/examples/iamb/config.example.toml#'
```
You should still vsconf the file though, that part was correct
next prev parent reply other threads:[~2024-04-07 20:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 14:59 [PR PATCH] " Bnyro
2024-04-07 15:17 ` AnInternetTroll
2024-04-07 15:22 ` [PR REVIEW] " AnInternetTroll
2024-04-07 15:25 ` AnInternetTroll
2024-04-07 15:54 ` Bnyro
2024-04-07 15:57 ` Bnyro
2024-04-07 16:07 ` [PR PATCH] [Updated] " Bnyro
2024-04-07 16:08 ` [PR REVIEW] " Bnyro
2024-04-07 17:31 ` AnInternetTroll
2024-04-07 17:33 ` AnInternetTroll
2024-04-07 17:34 ` AnInternetTroll
2024-04-07 18:03 ` Bnyro
2024-04-07 18:05 ` [PR REVIEW] " Bnyro
2024-04-07 19:24 ` [PR PATCH] [Updated] " Bnyro
2024-04-07 20:18 ` AnInternetTroll [this message]
2024-04-08 8:47 ` Bnyro
2024-06-01 21:52 ` Bnyro
2024-06-01 21:52 ` Bnyro
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=20240407201829.CD1B42138E@inbox.vuxu.org \
--to=aninternettroll@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).