Re: Failure - tmux on today's -current

ci4ic4 <[email protected]> Thu, 26 Mar 2026 12:59:19 +0000
Newsgroups gmane.os.netbsd.current
Message-ID <4jb9h6qj5nhk1A5T7VjGqORnUZBABts2is9RvGFAOLfIUi8MYeaklDHGFGKA8VHXgsAKnwNQIFSDGP1l3rrNuhsAw6v8CYqsq8vZFTOZLRY=@proton.me>



Sent with Proton Mail secure email.

On Thursday, 26 March 2026 at 9:45 AM, Thomas Klausner <[email protected]> wrote:

> On Thu, Mar 26, 2026 at 09:31:51AM +0100, ci4ic4 wrote:
> > Have I missed something? I could not see anything in UPDATING regarding changes around tmux. It stopped working on my today's amd64 system - I am about to test it on an aarch64 one in a moment. I started a session overnight - running pkg_rolling-replace - and tried to attach to it in the morning and am getting:
> 
> You're leaving out a lot of interesting details...  but one thing that
> could be a problem here: you need to restart tmux on binary updates,
> so if you have installed a newer tmux, you can't attach to a session
> started by an older tmux.

Got it - that was the case. I had rebooted into the new -current and started the tmux session as usual; /usr/pkg/bin was ahead of /usr/bin in the PATH so it had used the pkgsrc one, which got replaced by the pkg_rr process. I didn't want to interrupt the current session to restart, as it was in the middle of a nodejs build, which takes forever and a day... 

Thanks,

Chavdar 

>  Thomas
>