From: Hilton Chain via Guix-patches via <guix-patches@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 58829@debbugs.gnu.org
Subject: [bug#58829] [PATCH v3] gnu: mosh: Update to 1.4.0.
Date: Mon, 14 Nov 2022 23:45:14 +0800 [thread overview]
Message-ID: <y76mt8t1qwl.wl-hako@ultrarare.space> (raw)
In-Reply-To: <87zgctpyit.fsf_-_@gnu.org>
* gnu/packages/ssh.scm (mosh): Update to 1.4.0.
---
v2 -> v3: Hash changed, switch back to offical site source.
When I was sending v1, they hadn't put 1.4.0 on their website yet, that's why v2 is about switching
to GitHub source.
From the GitHub release page, the original source was released 19 days ago by github-actions, and
the tarball currently visible was uploaded 5 days later, this file is the same one released on the
offical site.
gnu/packages/ssh.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gnu/packages/ssh.scm b/gnu/packages/ssh.scm
index 6a3779ee55..4f8be760bf 100644
--- a/gnu/packages/ssh.scm
+++ b/gnu/packages/ssh.scm
@@ -461,13 +461,13 @@ (define-public corkscrew
(define-public mosh
(package
(name "mosh")
- (version "1.3.2")
+ (version "1.4.0")
(source (origin
(method url-fetch)
(uri (string-append "https://mosh.org/mosh-" version ".tar.gz"))
(sha256
(base32
- "05hjhlp6lk8yjcy59zywpf0r6s0h0b9zxq0lw66dh9x8vxrhaq6s"))))
+ "1pax8sqlvcc7ammsxd9r53yx4m2hg1827wfz6f4rrwjx9q9lnbl7"))))
(build-system gnu-build-system)
(arguments
'(#:phases
base-commit: f572de77c4fda3347bea16b4c86d630b193291dc
--
2.38.1
next prev parent reply other threads:[~2022-11-14 23:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 5:22 [bug#58829] [PATCH] gnu: mosh: Update to 1.4.0 Hilton Chain via Guix-patches via
2022-10-29 14:02 ` [bug#58829] [PATCH v2] " Hilton Chain via Guix-patches via
2022-11-14 11:26 ` [bug#58829] [PATCH] " Ludovic Courtès
2022-11-14 15:45 ` Hilton Chain via Guix-patches via [this message]
2022-11-17 17:14 ` bug#58829: [PATCH v3] " Ludovic Courtès
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=y76mt8t1qwl.wl-hako@ultrarare.space \
--to=guix-patches@gnu.org \
--cc=58829@debbugs.gnu.org \
--cc=hako@ultrarare.space \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.