From: RunningDroid <RunningDroid@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: openbazaar fails to run
Date: Sat, 09 Jul 2022 02:55:54 +0200 [thread overview]
Message-ID: <20220709005554.Eq2Z63jExXnXrngqN_3mtrXW3LWUV80IBI-5GW2CdMs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35126@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 338 bytes --]
New comment by RunningDroid on void-packages repository
https://github.com/void-linux/void-packages/issues/35126#issuecomment-1179263686
Comment:
To make things worse, nodejs FTBFS & is out of date. I'll look into updating nodejs in ~1 week, I'm busy atm.
Edit: I misread what xbps-src was saying; It has failing tests, not a FTBFS.
next prev parent reply other threads:[~2022-07-09 0:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 1:52 [ISSUE] " RunningDroid
2022-06-22 2:14 ` github-actions
2022-07-07 2:14 ` [ISSUE] [CLOSED] " github-actions
2022-07-07 2:30 ` RunningDroid
2022-07-08 18:35 ` RunningDroid
2022-07-09 0:55 ` RunningDroid [this message]
2022-07-09 1:50 ` RunningDroid
2022-07-09 3:27 ` RunningDroid
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=20220709005554.Eq2Z63jExXnXrngqN_3mtrXW3LWUV80IBI-5GW2CdMs@z \
--to=runningdroid@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).