Github messages for voidlinux
 help / color / mirror / Atom feed
From: jbenden <jbenden@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] mosh: update to 20220318
Date: Fri, 18 Mar 2022 21:17:55 +0100	[thread overview]
Message-ID: <20220318201755.9I7ypBY6WaNGZEanvc7ZD4hw-zSnmnMFei2EVaBLT0o@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36211@inbox.vuxu.org>

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

There is an updated pull request by jbenden against master on the void-packages repository

https://github.com/jbenden/void-packages mosh-git
https://github.com/void-linux/void-packages/pull/36211

mosh: update to 20220318
#### Testing the changes
- I tested the changes in this PR: **YES**

#### Local build testing
- I built this PR locally for my native architecture, (`x86_64`-`glibc`)

#### Notes
The upstream maintainer has seemingly vanished; therefore, a new release seems unlikely. As a workaround for the time being, switch to the git development branch.


A patch file from https://github.com/void-linux/void-packages/pull/36211.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-mosh-git-36211.patch --]
[-- Type: text/x-diff, Size: 3381 bytes --]

From 2c92091280d8192f99dd233152cdcc5716b0d9d1 Mon Sep 17 00:00:00 2001
From: Joseph Benden <joe@benden.us>
Date: Fri, 18 Mar 2022 11:38:26 -0700
Subject: [PATCH] mosh: update to 1.3.2+20220318

Signed-off-by: Joseph Benden <joe@benden.us>
---
 .../fix-memory-blowup-on-large-paste.patch    | 35 -------------------
 srcpkgs/mosh/template                         | 15 +++++---
 2 files changed, 10 insertions(+), 40 deletions(-)
 delete mode 100644 srcpkgs/mosh/patches/fix-memory-blowup-on-large-paste.patch

diff --git a/srcpkgs/mosh/patches/fix-memory-blowup-on-large-paste.patch b/srcpkgs/mosh/patches/fix-memory-blowup-on-large-paste.patch
deleted file mode 100644
index efe3fd806969..000000000000
--- a/srcpkgs/mosh/patches/fix-memory-blowup-on-large-paste.patch
+++ /dev/null
@@ -1,35 +0,0 @@
-From 91de8901f5da04bc2abba3242164b0a330764d49 Mon Sep 17 00:00:00 2001
-From: John Hood <cgull@glup.org>
-Date: Sat, 6 May 2017 23:28:29 -0400
-Subject: [PATCH] Don't do prediction on large pastes into mosh-client.
-
-Fixes #482, memory use blowup on large pastes.  mosh is still pretty slow
-about copying pastes through, though.
----
- src/frontend/stmclient.cc | 10 +++++++++-
- 1 file changed, 9 insertions(+), 1 deletion(-)
-
-diff --git src/frontend/stmclient.cc src/frontend/stmclient.cc
-index 7eff0af3..450d068a 100644
---- a/src/frontend/stmclient.cc
-+++ b/src/frontend/stmclient.cc
-@@ -318,10 +318,18 @@ bool STMClient::process_user_input( int fd )
-   if ( !network->shutdown_in_progress() ) {
-     overlays.get_prediction_engine().set_local_frame_sent( network->get_sent_state_last() );
- 
-+    /* Don't predict for bulk data. */
-+    bool paste = bytes_read > 100;
-+    if ( paste ) {
-+      overlays.get_prediction_engine().reset();
-+    }
-+
-     for ( int i = 0; i < bytes_read; i++ ) {
-       char the_byte = buf[ i ];
- 
--      overlays.get_prediction_engine().new_user_byte( the_byte, local_framebuffer );
-+      if ( !paste ) {
-+	overlays.get_prediction_engine().new_user_byte( the_byte, local_framebuffer );
-+      }
- 
-       if ( quit_sequence_started ) {
- 	if ( the_byte == '.' ) { /* Quit sequence is Ctrl-^ . */
diff --git a/srcpkgs/mosh/template b/srcpkgs/mosh/template
index 3ff5d593ea64..69b55f9de3ed 100644
--- a/srcpkgs/mosh/template
+++ b/srcpkgs/mosh/template
@@ -1,19 +1,24 @@
 # Template file for 'mosh'
 pkgname=mosh
-version=1.3.2
-revision=24
+version=1.3.2+20220318
+revision=1
+_commit=dbe419d0e069df3fedc212d456449f64d0280c76
+_repo="https://github.com/mobile-shell/mosh"
+wrksrc="mosh-${_commit}"
 build_style=gnu-configure
-hostmakedepends="pkg-config protobuf"
+hostmakedepends="automake pkg-config protobuf"
 makedepends="ncurses-devel protobuf-devel libutempter-devel openssl-devel"
 depends="perl-IO-Tty"
 short_desc="Mobile shell, remote terminal application that allows roaming"
 maintainer="Nathan Owens <ndowens04@gmail.com>"
 license="GPL-3.0-or-later"
 homepage="https://mosh.org/"
-distfiles="https://mosh.org/mosh-${version}.tar.gz"
-checksum=da600573dfa827d88ce114e0fed30210689381bbdcff543c931e4d6a2e851216
+distfiles="${_repo}/archive/${_commit}.tar.gz"
+checksum=49268ce1a81b251dffdd117dbc687d86cb80b18e3028019af5fddfa5c04ac1a9
 
 pre_configure() {
 	# make local.test always succeed. It fails due to missing X server in chroot.
 	printf "%s\n" "#!/bin/sh" ":" > src/tests/local.test
+
+	autoreconf -fi
 }

  parent reply	other threads:[~2022-03-18 20:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-18 19:30 [PR PATCH] " jbenden
2022-03-18 19:40 ` [PR REVIEW] " classabbyamp
2022-03-18 19:47 ` leahneukirchen
2022-03-18 20:17 ` jbenden [this message]
2022-03-18 20:18 ` [PR REVIEW] " jbenden
2022-03-18 20:21 ` jbenden
2022-06-29  2:15 ` github-actions
2022-07-13  2:15 ` [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=20220318201755.9I7ypBY6WaNGZEanvc7ZD4hw-zSnmnMFei2EVaBLT0o@z \
    --to=jbenden@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).