Re: svn crashes when connection to server refused

2022-01-28 Thread Andrey Repin
Greetings, Marco Atzeri!

> On 26.01.2022 21:16, Andrey Repin wrote:
>> Greetings, marco atzeri!
>> 
>> Marco, on an unrelated note, can you please package Subversion with
>> alternatives support?
>> I understand that the request is uncommon, but I do have uncommon
>> requirements. I'm using a custom Subversion build, which is good for common
>> use, but have a small deficiency in LC_TIME handling (simply put, it always
>> output localized dates, regardless of the settings).
>> Thus I have to use a different Subversion binary for release automation.
>> I already do some massaging to a similar extent, but a proper alternatives
>> support would be much more convenient.
>> 
>> Thank you in advance.
>> 
>> 

> Hi Andrey
> what exactly do you mean ?

> is you need svn to point to another program than

>/usr/bin/svn.exe

> can not you set Alternatives to use a

>/usr/local/bin/svn

> as switch point between /usr/bin/svn.exe and your alternate ?
> What am I missing ?

Hm, point. :) That did not occurred to me. thanks for the idea!


-- 
With best regards,
Andrey Repin
Friday, January 28, 2022 11:00:07

Sorry for my terrible english...


-- 
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: svn crashes when connection to server refused

2022-01-26 Thread Marco Atzeri

On 26.01.2022 21:16, Andrey Repin wrote:

Greetings, marco atzeri!

Marco, on an unrelated note, can you please package Subversion with
alternatives support?
I understand that the request is uncommon, but I do have uncommon
requirements. I'm using a custom Subversion build, which is good for common
use, but have a small deficiency in LC_TIME handling (simply put, it always
output localized dates, regardless of the settings).
Thus I have to use a different Subversion binary for release automation.
I already do some massaging to a similar extent, but a proper alternatives
support would be much more convenient.

Thank you in advance.




Hi Andrey
what exactly do you mean ?

is you need svn to point to another program than

  /usr/bin/svn.exe

can not you set Alternatives to use a

  /usr/local/bin/svn

as switch point between /usr/bin/svn.exe and your alternate ?
What am I missing ?

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: svn crashes when connection to server refused

2022-01-26 Thread Andrey Repin
Greetings, marco atzeri!

Marco, on an unrelated note, can you please package Subversion with
alternatives support?
I understand that the request is uncommon, but I do have uncommon
requirements. I'm using a custom Subversion build, which is good for common
use, but have a small deficiency in LC_TIME handling (simply put, it always
output localized dates, regardless of the settings).
Thus I have to use a different Subversion binary for release automation.
I already do some massaging to a similar extent, but a proper alternatives
support would be much more convenient.

Thank you in advance.


-- 
With best regards,
Andrey Repin
Wednesday, January 26, 2022 22:57:02

Sorry for my terrible english...


-- 
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: [EXTERNAL] Re: svn crashes when connection to server refused

2022-01-18 Thread Marco Atzeri

On 18.01.2022 18:31, Brian Inglis wrote:

On 2022-01-17 23:15, Marco Atzeri wrote:

On 18.01.2022 03:03, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:


Submitted details for adding Cygwin packages to the Apache Subversion 
Binary Packages web page:


 https://subversion.apache.org/packages.html

to the Subversion ML:

 https://lists.apache.org/list?us...@subversion.apache.org:2022-1

Also noticed that current subversion cygport, patches, etc. are not yet 
checked in to the git-cygwin-packages repo:


https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/subversion.git;a=summary 



Now they are in sync.

Uploading to git repository is always one of the things to do later ...

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: [EXTERNAL] Re: svn crashes when connection to server refused

2022-01-18 Thread Brian Inglis

On 2022-01-17 23:15, Marco Atzeri wrote:

On 18.01.2022 03:03, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:

Subversion seems to have along list of upstream issues
can you check if the issue was already noted and solved upstream ?
If so I can deploy a new release.


Looks like 1.14.1 dated Feb 2021 is the latest official release, per 
their website;

and that's what we have in Cygwin.

I also tried to check out and build it right from the repository, but 
there were some
issues  Once finally built I got an error message that the 
https:// scheme wasn’t
supported.  I guess I missed some configuration peculiarities for 
Cygwin (but also,
I noticed that for some reason the source code treats Cygwin as 
Windows -- particularly
how the pathname is assumed to have the drive letters, and that is 
really baffling --

so I am not exactly sure what was meant by that by the SVN developers).



you can rebuild with the same Cygwin setting and patches reusing the
content of the cygwin source packages. You can use Setup to download it.
It should appear under /usr/src.

You will need to install the package cygport to replicate the build

There is large manual to understand the script settings in
usr/share/doc/cygport/html/manual/toc_index.html


Submitted details for adding Cygwin packages to the Apache Subversion 
Binary Packages web page:


https://subversion.apache.org/packages.html

to the Subversion ML:

https://lists.apache.org/list?us...@subversion.apache.org:2022-1

Also noticed that current subversion cygport, patches, etc. are not yet 
checked in to the git-cygwin-packages repo:


https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/subversion.git;a=summary

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

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

--
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: [EXTERNAL] Re: svn crashes when connection to server refused

2022-01-18 Thread Brian Inglis

On 2022-01-17 19:03, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:

Subversion seems to have along list of upstream issues
can you check if the issue was already noted and solved upstream ?
If so I can deploy a new release.



Thanks for the suggestion!
Looks like 1.14.1 dated Feb 2021 is the latest official release, per their 
website;
and that's what we have in Cygwin.
I also tried to check out and build it right from the repository, but there 
were some
issues  Once finally built I got an error message that the https:// scheme 
wasn’t
supported.  I guess I missed some configuration peculiarities for Cygwin (but 
also,
I noticed that for some reason the source code treats Cygwin as Windows -- 
particularly
how the pathname is assumed to have the drive letters, and that is really 
baffling --
so I am not exactly sure what was meant by that by the SVN developers).


You should normally be able to build from git-cygwin-packages repo for 
subversion containing cygport, patches, and any other Cygwin files, but 
the current release has not yet been checked in at:


https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/subversion.git

although you can see from the tree 21 patches were available to apply.

So you have to download the source package which will include the 
current cygport, patches, and any other Cygwin files.


It is often a good idea also to look for relevant source patches 
available in packages' sources from upstream, as well as other distros 
such as Fedora (closely related to and used by some to build some Cygwin 
tools, parts of releases, and packages), Debian, MacPorts, and OpenSuSE 
where available:


https://src.fedoraproject.org/rpms/subversion/tree/rawhide
https://salsa.debian.org/lts-team/packages/subversion/-/tree/master/debian/patches
https://github.com/macports/macports-ports/tree/0a3636ef019083102b8eb19ba230d173a2a37afe/devel/subversion/files
https://github.com/bmwiedemann/openSUSE/tree/master/packages/s/subversion
[Thanks to those who pointed me to those package sources repos]

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

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

--
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: [EXTERNAL] Re: svn crashes when connection to server refused

2022-01-17 Thread Marco Atzeri



On 18.01.2022 03:03, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:

Subversion seems to have along list of upstream issues

can you check if the issue was already noted and solved upstream ?
If so I can deploy a new release.


Thanks for the suggestion!

Looks like 1.14.1 dated Feb 2021 is the latest official release, per their 
website;
and that's what we have in Cygwin.

I also tried to check out and build it right from the repository, but there 
were some
issues  Once finally built I got an error message that the https:// scheme 
wasn’t
supported.  I guess I missed some configuration peculiarities for Cygwin (but 
also,
I noticed that for some reason the source code treats Cygwin as Windows -- 
particularly
how the pathname is assumed to have the drive letters, and that is really 
baffling --
so I am not exactly sure what was meant by that by the SVN developers).

Anton Lavrentiev
Contractor NIH/NLM/NCBI




you can rebuild with the same Cygwin setting and patches reusing the
content of the cygwin source packages. You can use Setup to download it.
It should appear under /usr/src.

You will need to install the package cygport to replicate the build

There is large manual to understand the script settings in
usr/share/doc/cygport/html/manual/toc_index.html



--
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: [EXTERNAL] Re: svn crashes when connection to server refused

2022-01-17 Thread Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin
> Subversion seems to have along list of upstream issues
> 
> can you check if the issue was already noted and solved upstream ?
> If so I can deploy a new release.

Thanks for the suggestion!

Looks like 1.14.1 dated Feb 2021 is the latest official release, per their 
website;
and that's what we have in Cygwin.

I also tried to check out and build it right from the repository, but there 
were some
issues  Once finally built I got an error message that the https:// scheme 
wasn’t
supported.  I guess I missed some configuration peculiarities for Cygwin (but 
also,
I noticed that for some reason the source code treats Cygwin as Windows -- 
particularly
how the pathname is assumed to have the drive letters, and that is really 
baffling --
so I am not exactly sure what was meant by that by the SVN developers).

Anton Lavrentiev
Contractor NIH/NLM/NCBI


-- 
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: svn crashes when connection to server refused

2022-01-17 Thread marco atzeri
On Sun, Jan 16, 2022 at 11:55 PM Lavrentiev, Anton (NIH/NLM/NCBI) [C]
via Cygwin  wrote:
>
> Hi all,
>
> Before I go ahead and try to submit this as a bug report with the Apache 
> Subversion project, I wanted to ask
> if anybody experiences the same issue as me (or, maybe it's a Cygwin issue, 
> not svn's)...
>
> I use svn at home on Cygwin via a tunneled connection to my SVN server at 
> work, so when the tunnel is
> not up (and basically, svn connects to localhost:SVN-port and supposedly 
> receives "connection refused"),
> it crashes ungracefully with SEGFAULT leaving the repo locked ("svn cleanup" 
> is required).  When the tunnel
> is up, everything goes well.  Also, I could not reproduce any such behavior 
> at work, because the server there
> is readily available, so the connection always succeeds.
>
> It's not new, but it reached a tipping point, and I would rather try to have 
> it fixed.
>
> So this is how it looks like when the tunnel is down:
>
> $ svn --version
> svn, version 1.14.1 (r1886195)
>compiled Feb 12 2021, 17:58:10 on x86_64-unknown-cygwin
> ...
> $ svn up
> Updating '.':
> Segmentation fault (core dumped)

Subversion seems to have along list of upstream issues

can you check if the issue was already noted and solved upstream ?
If so I can deploy a new release.

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


svn crashes when connection to server refused

2022-01-16 Thread Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin
Hi all,

Before I go ahead and try to submit this as a bug report with the Apache 
Subversion project, I wanted to ask
if anybody experiences the same issue as me (or, maybe it's a Cygwin issue, not 
svn's)...

I use svn at home on Cygwin via a tunneled connection to my SVN server at work, 
so when the tunnel is
not up (and basically, svn connects to localhost:SVN-port and supposedly 
receives "connection refused"),
it crashes ungracefully with SEGFAULT leaving the repo locked ("svn cleanup" is 
required).  When the tunnel
is up, everything goes well.  Also, I could not reproduce any such behavior at 
work, because the server there
is readily available, so the connection always succeeds.

It's not new, but it reached a tipping point, and I would rather try to have it 
fixed.

So this is how it looks like when the tunnel is down:

$ svn --version
svn, version 1.14.1 (r1886195)
   compiled Feb 12 2021, 17:58:10 on x86_64-unknown-cygwin
...
$ svn up
Updating '.':
Segmentation fault (core dumped)
$ svn up
svn: E155004: Run 'svn cleanup' to remove locks (type 'svn help cleanup' for 
details)
svn: E155004: Working copy '/cygdrive/g/cygwin/cxx' locked.
svn: E155004: '/cygdrive/g/cygwin/cxx' is already locked.

(it does not crash the second time because it does not attempt to connect, but 
once "svn cleanup"
is done, it's going to do exactly the same as above and coredump)

The stackdump file does not look very useful, but here it is:

$ cat svn.exe.stackdump
Exception: STATUS_ACCESS_VIOLATION at rip=000
rax= rbx= rcx=0008000E7388
rdx=0008000EF6C8 rsi=0008000DE348 rdi=0011
r8 = r9 =000800118088 r10=0001
r11=0003F4F45359 r12=B9E0 r13=B9E8
r14=0008000DE3D8 r15=0008000E7388
rbp=B9F8 rsp=B988
program=C:\cygwin64\bin\svn.exe, pid 51421, thread main
cs=0033 ds=002B es=002B fs=0053 gs=002B ss=002B
Stack trace:
FrameFunctionArgs
End of stack trace

Also, I tried to strace svn in this situation, and this is what has transpired:

$ strace -m all -n -o svn.strace /usr/bin/svn up
Updating '.':
2943523 [main] svn 51421 cygwin_exception::open_stackdumpfile: Dumping stack 
trace to svn.exe.stackdump

The bottom portion of svn.strace (after the connect attempt) follows below.

Thanks for any insights!

P.S. I'm a little behind with my Cygwin version, but like I said, this problem 
was going on for me for many
versions, both SVN and Cygwin...  SVN seems current per Cygwin Setup, though.

$ uname -a
CYGWIN_NT-6.1 X 3.2.0(0.340/5/3) 2021-03-29 08:42 x86_64 Cygwin

P.P.S. I actually tried my recent own build (from Jan 14) of Cygwin, and the 
behavior did not change at all:

$ uname -a
CYGWIN_NT-6.1 X 3.4.0(0.341/5/3) 2022-01-14 21:40 x86_64 Cygwin

$ svn up
Updating '.':
Segmentation fault (core dumped)

...
11708  397483 [main] svn 51421 cygwin_socket: socket (2, 1 (flags 0x200), 6)
   47  397530 [main] svn 51421 build_fh_pc: fh 0x1803632C0, dev 001E0024
  148  397678 [main] svn 51421 fhandler_base::set_close_on_exec: set 
close_on_exec for  to 1
   28  397706 [main] svn 51421 fhandler_base::set_flags: flags 0x50002, 
supplied_bin 0x0
   29  397735 [main] svn 51421 fhandler_base::set_flags: O_TEXT/O_BINARY set in 
flags 0x1
   28  397763 [main] svn 51421 fhandler_base::set_flags: filemode set to binary
   23  397786 [main] svn 51421 cygwin_socket: 3 = socket(2, 1 (flags 
0x200), 6)
   29  397815 [main] svn 51421 fcntl64: fcntl(3, 3, ...)
   29  397844 [main] svn 51421 fhandler_base::fcntl: GETFL: 0x50002
   25  397869 [main] svn 51421 fcntl64: 327682 = fcntl(3, 3, 0x0)
   30  397899 [main] svn 51421 fcntl64: fcntl(3, 4, ...)
   37  397936 [main] svn 51421 fhandler_socket_wsock::ioctl: socket is now 
nonblocking
   28  397964 [main] svn 51421 fhandler_socket_wsock::ioctl: 0 = 
ioctl_socket(8004667E, 0xB86C)
   31  397995 [main] svn 51421 fhandler_base::set_flags: flags 0x54002, 
supplied_bin 0x0
   33  398028 [main] svn 51421 fhandler_base::set_flags: O_TEXT/O_BINARY set in 
flags 0x1
   27  398055 [main] svn 51421 fhandler_base::set_flags: filemode set to binary
   31  398086 [main] svn 51421 fcntl64: 0 = fcntl(3, 4, 0x54002)
   59  398145 [main] svn 51421 fhandler_socket_inet::setsockopt: setsockopt 
optval=1
   27  398172 [main] svn 51421 cygwin_setsockopt: 0 = setsockopt(3, 6, 0x1, 
0xB9D0, 4)
--- Process 8520 (pid: 51421) thread 8552 created
  437  398609 [main] svn 51421 __set_errno: void __set_winsock_errno(const 
char*, int):206 setting errno 119
   71  398680 [main] svn 51421 __set_winsock_errno: connect:821 - winsock error 
10036 -> errno 119
   55  398735 [main] svn 51421 cygwin_connect: -1 = connect(3, 0x8000D5878, 
16), errno 119
 3250  401985 [main] svn 51421 __set_errno: char* strerror(int):397 setting 
errno 22
   52  402037 [main] svn 51421 __set_errno: char* strerror(int):397 setting 
errno 22
   48  402085 [main] svn