Hi,
after upgrading to 1.7.x i've noticed some bug in svn lock machinery.
here's a reduced testcase with local repo.
1). create from root a repo and change owner/mod to svnadmin.svnusers.
# svnadmin create test.svn
# chown -R svnadmin.svnusers test.svn
# chmod g+ws test.svn/db -R
2). from user
On 15.12.2011 13:25:58, Stefan Sperling wrote:
> I would recommend to use a 1.6 client instead of trying to upgrade the WC.
> And above all import the data into a new repository so it can be versioned
> properly again. Having a working copy as the only copy of the data was
> bound to cause a dead-e
On 15.12.2011 13:04:30, Philip Martin wrote:
> The most likely thing to be missing is the root URL.
That was it. After fixing entries it worked.
Thank you!
Jojakim
I'd think the right thing to do here would be to import your pristine
directory under .svn as the start of a new repository, check it out
and copy over changes from the visible part of the working copy,
commit that, then work as normal. Anyone have a better idea or hints
on how to avoid unwanted m
Stefan Sperling wrote on Thu, Dec 15, 2011 at 12:37:00 +0100:
> 'svn upgrade' contacts the server when upgrading very old working
> copies which didn't store the repository root and UUID.
For the record, how old is "old" here? 1.5? 1.0?
On Thu, Dec 15, 2011 at 12:04:31PM +, Philip Martin wrote:
> Stefan Sperling writes:
>
> > You will likely be better
> > of with a new checkout, given that such old working copies often exhibit
> > problems during or after an upgrade to the 1.7.x format anyway.
>
> That's not possible as the
Stefan Sperling writes:
> You will likely be better
> of with a new checkout, given that such old working copies often exhibit
> problems during or after an upgrade to the 1.7.x format anyway.
That's not possible as the repository effectively no longer exists.
However it is possible to manually
Guten Tag Jojakim Stahl,
am Donnerstag, 15. Dezember 2011 um 11:54 schrieben Sie:
> Till svn 1.6
> we could use svn diff to see changes that we implemented after the initial
> crash.
Does this mean you worked on the working copy and just never
committed? You could have created a new repository wi
On Thu, Dec 15, 2011 at 11:54:36AM +0100, Jojakim Stahl wrote:
> Hi all!
>
> Before several years we had a HDD crash and lost part of our svn history.
> Now we have old projects (we have many customer-individual projects) where
> we only have the working copy. This WC refers to an old svn server,
Hi all!
Before several years we had a HDD crash and lost part of our svn history.
Now we have old projects (we have many customer-individual projects) where
we only have the working copy. This WC refers to an old svn server, it
cannot be switched because the WC head revision has been lost. Till
how to get the URL,for example:
use show log, I modify log message of some revision, how to get the
current URL of the modify.
Johan Corveleyn wrote on Thu, Dec 15, 2011 at 09:33:00 +0100:
> After that, you can perform a new checkout on Windows. I don't think
> you can salvage your partly checked out working copy, you should get a
> new one (and if necessary, transfer your local changes to the new
> working copy manually).
You're seeing intended behaviour, including the --set-depth=exclude
feature (which is new in 1.6).
Thomas Dziedzic wrote on Wed, Dec 14, 2011 at 21:10:56 -0600:
> Hi,
>
> I used to be able to do:
> svn checkout --depth=empty svn://svn.archlinux.org/packages
> cd packages
> svn up pacman
> rm -r p
Thomas Gier wrote on Thu, Dec 15, 2011 at 08:40:22 +0100:
> I found 3 corrupted revisions so far starting at rev. 12943, HEAD
> was at 14667 yesterday evening. I haven't checked in depth yet,
There are two different sorts of corruption:
- Filesystem corruption: the filesystem backend (FSFS or BDB
On Wed, Dec 14, 2011 at 09:10:56PM -0600, Thomas Dziedzic wrote:
> Hi,
>
> I used to be able to do:
> svn checkout --depth=empty svn://svn.archlinux.org/packages
> cd packages
> svn up pacman
> rm -r pacman
> svn up
>
> and it would leave me with an empty, working copy on my computer in
> subvers
Thanks for your excellent help :) Your intepretation of my structure is
correct. And the Visual Studio 2008\Projects directory is a sub directory
of My Documents created by default by VS2008.
I solved the situation by checking out a new WC. Each subdir in the old WC
worked, so there were no need t
Am 15.12.2011 06:03, schrieb David Fahlander:
Got problems after an upgrade.
1) Upgraded one sub path to 1.7
2) Upgraded sub path by sub path to 1.7
3) Failed to upgrade one of the sub paths, claiming that my localhost SVN
server disconnected the socket. This happened over and over so I decided
On Wed, Dec 14, 2011 at 9:16 PM, Strickland, Stuart
wrote:
>
> In attempting to pull down a copy of the trunk to my PC, I inadvertently
> accessed a file in the Subversion repository that was created on a
> non-Windows machine. The file has a name containing a less-than sign, which
> is illegal
18 matches
Mail list logo
