From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: [EXTERNAL] Re: svn crashes when connection to server refused
Date: Tue, 18 Jan 2022 10:31:59 -0700 [thread overview]
Message-ID: <0d636dbf-3f9a-418a-46e2-c8b941c4ae12@SystematicSw.ab.ca> (raw)
In-Reply-To: <d9bb425b-5780-2c4d-ec15-32b2b103dada@gmail.com>
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?users@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.]
next prev parent reply other threads:[~2022-01-18 17:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-16 22:55 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-01-17 15:51 ` marco atzeri
2022-01-18 2:03 ` [EXTERNAL] " Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-01-18 6:15 ` Marco Atzeri
2022-01-18 17:31 ` Brian Inglis [this message]
2022-01-18 19:30 ` Marco Atzeri
2022-01-18 8:35 ` Brian Inglis
2022-01-26 20:16 ` Andrey Repin
2022-01-26 21:05 ` Marco Atzeri
2022-01-28 8:01 ` Andrey Repin
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=0d636dbf-3f9a-418a-46e2-c8b941c4ae12@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/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).