From: Goorzhel <Goorzhel@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: flyctl-0.0.351
Date: Thu, 21 Jul 2022 08:30:59 +0200 [thread overview]
Message-ID: <20220721063059.zX-XqoCSMp9t2Hfuc-xmeZNYKL8S1G0xRv91FlOSw70@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37950@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 609 bytes --]
New comment by Goorzhel on void-packages repository
https://github.com/void-linux/void-packages/pull/37950#issuecomment-1191093966
Comment:
Another oversight:
```
❯ flyctl version
Update available 0.0.351 -> v0.0.356.
Run "flyctl version update" to upgrade.
flyctl v0.0.351 linux/amd64 Commit: df8c42a BuildDate: 2022-07-10T01:45:12Z
```
That command curls a script to `sh`, the script's job being to install flyctl to `~/.fly/bin/flyctl`.
The warning can be suppressed with `export FLY_NO_UPDATE_CHECK=1`, but I wouldn't know where to set that on package installation (if it's feasible).
next prev parent reply other threads:[~2022-07-21 6:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 18:52 [PR PATCH] " Goorzhel
2022-07-09 18:53 ` classabbyamp
2022-07-09 18:57 ` [PR REVIEW] " classabbyamp
2022-07-09 19:21 ` [PR PATCH] [Updated] " Goorzhel
2022-07-09 19:51 ` Goorzhel
2022-07-09 20:01 ` Goorzhel
2022-07-09 20:02 ` Goorzhel
2022-07-09 20:02 ` Goorzhel
2022-07-09 20:08 ` Goorzhel
2022-07-10 0:24 ` [PR REVIEW] " CameronNemo
2022-07-10 0:41 ` classabbyamp
2022-07-10 1:46 ` [PR PATCH] [Updated] " Goorzhel
2022-07-10 1:46 ` Goorzhel
2022-07-10 1:57 ` classabbyamp
2022-07-12 7:12 ` [PR PATCH] [Updated] " Goorzhel
2022-07-12 7:12 ` Goorzhel
2022-07-12 7:13 ` Goorzhel
2022-07-21 6:30 ` Goorzhel [this message]
2022-07-21 13:32 ` classabbyamp
2022-07-24 19:39 ` [PR PATCH] [Updated] " Goorzhel
2022-07-24 19:39 ` Goorzhel
2022-07-24 19:40 ` Goorzhel
2022-07-24 19:40 ` [PR PATCH] [Updated] " Goorzhel
2022-08-06 21:01 ` Goorzhel
2022-08-06 21:01 ` [PR PATCH] [Closed]: " Goorzhel
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=20220721063059.zX-XqoCSMp9t2Hfuc-xmeZNYKL8S1G0xRv91FlOSw70@z \
--to=goorzhel@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).