From: Marco Atzeri <marco.atzeri@gmail.com>
To: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr@ncbi.nlm.nih.gov>
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: [EXTERNAL] Re: svn crashes when connection to server refused
Date: Tue, 18 Jan 2022 07:15:03 +0100 [thread overview]
Message-ID: <d9bb425b-5780-2c4d-ec15-32b2b103dada@gmail.com> (raw)
In-Reply-To: <DM8PR09MB709586896BBA95C2B88610CEA5589@DM8PR09MB7095.namprd09.prod.outlook.com>
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
next prev parent reply other threads:[~2022-01-18 6:15 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 [this message]
2022-01-18 17:31 ` Brian Inglis
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=d9bb425b-5780-2c4d-ec15-32b2b103dada@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
--cc=lavr@ncbi.nlm.nih.gov \
/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).