Re: ncurses version (was: Tmux crashes on copy)

2024-01-31 Thread Brian Inglis via Cygwin

On 2024-01-31 10:36, ASSI via Cygwin wrote:

Jon Turney via Cygwin writes:

If upstream really is making multiple releases called '6.4', which
we're supposed to distinguish by some other means, then there aren't
really any good answers...



There's only one official 6.4 release, but just about everyone packages
one of the roughly weekly snapshots inbetween releases (depending on
where you are looking they are also called beta versions), which are
named 6.4-mmdd upstream.  We can't have a "-" in the version number,
hence the suggestion to replace it with a "+".


[moving discussion to -apps]

Upstream developer is Thomas Dickey at invisible-island.net so no git.

My only concern is if 6.4+20240203-1 !> 6.4-20240120 as strvercmp test beds 
disagree, presumably about the effect of the delimiter, possibly because the + 
may be treated similarly to a prefix for an RC preceding the 6.4 release?


For guidance I have looked at:

https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning/

which states that ~ prefixes pre-stable "snapshot" releases and ^ prefixes 
post-stable "snapshot" releases where . or nothing prefixes upstream bugfix or 
patch level releases, so perhaps we should just use version suffix .mmdd?


I have downloaded and locally installed Fedora rpmdevtools package but Cygwin 
python rpm module seems to lack labelCompare():


$ rpmdev-vercmp 6.4+20240203-1 6.4-20240120
/usr/local/lib/python3.9/site-packages/rpm.py:15: UserWarning: The RPM Python 
bindings are not currently available via PyPI.


Please install them with your distro package manager (typically called
'python2-rpm' or 'python3-rpm'), and ensure that any virtual environments
needing the API are configured to be able to see the system site packages
directory.

  warnings.warn(warning_msg)
Traceback (most recent call last):
  File "/home/BWI/bin/rpmdev-vercmp", line 121, in 
main()
  File "/home/BWI/bin/rpmdev-vercmp", line 108, in main
rc = rpm.labelCompare((e1 or None, v1 or None, r1 or None),
AttributeError: module 'rpm' has no attribute 'labelCompare'

I also pip3 installed SAS SW rpm_vercmp which seems okay:

$ python3 -c 'import 
rpm_vercmp;print(rpm_vercmp.vercmp("6.4+20240203-1","6.4-20240120"))

'
1

and wrote a wrapper for shell script functions I found which agrees:

$ ~/src/fedora/rpm-ver.bash 6.4+20240203-1 6.4-20240120
0 6 4 20240203 1
0 6 4 20240120
6.4+20240203-1   6.4-20240120
0 6 4 20240203 1 0 6 4 20240120
sizes 5 4 max 5
20240203 != 20240120
8 ? 8
1

How are Cygwin pre-stable RC releases defined differently from post-stable 
snapshot releases and upstream patch releases?


--
Take care. Thanks, Brian Inglis  Calgary, Alberta, Canada

La perfection est atteinte   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry

--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


Re: Tmux crashes on copy

2024-01-31 Thread ASSI via Cygwin
Jon Turney via Cygwin writes:
> If upstream really is making multiple releases called '6.4', which
> we're supposed to distinguish by some other means, then there aren't
> really any good answers...

There's only one official 6.4 release, but just about everyone packages
one of the roughly weekly snapshots inbetween releases (depending on
where you are looking they are also called beta versions), which are
named 6.4-mmdd upstream.  We can't have a "-" in the version number,
hence the suggestion to replace it with a "+".


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra

-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


Re: Tmux crashes on copy

2024-01-31 Thread marco atzeri via Cygwin
On Wed, Jan 31, 2024 at 2:39 PM Jon Turney via Cygwin  wrote:
>
> On 21/01/2024 22:13, Brian Inglis via Cygwin wrote:
> > On 2024-01-21 14:12, ASSI via Cygwin wrote:
> >> Brian Inglis via Cygwin writes:
> >>> Previous maintainer added some artificial single digit release
> >>> prefixes (in a few packages), but we decided to drop those and use the
> >>> release date directly as used in the package.
> >
> >> That is the upstream versioning scheme for patch releases or beta
> >> versions, which can't be used directly on Cygwin without losing the
> >> release part of the package version.
> >> You might want to go for something like 6.4+20240120-1 instead.
>
> I'm not sure that's the right solution
>
> Ideally, V should be the upstream version label.
>
> If upstream really is making multiple releases called '6.4', which we're
> supposed to distinguish by some other means, then there aren't really
> any good answers...
>
> See the mess that is https://repology.org/project/ncurses/information,
> where everyone makes up there own scheme.
>
> > Good point, but I figured we could add the suffix .1 or something if we
> > could not get a change merged upstream: the snapshots are weekly or
> > better in ncurses, although others not so often, and I have no idea how
> > they decide when to release a new GNU version 6.5?
> >
> > What happens if we change versioning from 6.4-mmdd to 6.4+mmdd-1?
>

 for me  will make more sense a scheme like

6.4-5+GITID
6.4-6+GITID
..

just my 2c€

Regards
Marco

-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


Re: Tmux crashes on copy

2024-01-31 Thread Jon Turney via Cygwin

On 21/01/2024 22:13, Brian Inglis via Cygwin wrote:

On 2024-01-21 14:12, ASSI via Cygwin wrote:

Brian Inglis via Cygwin writes:

Previous maintainer added some artificial single digit release
prefixes (in a few packages), but we decided to drop those and use the
release date directly as used in the package.



That is the upstream versioning scheme for patch releases or beta
versions, which can't be used directly on Cygwin without losing the
release part of the package version.
You might want to go for something like 6.4+20240120-1 instead.


I'm not sure that's the right solution

Ideally, V should be the upstream version label.

If upstream really is making multiple releases called '6.4', which we're 
supposed to distinguish by some other means, then there aren't really 
any good answers...


See the mess that is https://repology.org/project/ncurses/information, 
where everyone makes up there own scheme.


Good point, but I figured we could add the suffix .1 or something if we 
could not get a change merged upstream: the snapshots are weekly or 
better in ncurses, although others not so often, and I have no idea how 
they decide when to release a new GNU version 6.5?


What happens if we change versioning from 6.4-mmdd to 6.4+mmdd-1?



--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


Re: Tmux crashes on copy

2024-01-21 Thread Brian Inglis via Cygwin

On 2024-01-21 14:12, ASSI via Cygwin wrote:

Brian Inglis via Cygwin writes:

Previous maintainer added some artificial single digit release
prefixes (in a few packages), but we decided to drop those and use the
release date directly as used in the package.



That is the upstream versioning scheme for patch releases or beta
versions, which can't be used directly on Cygwin without losing the
release part of the package version.
You might want to go for something like 6.4+20240120-1 instead.


Good point, but I figured we could add the suffix .1 or something if we could 
not get a change merged upstream: the snapshots are weekly or better in ncurses, 
although others not so often, and I have no idea how they decide when to release 
a new GNU version 6.5?


What happens if we change versioning from 6.4-mmdd to 6.4+mmdd-1?

My rpm-ver.bash shell script says okay, but rpmdev-vercmp (from rpmdevtools 9.6) 
now complains, rpm{,-build,-devel}, python3{,9}-rpm are installed and OK, any idea?


/usr/local/lib/python3.9/site-packages/rpm.py:15: UserWarning: The RPM Python 
bindings are not currently available via PyPI.


Please install them with your distro package manager (typically called
'python2-rpm' or 'python3-rpm'), and ensure that any virtual environments
needing the API are configured to be able to see the system site packages
directory.

  warnings.warn(warning_msg)
Traceback (most recent call last):
  File "/mnt/c/Users/bwi/src/fedora/rpmdevtools-RPMDEVTOOLS_9_6/rpmdev-vercmp", 
line 121, in 

main()
  File "/mnt/c/Users/bwi/src/fedora/rpmdevtools-RPMDEVTOOLS_9_6/rpmdev-vercmp", 
line 108, in main

rc = rpm.labelCompare((e1 or None, v1 or None, r1 or None),
AttributeError: module 'rpm' has no attribute 'labelCompare'

--
Take care. Thanks, Brian Inglis  Calgary, Alberta, Canada

La perfection est atteinte   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry

--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


Re: Tmux crashes on copy

2024-01-21 Thread ASSI via Cygwin
Brian Inglis via Cygwin writes:
> Previous maintainer added some artificial single digit release
> prefixes (in a few packages), but we decided to drop those and use the
> release date directly as used in the package.

That is the upstream versioning scheme for patch releases or beta
versions, which can't be used directly on Cygwin without losing the
release part of the package version.

You might want to go for something like 6.4+20240120-1 instead.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs

-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


Re: Tmux crashes on copy

2024-01-21 Thread Brian Inglis via Cygwin

On 2024-01-18 01:24, Takashi Yano via Cygwin wrote:

On Thu, 18 Jan 2024 16:37:59 +0900 (JST)
Yasuhiro Kimura wrote:

On Wed, 17 Jan 2024 12:30:59 +, David Stephenson via Cygwin wrote:



When using the copy function in tmux it crashes on Enter.
Steps:
ctrl-[ (enter copy mode)
Navigate to text
space (start copy)
Navigate to end of text
Enter (to select highlighted text) at this point tmux crashes
cygcheck.out (email redacted) and tmux.exe.stackdump attached


Known issue also on Fedora with tmux:

https://github.com/tmux/tmux/issues/3699

https://github.com/tmux/tmux/commit/b202a2f1b517a3de7141fc35fbd9e39ed5ac5284

new release not yet available - maintainer will have to apply upstream patch, or 
users will have to downgrade ncurses.


It looks like ncurses maintenance lagged, while tmux was updated; now ncurses is 
being updated, so tmux needs updated to 3.3a, with above patch and any prereqs.



I have same problem with Windows 11 2023H2, and it disappears if I
rollback libncursesw10 package from 6.4-20231230 to 6.4-3.20230114.
So we may hit the bug of libncursesw10 6.4-20231230.



TO: Brian
BTW, shouldn't the package name
libncursesw10-6.4-20231230
be
libncursesw10-6.4-4.20231230
Or is this intentional?


Previous maintainer added some artificial single digit release prefixes (in a 
few packages), but we decided to drop those and use the release date directly as 
used in the package.


--
Take care. Thanks, Brian Inglis  Calgary, Alberta, Canada

La perfection est atteinte   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
 -- Antoine de Saint-Exupéry

--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


Re: Tmux crashes on copy

2024-01-18 Thread Takashi Yano via Cygwin
On Thu, 18 Jan 2024 16:37:59 +0900 (JST)
Yasuhiro Kimura wrote:
> From: David Stephenson via Cygwin 
> Subject: Tmux crashes on copy
> Date: Wed, 17 Jan 2024 12:30:59 +
> 
> > When using the copy function in tmux it crashes on Enter.
> > 
> > Steps:
> > 
> > ctrl-[ (enter copy mode)
> > Navigate to text
> > space (start copy)
> > Navigate to end of text
> > Enter (to select highlighted text) at this point tmux crashes
> > 
> > cygcheck.out (email redacted) and tmux.exe.stackdump attached
> > 
> > Thanks
> 
> I have same problem with Windows 11 2023H2, and it disappears if I
> rollback libncursesw10 package from 6.4-20231230 to 6.4-3.20230114.
> So we may hit the bug of libncursesw10 6.4-20231230.

TO: Brian

BTW, shouldn't the package name
libncursesw10-6.4-20231230 
be
libncursesw10-6.4-4.20231230 
?

Or is this intentional?

-- 
Takashi Yano 

-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


Re: Tmux crashes on copy

2024-01-17 Thread Yasuhiro Kimura via Cygwin
From: David Stephenson via Cygwin 
Subject: Tmux crashes on copy
Date: Wed, 17 Jan 2024 12:30:59 +

> When using the copy function in tmux it crashes on Enter.
> 
> Steps:
> 
> ctrl-[ (enter copy mode)
> Navigate to text
> space (start copy)
> Navigate to end of text
> Enter (to select highlighted text) at this point tmux crashes
> 
> cygcheck.out (email redacted) and tmux.exe.stackdump attached
> 
> Thanks

I have same problem with Windows 11 2023H2, and it disappears if I
rollback libncursesw10 package from 6.4-20231230 to 6.4-3.20230114.
So we may hit the bug of libncursesw10 6.4-20231230.

Regards.

---
Yasuhiro Kimura

-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


Tmux crashes on copy

2024-01-17 Thread David Stephenson via Cygwin
When using the copy function in tmux it crashes on Enter.

Steps:

ctrl-[ (enter copy mode)
Navigate to text
space (start copy)
Navigate to end of text
Enter (to select highlighted text) at this point tmux crashes

cygcheck.out (email redacted) and tmux.exe.stackdump attached

Thanks


cygcheck.out
Description: Binary data


tmux.exe.stackdump
Description: Binary data

-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple