Github messages for voidlinux
 help / color / mirror / Atom feed
From: vfx1b <vfx1b@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] operator-sdk: update to 1.32.0.
Date: Fri, 17 Nov 2023 02:21:41 +0100	[thread overview]
Message-ID: <20231117012141.36JLnZP9f3fhSS6aCmssHvG4oMW86mUBBqNmHkHtu1s@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47275@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 718 bytes --]

New review comment by vfx1b on void-packages repository

https://github.com/void-linux/void-packages/pull/47275#discussion_r1396562597

Comment:
because upstream project only supports these 2 and ppc64le and s390x. when you then setup a project with operator-sdk, its going to go fetch some extra binaries from github that are also just supplied for those 4 archs.

here it fetches `kustomize` if not present on the `$PATH`: https://github.com/operator-framework/operator-sdk/blob/master/testdata/helm/memcached-operator/Makefile#L137

kustomize only supplies those 4 archs, and void-packages has no kustomize in repos, as a  fallback.
https://github.com/kubernetes-sigs/kustomize/releases/tag/kustomize%2Fv4.5.7

  parent reply	other threads:[~2023-11-17  1:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-16 22:18 [PR PATCH] " vfx1b
2023-11-16 22:28 ` [PR PATCH] [Updated] " vfx1b
2023-11-16 23:55 ` [PR REVIEW] " mhmdanas
2023-11-17  1:21 ` vfx1b [this message]
2024-02-15  1:45 ` github-actions
2024-02-15  5:35 ` [PR REVIEW] " classabbyamp
2024-05-16  1:46 ` github-actions
2024-05-30  1:47 ` [PR PATCH] [Closed]: " github-actions

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=20231117012141.36JLnZP9f3fhSS6aCmssHvG4oMW86mUBBqNmHkHtu1s@z \
    --to=vfx1b@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).