Hello and thanks for this bug report, however what you suggest is not
how updates to stable Ubuntu releases are handled, see [1] for more
information. What we need in the bug report is a statement of the
problem, with possibly a reproducer and ideally with a pointer to the
upstream or Debian fix. Something on these lines:
- On Noble, if you do XYZ then tmux crashes
- This bug appears to be fixed by upstream commit aa17f0e0c1
- That commit has been cherry-picked in tmux 3.4-3:
---
tmux (3.4-3) unstable; urgency=medium
* Cherry-pick commit aa17f0e0c1 from upstream to fix crash on invalid
Sixel input.
---
Closely related issues that are to be fixed together go into the same
bug.
Thanks!
https://wiki.ubuntu.com/StableReleaseUpdates
** Changed in: tmux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068393
Title:
Sync tmux (main) from Oracular (main)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tmux/+bug/2068393/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
