David Rothenberger wrote:
On 9/25/2009 10:49 PM, Chris Cormie wrote:
I updated Cygwin today via setup.exe and Subversion ceased working:
$ svn status
$
ie no output whatsoever regardless of what command is given to svn
including --help.
[snip]
I hadn't updated for several months so a dozen or so packages were
updated. As far as I know setup.exe doesn't keep a log so I can't tell
you which packages got updated. My current system state is attached.
[snip]
Is this a general issue that needs to be investigated or specific to
my install?
This sounds like you're missing a dependency required by subversion,
although I can't see what it is from your cygcheck output. I use
subversion daily in both 1.5 and 1.7 and it works fine, so this is not a
general problem.
>
I suggest sending the output of "cygcheck /bin/svn" to the list as an
attachment.
You can also try running "strace /bin/svn". This will produce a lot of
output which I would ignore for now. If svn is having a problem finding
another DLL, strace should open a pop-up telling you what is missing.
Please post any findings back to the list so I can fix the svn package's
dependencies if needed.
If it is a missing dependency it's probably not 1st level dependency
since the first thing I did was to manually reinstall subversion and all
1st level dependencies: still svn failed silently.
I can offer evidence that it's *not* a package conflict as I first thought:
I've managed to do a fresh 1.5 install. *svn works* on fresh
base-install 1.5 Comparing the installed packages to my "bad" install I
found 94 new packages I'd added (directly or via dependencies.) I
installed the 94 packages 5 at a time into the fresh Cygwin 1.5: svn
continued to work through the whole 94.
So reproduction of the problem isn't as easy as I thought either. And I
fail to see how my simple existing-package-update-no-install-or-remove
run of setup.exe could cause it.
Now for the amusing bit: I can't get back into the old "bad" 1.5 install
with the failing svn to run cygcheck /bin/svn or strace for you. I'm not
so very surprised, since Cygwin doesn't support multiple installs. Still
if there was a way I'd like to know. By "not getting in" I mean the old
install is still there, but from a cmd shell:
E:\cygwin>Cygwin.bat
chr...@hamster ~
$ mount
E:\cygwin_1_5\bin on /usr/bin type system (binmode)
E:\cygwin_1_5\lib on /usr/lib type system (binmode)
E:\cygwin_1_5 on / type system (binmode)
c: on /c type system (binmode,noumount)
e: on /e type system (binmode,noumount)
g: on /g type system (binmode,noumount)
h: on /h type system (binmode,noumount)
p: on /p type system (binmode,noumount)
that is I tried to launch a shell in E:\cygwin install but ended up in
my new, working install. Can you tell me how to launch a shell in the
old install temporarily to help hunt the bug?
Cheers,
Chris
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
