From: sug0 <sug0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: go-ipfs: update to 0.17.0.
Date: Sat, 17 Dec 2022 20:30:10 +0100 [thread overview]
Message-ID: <20221217193010.3EpYTvY-xjDLoVmu_u1jrtlzixyW_KndE5SXVAs2wMA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40919@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 549 bytes --]
New comment by sug0 on void-packages repository
https://github.com/void-linux/void-packages/pull/40919#issuecomment-1356403961
Comment:
`fs-repo-migrations` is segfaulting on `armv7l-musl` actually. there's another annoying issue: the migrations logic in ipfs is hard-coded to reject musl targets: https://github.com/ipfs/kubo/blob/430a65ad5f78dc2aed0f54946b2c5922fa4b1ee1/repo/fsrepo/migrations/migrations.go#L258-L260
technically it's possible to package each individual `fs-repo-migrations` binary, and remove `fs-repo-migrations`'s package
next prev parent reply other threads:[~2022-12-17 19:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 16:39 [PR PATCH] " sgn
2022-12-05 16:40 ` sgn
2022-12-05 17:17 ` CMB
2022-12-06 0:43 ` sgn
2022-12-06 0:58 ` CMB
2022-12-17 16:51 ` sug0
2022-12-17 16:52 ` sug0
2022-12-17 17:07 ` sgn
2022-12-17 19:28 ` sug0
2022-12-17 19:30 ` sug0 [this message]
2022-12-17 22:06 ` sug0
2022-12-17 22:07 ` sug0
2022-12-17 22:27 ` sug0
2022-12-17 22:28 ` sug0
2022-12-18 15:53 ` sug0
2022-12-18 16:33 ` sug0
2022-12-18 16:46 ` sug0
2022-12-18 16:46 ` sug0
2023-03-08 23:12 ` sug0
2023-06-07 2:06 ` github-actions
2023-06-22 1:59 ` [PR PATCH] [Closed]: " github-actions
2023-08-04 7:34 ` eoli3n
2023-08-04 7:35 ` eoli3n
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=20221217193010.3EpYTvY-xjDLoVmu_u1jrtlzixyW_KndE5SXVAs2wMA@z \
--to=sug0@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).