[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

cygwin user with two issues

From: ernie nichols <ernie.nichols_at_comcast.net>
Date: 2004-11-30 01:33:13 CET

Environment:
cygwin v 1.5.12-1
svn v 1.1.1(r11581) from latest cygwin update
win98 SE OS

Have been using RCS and CVS for the past several years and decided to
try subversion to deal with branching in a more natural way - saving
both text stuff and resource stuff (*.bmp)..
Currently working on a Palm project using PilRC and attendant tools.

Issue #1:
After reading the svn book and help files I made a repository and
checked out a working copy. The first issue took me a day to work
around using the FSFS access method. The import part worked fine but
when checking out with :
===============
svn checkout file:///repos/project/trunk aa
=================
I get:
============
svn: Unable to open an ra_local session to URL
svn: Unable to open repository 'file:///repos/project/trunk'
svn: Can't get shared lock on file '/repos/locks/db.lock': Resource
temporarily unavailable
==============
I've tried all variations of the URL with no effect -- by CDing to the
aa subdirectory and doing
=======
svn up
========
everything arrives in the subdirectory but this seems like an error
somewhere in the code to make me do a second operation to get the
checked out stuff to work on and to display an error message that makes
no sense to me. I've googled around with the error message but
responses did not seem to apply to my situation. By doing the svn up
command in the subdirectory I can continue to use the product but wonder
what else is lurking to screw me up.

At this point I was able to do a "make" that included *.bmp files as
well as text files processed thru the various gcc/ld/palm utilities to
generate a runnable PRC file that would download to a Palm and execute.

Issue #2:
I then made a branch as recommended in the svn book and checked that out
after adding a couple of debug files to the repository. At this point
the *.bmp files had changed sizes and were no longer usable by the build
routines - the utility claimed that the *.bmp files were compressed and
not usable. I looked at the sizes of the checked out *.bmp files and
indeed the color bit maps were of a different(and larger) size than the
original. What's going on here?
The product is nonfunctional at this point if I can't save *.bmp files
and have them returned in a usable form.

Anyone have an idea what is happening and how to fix it?

thanks

    ernie

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Nov 30 16:10:48 2004

This is an archived mail posted to the Subversion Dev mailing list.