public inbox for
 help / color / mirror / Atom feed
From: "Rockefeller, Harry" <>
To: "" <>
Subject: subversion problem
Date: Mon, 23 Apr 2018 20:20:00 -0000	[thread overview]
Message-ID: <> (raw)

I just updated packages this morning and noticed there were some
subversion updates.  I was wondering if version 10 is new and requires me to do something?
Or maybe the recent release broke something?

About my Cygwin system: [If more information is required please ask.]
$ uname -a
CYGWIN_NT-6.1 HARRYR-PC 2.10.0(0.325/5/3) 2018-02-02 15:16 x86_64 Cygwin
$ cygcheck -c subversion
Package              Version        Status
subversion           1.10.0-1       OK
$ svnadmin info /usr/local/svnroot
Path: /usr/local/svnroot
UUID: 6c5b531c-fdee-0310-8ccc-e19e2ad93f33
Revisions: 1029
Repository Format: 5
Compatible With Version: 1.9.0
Repository Capability: mergeinfo
Filesystem Type: fsfs
Filesystem Format: 7
FSFS Sharded: yes
FSFS Shard Size: 1000
FSFS Shards Packed: 0/1
FSFS Logical Addressing: yes
Configuration File: /usr/local/svnroot/db/fsfs.conf

I also ran "svnadmin verify" on the repository above and there were no errors.
Also, as shown here, I use subversion only locally.

Simple example of the problem.

harryr@HARRYR-PC ~/test_subversion
$ svn co file:///usr/local/svnroot/ced
A    ced/branches
A    ced/tags
A    ced/trunk
svn: E000002: Can't change perms of file '/cygdrive/c/Users/harryr/test_subversion/ced/.svn/pristine/85/85d3a383ab07dabcd654cbe2d4bfea4f6a658b6c.svn-base': No such file or directory

ced/trunk is the only path that actually has files in it.

$ svn list file:///usr/local/svnroot/ced/trunk/cedmain.c

Problem reports:
Unsubscribe info:

             reply	other threads:[~2018-04-23 20:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-23 20:20 Rockefeller, Harry [this message]
2018-04-23 20:31 ` David Rothenberger
2018-04-22 14:04   ` Cygwin subversion and UNC path Yasutaka Atarashi
2018-04-22 15:58     ` David Rothenberger
2018-04-25 13:11     ` subversion problem Yasutaka Atarashi
2018-04-25 17:03       ` David Rothenberger
2018-04-23 21:28   ` Rockefeller, Harry
2018-04-23 21:05 ` Andrey Repin
2018-04-23 21:28   ` Rockefeller, Harry

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).