From: Jon Turney <jon.turney@dronecode.org.uk>
To: Yasuhiro KIMURA <yasu@utahime.org>, Michael Wild <themiwi@gmail.com>
Cc: cygwin-apps@cygwin.com
Subject: Re: Tmux crashes on copy
Date: Wed, 31 Jan 2024 13:28:41 +0000 [thread overview]
Message-ID: <3dba4fa0-a0ba-4364-9de3-b5ab16d52429@dronecode.org.uk> (raw)
In-Reply-To: <20240125.204909.51048265819335534.yasu@utahime.org>
On 25/01/2024 11:49, Yasuhiro Kimura via Cygwin-apps wrote:
> From: Marco Atzeri via Cygwin-apps <cygwin-apps-rDBXBDvO6BXQT0dZR+AlfA@public.gmane.org>
> Subject: Re: Tmux crashes on copy
> Date: Thu, 25 Jan 2024 12:11:13 +0100
>
[...]
>
> Thanks for quick reply.
>
> By applying following changes to tmux.cygport of tmux 3.2-1, build of
> tmux succeeds with latest snapshot of upstream repository.
>
> ----------------------------------------------------------------------
> diff --git a/tmux.cygport b/tmux.cygport
> index 8a770f9..bd33422 100644
> --- a/tmux.cygport
> +++ b/tmux.cygport
> @@ -1,5 +1,5 @@
> NAME="tmux"
> -VERSION="3.2"
> +VERSION="3.3a.330"
> RELEASE="1"
> CATEGORY="Utils"
> SUMMARY="Terminal multiplexer"
> @@ -13,11 +13,13 @@ placed in /tmp. Moreover tmux provides a consistent and well-documented command
> interface, with the same syntax whether used interactively, as a key binding,
> or from the shell. It offers a choice of vim or Emacs key layouts."
> HOMEPAGE="http://${PN}.github.io"
> -SRC_URI="https://github.com/${PN}/${PN}/releases/download/${PV}/${P}.tar.gz"
> +GIT_URI="https://github.com/${PN}/${PN}"
> +GIT_REV="ea7136fb"
> +inherit git
> PATCH_URI="patches/0001-fix-control-mode.patch"
>
> DEPEND="autoconf automake pkg-config libtool gettext-devel make git
> -libevent-devel libncurses-devel"
> +libevent-devel libncurses-devel bison"
>
> # tmux includes ncurses as <ncurses.h> and doesn't look for libncursesw
> CYGCONF_ARGS="CPPFLAGS=-I/usr/include/ncursesw LIBS=-lncursesw"
> ----------------------------------------------------------------------
Thanks.
Since this is a crash bug, which renders the package more or less
useless, I made an NMU with these changes.
Michael,
Sorry about not pinging you before I made this change.
You don't seem to have been active for a few years. Are you still
interesting in maintaining this package?
IF so, do you want to get pinged if/when problems crop up?
next prev parent reply other threads:[~2024-01-31 13:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADr_F644gWjSLKTFMLp=7ajFu0VXSwZr=Xq+cjuGYA+wbGdrYw@mail.gmail.com>
[not found] ` <20240118.163759.544696899534989142.yasu@utahime.org>
[not found] ` <20240118172431.8308e15fc705d96fc39410d7@nifty.ne.jp>
[not found] ` <35eb821c-5270-406c-985f-b6107b43be9a@SystematicSW.ab.ca>
2024-01-25 9:04 ` Yasuhiro Kimura
2024-01-25 11:11 ` Marco Atzeri
2024-01-25 11:49 ` Yasuhiro Kimura
2024-01-31 13:28 ` Jon Turney [this message]
2024-02-14 0:11 ` Yasuhiro Kimura
2024-02-15 19:09 ` Jon Turney
2024-02-17 19:53 ` ASSI
[not found] ` <2016e573-7282-4fa3-bee4-e54d36ac0c2d@SystematicSW.ab.ca>
[not found] ` <a910f721-6047-4162-a86b-61d4ec8f93ca@dronecode.org.uk>
[not found] ` <878r45wgjw.fsf@>
2024-01-31 20:45 ` ncurses version (was: Tmux crashes on copy) Brian Inglis
2024-01-31 23:05 ` ncurses version Jon Turney
2024-02-01 3:41 ` Brian Inglis
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=3dba4fa0-a0ba-4364-9de3-b5ab16d52429@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
--cc=themiwi@gmail.com \
--cc=yasu@utahime.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 read-only IMAP folder(s) and NNTP newsgroup(s).