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 01:35:56 -0700 [thread overview]
Message-ID: <a8821ee9-f48e-8ca3-e5c3-2c0277e6d397@SystematicSw.ab.ca> (raw)
In-Reply-To: <DM8PR09MB709586896BBA95C2B88610CEA5589@DM8PR09MB7095.namprd09.prod.outlook.com>
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.]
next prev parent reply other threads:[~2022-01-18 8:35 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
2022-01-18 19:30 ` Marco Atzeri
2022-01-18 8:35 ` Brian Inglis [this message]
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=a8821ee9-f48e-8ca3-e5c3-2c0277e6d397@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).