RE: Subversion Binaries.

[Cooke, Mark]

> 
> I'm using the Subversion 1.6.6 (windows) binaries hosted on 
> tigris.org.
>  
> I've configured to run subversion on Apache Httpd using mod_dav_svn.
>  
> I was looking for Apache 2.2.x compatible binaries (free 
> versions) for Subversion latest and could not find one.
>  
> Though slicksvn provides command-line tools for subversion, 
> they do not ship the apache modules and python bindings.
>  
> I've tried contacting DJHeap and EbSwift on Tigris.org for 
> getting an updated version of subversion installer on to 
> tigris.org domain.
> And looks like they are not able to generate binaries.
>  
> May I request the team to kindly upload latest subversion 
> binaries (as reference implementation)  on to tigris.org. or 
> apache.org.
>  
> This would help us (the user community) by giving us access 
> to the "plain vanilla" versions of Subversion under apache license.
> And not to be tied with any vendor specific product.
>  
> Thanks in advance,
> Sincerely,
> Elisha Ebenezer
> 
Can I suggest that you search the list before posting questions?  This
has been covered quite a bit since 1.6.9 was released.

Having said that, I've just checked the apache archive and cannot find a
search function.  You could try http://subversion.markmail.org/

Searching reveals a thread with the subject "Re: Tigris binary packages
for Windows" in which a generous individual named David has stepped up
to the task and has provided windows binaries on his own site pending
thorough testing by the community and access to the "right" place to put
them.

Here's the relevant bit for the terminally lazy:

>
 From: David Darj [mailto:z...@alagazam.net]
 Sent: 22 April 2010 21:21

 I have built both 1.6.9 and 1.6.11
 They are available on my webpage http://alagazam.net
 You (and anyone else) is welcome to download and use it.

 The reason I've not announced the release in this (users)
 list is that I've hoped some people reading the dev list
 (where I did announce it) to download and test it first so
 I know my build environment is okey.
 As the web page says all test on subversion itself is running
 ok., but the bindings has not been tested.

Size of SVN Transaction vs Actual commit size

[Ravi Roy]

Hi

General question about Transaction size versus actual file commit size. I am
getting strange results when I am trying to commit 1.28 file and transaction
size I am getting is 5538 bytes. Does somebody knows the mystery ?

I expect transaction size to be the same as actual commit size ? or some
compression in between ?

Can somebody throw some light on this please?

Thanks

-RR

Cannot reintegrate feature branch

[Jean Seurin]

Hi,

I just persuaded my organisation to give a try to Feature Branch.

After 3 merges only, when I attempt to --dry-run a merge --reintegrate 
I've got the following error:


svn merge --reintegrate ^/branches/project-dev --dry-run

With an OSX 1.6.11 client :

svn: Cannot reintegrate into a working copy not entirely at infinite depth

with a Ubuntu 1.6.5 client on fresh check out:

svn: Reintegrate can only be used if revisions 6336 through 6393 were 
previously merged from svn://company/company/trunk/project to the 
reintegrate source, but this is not the case:
  
branches/project-dev/src/test/java/com/company/client/project/adherent/persistence/AdherentDaoHibernateTest.java
Missing ranges: 
/trunk/project/src/test/java/com/company/client/project/adherent/persistence/AdherentDaoHibernateTest.java:6336-6389
  
branches/project-dev/src/test/java/com/company/client/project/codeobjet/persistence/CodeObjetDaoHibernateTest.java
Missing ranges: 
/trunk/project/src/test/java/com/company/client/project/codeobjet/persistence/CodeObjetDaoHibernateTest.java:6336-6389
  
branches/project-dev/src/test/java/com/company/client/project/courrier/persistence/CourrierDaoHibernateTest.java
Missing ranges: 
/trunk/project/src/test/java/com/company/client/project/courrier/persistence/CourrierDaoHibernateTest.java:6336-6389
  
branches/project-dev/src/test/java/com/company/client/project/dossierstagiaire/persistence/DossierStagiaireDaoHibernateTest.java
Missing ranges: 
/trunk/project/src/test/java/com/company/client/project/dossierstagiaire/persistence/DossierStagiaireDaoHibernateTest.java:6336-6389

  branches/project-dev/src/test/resources/log4j.properties
Missing ranges: 
/trunk/project/src/test/resources/log4j.properties:6336-6389


I really don't undertsand what has happened. The merge went well.
I've tried to modify the svn:mergeinfo properties to add the missing 
info but to now avail. I think I shouldn't have to that.


Help please!
Jean

Fwd: Cannot reintegrate feature branch

[Jean Seurin]

Some more information, that may indicate a bug:

All and only the 5 files concerned with the probleme have been commited
during after a merge from the trunk, empty of modification, but with the raw
properties modified as follow:
added line
/branches/project-1.13/*pathToFile*:6266-6372

This comes from a merge done on the trunk from a release branch, which in
turn made its way to the Feature branch of the trunk.

The operation seem regular to me, the question is why only those 5 files
have add the mergeinfo added?

What can I do to solve this? Would simply remove the added line in mergeinfo
for those 5 files would do trick?

thanks
Jean

-- Forwarded message --
From: Jean Seurin 
Date: Thu, May 6, 2010 at 6:18 PM
Subject: Cannot reintegrate feature branch
To: users@subversion.apache.org


 Hi,

I just persuaded my organisation to give a try to Feature Branch.

After 3 merges only, when I attempt to --dry-run a merge --reintegrate I've
got the following error:

svn merge --reintegrate ^/branches/project-dev --dry-run

With an OSX 1.6.11 client :

svn: Cannot reintegrate into a working copy not entirely at infinite depth

with a Ubuntu 1.6.5 client on fresh check out:

svn: Reintegrate can only be used if revisions 6336 through 6393 were
previously merged from svn://company/company/trunk/project to the
reintegrate source, but this is not the case:

branches/project-dev/src/test/java/com/company/client/project/adherent/persistence/AdherentDaoHibernateTest.java
Missing ranges:
/trunk/project/src/test/java/com/company/client/project/adherent/persistence/AdherentDaoHibernateTest.java:6336-6389

branches/project-dev/src/test/java/com/company/client/project/codeobjet/persistence/CodeObjetDaoHibernateTest.java
Missing ranges:
/trunk/project/src/test/java/com/company/client/project/codeobjet/persistence/CodeObjetDaoHibernateTest.java:6336-6389

branches/project-dev/src/test/java/com/company/client/project/courrier/persistence/CourrierDaoHibernateTest.java
Missing ranges:
/trunk/project/src/test/java/com/company/client/project/courrier/persistence/CourrierDaoHibernateTest.java:6336-6389

branches/project-dev/src/test/java/com/company/client/project/dossierstagiaire/persistence/DossierStagiaireDaoHibernateTest.java
Missing ranges:
/trunk/project/src/test/java/com/company/client/project/dossierstagiaire/persistence/DossierStagiaireDaoHibernateTest.java:6336-6389
  branches/project-dev/src/test/resources/log4j.properties
Missing ranges:
/trunk/project/src/test/resources/log4j.properties:6336-6389

I really don't undertsand what has happened. The merge went well.
I've tried to modify the svn:mergeinfo properties to add the missing info
but to now avail. I think I shouldn't have to that.

Help please!
Jean

Re: Fwd: Cannot reintegrate feature branch

[Stefan Sperling]

On Thu, May 06, 2010 at 06:49:51PM +0800, Jean Seurin wrote:
> added line
> /branches/project-1.13/*pathToFile*:6266-6372

A * has special meaning in mergeinfo.
Does the * actually appear in the mergeinfo or not?

Stefan

Re: Fwd: Cannot reintegrate feature branch

[Jean Seurin]

Hi Stefan,

it actually does not appear in mergeinfo.

thanks
Jean

On Thu, May 6, 2010 at 7:11 PM, Stefan Sperling  wrote:

> On Thu, May 06, 2010 at 06:49:51PM +0800, Jean Seurin wrote:
> > added line
> > /branches/project-1.13/*pathToFile*:6266-6372
>
> A * has special meaning in mergeinfo.
> Does the * actually appear in the mergeinfo or not?
>
> Stefan
>

Re: Cannot reintegrate feature branch

[Stefan Sperling]

On Thu, May 06, 2010 at 06:18:07PM +0800, Jean Seurin wrote:
> Hi,
> 
> I just persuaded my organisation to give a try to Feature Branch.
> 
> After 3 merges only,

What 3 merges precisely?

> when I attempt to --dry-run a merge
> --reintegrate I've got the following error:
> 
> svn merge --reintegrate ^/branches/project-dev --dry-run
> 
> With an OSX 1.6.11 client :
> 
> svn: Cannot reintegrate into a working copy not entirely at infinite depth

That error is important.
Why is your working copy not entirely at infinite depth?

If you don't understand this error message, please read:
http://svnbook.red-bean.com/nightly/en/svn.advanced.sparsedirs.html

> with a Ubuntu 1.6.5 client on fresh check out:
> svn: Reintegrate can only be used if revisions 6336 through 6393
> were previously merged from svn://company/company/trunk/project to
> the reintegrate source, but this is not the case:
> branches/project-dev/src/test/java/com/company/client/project/adherent/persistence/AdherentDaoHibernateTest.java
> Missing ranges: 
> /trunk/project/src/test/java/com/company/client/project/adherent/persistence/AdherentDaoHibernateTest.java:6336-6389
> branches/project-dev/src/test/java/com/company/client/project/codeobjet/persistence/CodeObjetDaoHibernateTest.java
> Missing ranges: 
> /trunk/project/src/test/java/com/company/client/project/codeobjet/persistence/CodeObjetDaoHibernateTest.java:6336-6389
> branches/project-dev/src/test/java/com/company/client/project/courrier/persistence/CourrierDaoHibernateTest.java
> Missing ranges: 
> /trunk/project/src/test/java/com/company/client/project/courrier/persistence/CourrierDaoHibernateTest.java:6336-6389
> branches/project-dev/src/test/java/com/company/client/project/dossierstagiaire/persistence/DossierStagiaireDaoHibernateTest.java
> Missing ranges: 
> /trunk/project/src/test/java/com/company/client/project/dossierstagiaire/persistence/DossierStagiaireDaoHibernateTest.java:6336-6389
>   branches/project-dev/src/test/resources/log4j.properties
> Missing ranges:
> /trunk/project/src/test/resources/log4j.properties:6336-6389
> 
> I really don't undertsand what has happened. The merge went well.

Well, let's look at what the error is saying:

So there are files in trunk/project from which you have not yet merged
changes into your branch. You have however merged changes to other
files from revisions 6336 through 6393 to your branch from trunk.

That is what's causing the error. r6336 to 6393 have not been completely
merged from trunk to the branch. The changes listed in the error message
are the changes which have not been merged into the branch yet.

This can easily happen if people do merges into shallow working copies,
with depth != infinity. Maybe your working copy on the Mac is shallow,
and you have done incomplete merges from trunk to the branch with it,
and as a result those merges weren't complete, causing reintegrate to
complain?

To illustrate, let's assume I make a commit to trunk in r50,
which affects the following files:

 /trunk/foo.c
 /trunk/bar/baz.c

Now I merge r50 from trunk to my branch, but the merge omits the change
to bar/baz.c because my branch working copy is shallow.
The mergeinfo created by this merge looks like this:

  /branch (svn:mergeinfo = trunk:r50*)
  /branch/foo.c (svn:mergeinfo = trunk:r50)

The * means "only applies to this folder, not its children".
This happens because svn realises that I did not merge changes r50
made inside of /trunk/bar/. Maybe I still want to merge those later.
Because the mergeinfo at /branch is not inheritable, svn also made
a note at /branch/foo.c saying "this file already has changes to r50".
This will prevent changes made in r50 to foo.c from being merged to
the branch again.

Trying to reintegrate the branch from this state without first merging
everything r50 did will result in the error you are getting.

You want mergeinfo like this:

  /branch (svn:mergeinfo = trunk:r50)

Which says "This entire branch has all changes made to trunk in r50".

BTW, a 1.6 client will flag a tree conflict in this case,
saying "local delete, incoming edit upon merge", because in my WC
it looks as if I deleted bar/ (though it should probably say "local
missing because of shallow working copy, incoming edit").
You probably did the merge with a 1.5 client since you didn't get a conflict?

> I've tried to modify the svn:mergeinfo properties to add the missing
> info but to now avail. I think I shouldn't have to that.

No, you shouldn't. My guess is that (possibly unconscious) use of shallow
working copies is responsible for this error.

Shallow working copies have their use cases, but merging into them
isn't one of them (unless you know about the consequences and know
how to deal with them).

Thanks,
Stefan

Re: Cannot reintegrate feature branch

[Jean Seurin]

I mean 3 times doing a
svn merge ^/trunk/project
on the feature branch and then commit.

So each time commiting some modifications coming from the trunk, 
everything went well.


I checked sparse dir doc, I understand it. I've run the same reintegrate 
command on freshly checked out working copy, same result except that it 
was with a Ubuntu 1.6.5 client and the error was more explicit.


We are not working with shallow working copies.

A possible explanation I foresee, is someone with a 1.5 client doing the 
merge from the Release branch to the trunk, causing problem when merging 
trunk to Feature Branch afterward.


Investigating...

Thanks for your deep explanation of the shallow copies ;)
Jean

Stefan Sperling wrote:

On Thu, May 06, 2010 at 06:18:07PM +0800, Jean Seurin wrote:
   

Hi,

I just persuaded my organisation to give a try to Feature Branch.

After 3 merges only,
 


What 3 merges precisely?

   

when I attempt to --dry-run a merge
--reintegrate I've got the following error:

svn merge --reintegrate ^/branches/project-dev --dry-run

With an OSX 1.6.11 client :

svn: Cannot reintegrate into a working copy not entirely at infinite depth
 


That error is important.
Why is your working copy not entirely at infinite depth?

If you don't understand this error message, please read:
http://svnbook.red-bean.com/nightly/en/svn.advanced.sparsedirs.html

   

with a Ubuntu 1.6.5 client on fresh check out:
svn: Reintegrate can only be used if revisions 6336 through 6393
were previously merged from svn://company/company/trunk/project to
the reintegrate source, but this is not the case:
branches/project-dev/src/test/java/com/company/client/project/adherent/persistence/AdherentDaoHibernateTest.java
 Missing ranges: 
/trunk/project/src/test/java/com/company/client/project/adherent/persistence/AdherentDaoHibernateTest.java:6336-6389
branches/project-dev/src/test/java/com/company/client/project/codeobjet/persistence/CodeObjetDaoHibernateTest.java
 Missing ranges: 
/trunk/project/src/test/java/com/company/client/project/codeobjet/persistence/CodeObjetDaoHibernateTest.java:6336-6389
branches/project-dev/src/test/java/com/company/client/project/courrier/persistence/CourrierDaoHibernateTest.java
 Missing ranges: 
/trunk/project/src/test/java/com/company/client/project/courrier/persistence/CourrierDaoHibernateTest.java:6336-6389
branches/project-dev/src/test/java/com/company/client/project/dossierstagiaire/persistence/DossierStagiaireDaoHibernateTest.java
 Missing ranges: 
/trunk/project/src/test/java/com/company/client/project/dossierstagiaire/persistence/DossierStagiaireDaoHibernateTest.java:6336-6389
   branches/project-dev/src/test/resources/log4j.properties
 Missing ranges:
/trunk/project/src/test/resources/log4j.properties:6336-6389

I really don't undertsand what has happened. The merge went well.
 


Well, let's look at what the error is saying:

So there are files in trunk/project from which you have not yet merged
changes into your branch. You have however merged changes to other
files from revisions 6336 through 6393 to your branch from trunk.

That is what's causing the error. r6336 to 6393 have not been completely
merged from trunk to the branch. The changes listed in the error message
are the changes which have not been merged into the branch yet.

This can easily happen if people do merges into shallow working copies,
with depth != infinity. Maybe your working copy on the Mac is shallow,
and you have done incomplete merges from trunk to the branch with it,
and as a result those merges weren't complete, causing reintegrate to
complain?

To illustrate, let's assume I make a commit to trunk in r50,
which affects the following files:

  /trunk/foo.c
  /trunk/bar/baz.c

Now I merge r50 from trunk to my branch, but the merge omits the change
to bar/baz.c because my branch working copy is shallow.
The mergeinfo created by this merge looks like this:

   /branch (svn:mergeinfo = trunk:r50*)
   /branch/foo.c (svn:mergeinfo = trunk:r50)

The * means "only applies to this folder, not its children".
This happens because svn realises that I did not merge changes r50
made inside of /trunk/bar/. Maybe I still want to merge those later.
Because the mergeinfo at /branch is not inheritable, svn also made
a note at /branch/foo.c saying "this file already has changes to r50".
This will prevent changes made in r50 to foo.c from being merged to
the branch again.

Trying to reintegrate the branch from this state without first merging
everything r50 did will result in the error you are getting.

You want mergeinfo like this:

   /branch (svn:mergeinfo = trunk:r50)

Which says "This entire branch has all changes made to trunk in r50".

BTW, a 1.6 client will flag a tree conflict in this case,
saying "local delete, incoming edit upon merge", because in my WC
it looks as if I deleted bar/ (though it should probably say "local
missing because of shallow working copy, incoming edit").
You proba

Re: Cannot reintegrate feature branch

[Stefan Sperling]

On Thu, May 06, 2010 at 01:36:04PM +0200, Stefan Sperling wrote:
> You want mergeinfo like this:
> 
>   /branch (svn:mergeinfo = trunk:r50)

Oh, and I'm not implying that you should modify the mergeinfo by hand.
Just do the merge from trunk to the branch again, but with a working
copy at depth infinity. This will make the branch pick up the missing changes.
Then try to reintegrate the branch again.

Stefan

RE: Trouble with authorization

[K F]

> From: K F [mailto:cmkfo...@yahoo.com] 
> Sent: 05 May 2010 20:43
> 
> The repo in on a Unix box located at svnrepo/sandbox 
> accessing via tortoise on a windows machine with the latest 
> releases. When I try to do a commit as user dev1, psswd dev1, 
> I get the following error:
>  
> Command: Commit 
> Error: Commit failed (details follow):  
> Error: Authorization failed  
> Finished!:   
>  
> I am not sure what is wrong. I did some searching on the web 
> and can't find anything wrong with what I am doing. Here is 
> what I have in the pertinent files.
>  
> passwd file:
> dev1 = dev1
> dev2 = dev2
> dev3 = dev3
>  
> authz file:
> [aliases]
>  
> [groups]
> deva = dev1, dev2
> devb = dev3
>  
> [svnrepo/sandbox:/]
> deva = rw
> devb = r

Personally I had some issues with using [groups] that I unfotunately did
not have time to resolve.  I suggest that you start by using the
usernames (dev1 etc) directly in the authz file to test:

Also, I think that [svnrepo/sandbox:/] is wrong.  I would only ever
expect to see one name before the slash (a specific repo in a parentpath
setup) then the path within the repo comes after the ":/".  

[sandbox:/]
dev1 = rw
dev2 = rw
dev3 = r

If you only have one repo / are not using parentpath then you can just
set the default global access level:

[/]
dev1 = rw
dev2 = rw
dev3 = r

Are you using parentpath in your setup?  Unless your client is 1.6.11+,
you need to grant read access to the root (you do seem to be doing that,
just thought it worth mentioning).

Finally, a link to path-based authorization in the nightly red book:
http://svnbook.red-bean.com/nightly/en/svn.serverconfig.pathbasedauthz.html


~ mark c

> svnserve.conf file:
> [general]
> anon-access=none
> auth-access=write
>  
> password-db=passwd
>  
> authz-db=authz
> 

Mark,

I looked at the link you offered for Path-Based Authorization and really didn't 
see anything that I haven't tried. Based on your suggestions, to get it to work 
I am not using groups and am simply using the usernames. 

[/]
dev1 = rw
dev2 = rw
dev3 = r

As you can see I am also using the global level access. This all seems to work. 
I would still like to try and get the groups to work if anyone has any other 
ideas.

Thanks,
Rich



  

RE: Trouble with authorization

[Cooke, Mark]

> > From: K F [mailto:cmkfo...@yahoo.com] 
> > Sent: 05 May 2010 20:43
> > 
> > The repo in on a Unix box located at svnrepo/sandbox 
> > accessing via tortoise on a windows machine with the latest 
> > releases. When I try to do a commit as user dev1, psswd dev1, 
> > I get the following error:
> >  
> > Command: Commit 
> > Error: Commit failed (details follow):  
> > Error: Authorization failed  
> > Finished!:   
> >  
> > I am not sure what is wrong. I did some searching on the web 
> > and can't find anything wrong with what I am doing. Here is 
> > what I have in the pertinent files.
> >  
> > passwd file:
> > dev1 = dev1
> > dev2 = dev2
> > dev3 = dev3
> >  
> > authz file:
> > [aliases]
> >  
> > [groups]
> > deva = dev1, dev2
> > devb = dev3
> >  
> > [svnrepo/sandbox:/]
> > deva = rw
> > devb = r
> 
> Personally I had some issues with using [groups] that I 
> unfotunately did
> not have time to resolve.  I suggest that you start by using the
> usernames (dev1 etc) directly in the authz file to test:
> 
> Also, I think that [svnrepo/sandbox:/] is wrong.  I would only ever
> expect to see one name before the slash (a specific repo in a 
> parentpath
> setup) then the path within the repo comes after the ":/".  
> 
> [sandbox:/]
> dev1 = rw
> dev2 = rw
> dev3 = r
> 
> If you only have one repo / are not using parentpath then you can just
> set the default global access level:
> 
> [/]
> dev1 = rw
> dev2 = rw
> dev3 = r
> 
> Are you using parentpath in your setup?  Unless your client 
> is 1.6.11+,
> you need to grant read access to the root (you do seem to be 
> doing that,
> just thought it worth mentioning).
> 
> Finally, a link to path-based authorization in the nightly red book:
>
http://svnbook.red-bean.com/nightly/en/svn.serverconfig.pathbasedauthz.h
tml 
> 
> 
> ~ mark c
> 
> > svnserve.conf file:
> > [general]
> > anon-access=none
> > auth-access=write
> >  
> > password-db=passwd
> >  
> > authz-db=authz
> > 

> From: K F [mailto:cmkfo...@yahoo.com] 
> Sent: 06 May 2010 13:36
> 
> Mark,
> 
> I looked at the link you offered for Path-Based Authorization 
> and really didn't see anything that I haven't tried. Based on 
> your suggestions, to get it to work I am not using groups and 
> am simply using the usernames. 
> 
> [/]
> dev1 = rw
> dev2 = rw
> dev3 = r
> 
> As you can see I am also using the global level access. This 
> all seems to work. I would still like to try and get the 
> groups to work if anyone has any other ideas.
> 
> Thanks,
> Rich
>
Dang!  I missed the obvious problem which is that according to the Red
Book link you need to prefix group names with '@' which gives:-

> authz file:
> [aliases]
>  
> [groups]
> deva = dev1, dev2
> devb = dev3
>  
> [svnrepo/sandbox:/]
> @deva = rw
> @devb = r

...let me know if it works!

(and for completeness: Aliases need to be prefixed by '&' which does
work for me)  Hmm, perhaps my problem with groups was trying to create
groups just of aliases e.g.

[aliases]
user1=joe90
user2=adameve
user3=spod

[groups]
devs=&user1, &user2
test=&user2, &user3

[/]
@devs = rw
@test = r

Can anyone else confirm if this should /does (not) work?

~ mark c

Re: I need help to restore my files from svn

[Ulrich Eckhardt]

On Wednesday 05 May 2010, frank wang wrote:
> [...]I try to commit the changes I got:
>
> Error  Working copy 'c:\work2\test\include' locked
> Erro Please execute the 'Cleanup' command.
>
> At the dos prompt I type: svn cleanup and then I got error message:
> svn: Error at entry 1 in entries file for 'test/include/codes': has
> invlaid node kind
>
> How can I fix this problem? Now I could not update or commit my code.

It seems that your working copy has become invalid is some kind. What you 
could do is to simply check out a new working copy, then copy over all files 
from the old one that contain changes (don't copy the .svn folders though!). 
Then, review the changes, because the changes from the old WC might be based 
on a different revision than the new working copy, so don't blindly assume 
things fit.

The question that remains is what broke the working copy. Typical candidates 
are tools that simply ignore that the .svn folders are read-only and hidden 
and still perform e.g. text replacements in there.

Uli

-- 
ML: http://subversion.tigris.org/mailing-list-guidelines.html
FAQ: http://subversion.tigris.org/faq.html
Docs: http://svnbook.red-bean.com/

Sator Laser GmbH, Fangdieckstraße 75a, 22547 Hamburg, Deutschland
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932

**
Sator Laser GmbH, Fangdieckstraße 75a, 22547 Hamburg, Deutschland
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932
**
   Visit our website at 
**
Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten 
bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen 
Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein 
sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, 
weitergeleitet, veröffentlicht oder anderweitig benutzt werden.
E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte 
Änderungen enthalten. Sator Laser GmbH ist für diese Folgen nicht 
verantwortlich.
**

Unable to commit files : Server sent unexpected return value (400 Bad Request) in response

[robert mena]

Hi,

I have a CentOS 5.4 with standard subversion + webdav access.  I am facing a
problem.  I can access the repository e checkout the files but when I try to
commit I get errors such as the example below

Some of selected resources were not committed.
RA layer request failed
svn: Commit failed (details follow):
svn: Server sent unexpected return value (400 Bad Request) in response to
MKACTIVITY request for
'/svn/repos/!svn/act/b7856539-4f3e-bc49-973e-2a56292a7f5d'

The client is Eclipse galileo sr2 with the subversion plugin.

Re: Cannot reintegrate feature branch

[Jean Seurin]

Hi Stefan,

unfortunately even with a fresh branch check out, it would not pick up 
the missing changes, that is the problem.
All our WC are at infinity by default, if I'm not mistaken, since we 
don't use sparse directories. So this can't have been the source of the 
error.


cheers
Jean

Stefan Sperling wrote:

On Thu, May 06, 2010 at 01:36:04PM +0200, Stefan Sperling wrote:
   

You want mergeinfo like this:

   /branch (svn:mergeinfo = trunk:r50)
 


Oh, and I'm not implying that you should modify the mergeinfo by hand.
Just do the merge from trunk to the branch again, but with a working
copy at depth infinity. This will make the branch pick up the missing changes.
Then try to reintegrate the branch again.

Stefan
   

which is better?

[west alto]

Hi,

Just a question.

I have a server with the following specs:

ESXi guest server
2 cpu
4 gig memory

Which is better option for running svn and apache, pre-fork or worker?


Thanks,


West

Re: Size of SVN Transaction vs Actual commit size

[Ravi Roy]

On Thu, May 6, 2010 at 3:37 PM, Ravi Roy  wrote:

> Hi
>
> General question about Transaction size versus actual file commit size. I
> am getting strange results when I am trying to commit 1.28 file and
> transaction size I am getting is 5538 bytes. Does somebody knows the mystery
> ?
>

   Sorry, Realised a mistake, please read 1.28 MB file.

>
> I expect transaction size to be the same as actual commit size ? or some
> compression in between ?
>
> Can somebody throw some light on this please?
>
> Thanks
>
> -RR
>
>
>