Re: Extrange commit error when add files to existing directory

[Joseba Ercilla Olabarri]

Looks like a permission misconfiguration in your file system, but is
difficult to confirm without more information about your installation...
Maybe you have a SELinux enabled?

_
Joseba
www.gailen.es

2011/4/4 

>
> Hi, I have a very extrange error with my subversion server, I use a linux
> server (fedora) to place de server. I can add a new folders on the
> repositories, and add any files to this recent created folders, also I can
> modify the files that previosly exists in any repository folder, but when I
> try to add a file (not another folder, just a simple file)  to one existing
> folder and make "commit" I receive the error: "Could not open the requested
> SVN  filesystem".
>
> Can anyone give me any  clue about how to fix this error?
>
> Thaks for your attention and sorry about my english.
>
>   --
>  Este mensaje se dirige exclusivamente al destinatario consignado. Puede
> contener información confidencial, de nuestra propiedad o legalmente
> protegida. Si usted no es el destinatario, le informamos que cualquier
> acceso, divulgación, copia o distribución de la información, así como
> cualquier acción u omisión realizada con base a la misma, queda prohibida y
> puede ser ilegal. En caso de haber recibido este mensaje por error, le
> rogamos que nos lo reenvíe y notifique inmediatamente, borrando toda copia
> de su sistema. Gracias.
>
> --
>
> *Comprometidos con la Responsabilidad 
> Social*.
> *No imprima si no es necesario*
> --
>  Francisco Fernández Cuadrado
> Departamento de Nuevas Tecnologías
> Agencia de Desarrollo Local
> C/ Astilleros, 4 , 03130 Santa Pola (Alicante)
> Tlf: 96 541 71 36 - Fax: 96 669 60 39
> www.adlsantapola.es
>
>
<><><>

RE: How to move my code to another SVN repo

[Cooke, Mark]

> -Original Message-
> From: richardcav...@mail.com [mailto:richardcav...@mail.com] 
> Sent: 06 April 2011 07:29
> To: users@subversion.apache.org
> Subject: How to move my code to another SVN repo
> 
> Hi, everyone.
> 
> I'm developing an open source Wikipedia bot. Currently it's hosted
> on an SVN repo that's on a guy's private computer. We'll say it's
> at blah.com. I don't control that computer and cannot log into it, 
> although I do have commit rights. Now that my code is good enough
> to post publicly, I want to host it on the SourceForge SVN repo 
> instead of this guy's private computer. Sourceforge says that the
> SVN repo (which is currently empty) can be checked out using this
> command:
> 
> svn co https://rcavellbot.svn.sourceforge.net/svnroot/rcavellbot
rcavellbot
> 
> Obviously I do not control SourceForge's servers. Is it possible
> for me to use svnsync to migrate blah.com's repo to SourceForge?
> If so, what svnsync command do I need to pull the entire repo from
> blah.com into SourceForge, and use the SourceForge repo for all
> future commits?  Obviously I want my local working directory to use
> SourceForge in future.
> 
> Richard

At Subversion Live they were talking about a new remote dump tool.
Google for svnrdump ~ it may be able to help you...

~ mark c

Re: svn pipe.

[Stephen Butler]

On Apr 6, 2011, at 8:29 , 胡专门 wrote:

> I want to pipe a specified version file to another file,like cvs –p
> cvs -p
>  Pipe the files retrieved from the repository to standard output, 
> rather than writing them in the current directory.  Available with the 
> checkout and update commands.
> but I cannot find the option,can you help me?

Try the "cat" subcommand.

svn cat TARGET[@REV]...

--
Stephen Butler | Senior Consultant
elego Software Solutions GmbH
Gustav-Meyer-Allee 25 | 13355 Berlin | Germany
fon: +49 30 2345 8696 | mobile: +49 163 25 45 015
fax: +49 30 2345 8695 | http://www.elegosoft.com
Geschäftsführer: Olaf Wagner | Sitz der Gesellschaft: Berlin
Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194

Re: opensuse repository

[Andy Levy]

On Wed, Apr 6, 2011 at 01:51, Stutz Oliver  wrote:
> Hey Guys,
>
> I'am trying to access
> https://build.opensuse.org/package/binaries?package=subversion&project=devel%3Atools%3Ascm%3Asvn&repository=SLE_11
>
> Is the site down?

You'll have to ask the OpenSuSE people what's going on with their server.

svn: PUT 403 Forbidden error

[Popa Bogdan]

Hey,

I have a new repository on a new server that uses CentOS and has CPanel for
management. Getting SVN to work with CPanel was a pain but now it works ok,
I can create repositories, I can checkout and I can see the repositories in
browser. I can even commit if I try from command line, on the server, as
root. The problem is that on my local working copy I get the following error
when I try to commit.

svn: Commit failed (details follow):
> svn: PUT of
> '/svn/testrepo/!svn/wrk/a9b6652a-2f01-0010-83aa-f9ff957523f6/index.php': 403
> Forbidden


The repository is owned by the apache user and it has the right permissions.
I've googled it for a while now and from what I can tell there is some
Allow/Deny directive in the CPanel generated apache config that generates
the 403 error.

The repositories are at
*/home/repos/ *
And I access them by:
*http://site.com/svn/repository*

So /home/repos/testrepo should match http://site.com/svn/stestrepo

-- 
Bogdan Popa
Sysadmin & Senior Developer



phone: +4 0753 096 904
e-mail: off...@becmedia.ro
web:http://www.becmedia.ro



Privileged/Confidential Information may be contained in this message. If you
are not in the addresses indicated in this message (or responsible for
delivery of the message to such person), you may not copy or deliver this
message to anyone. In such a case, you should destroy this message and
kindly notify the sender by reply e-mail.

Re: Build project in pre-commit

[Johan Corveleyn]

On Wed, Apr 6, 2011 at 1:05 AM, David Weintraub  wrote:
> On Tue, Apr 5, 2011 at 6:08 PM, San Martino  wrote:
>> we absolutely need to validate a project in the pre-commit trigger
>> with a build of the whole project being committed.
>>
>> Is this possible? Are there any tools allowing this?
>
> You can't really do it with a pre-commit script since the changes
> aren't part of the repository. (well, you can but it's a lot of work).
>
> The big problem is that your developers are sitting there twiddling
> their thumbs staring at a blank screen and unable to do any work while
> your application builds. Even a fast build takes a couple of minutes
> to complete.
>
> Your developers will hate Subversion, hate you, and hate their job.
> Well, they actually already may hate Subversion, you and their job,
> but this will make it even worse.
>
> May I recommend something like Jenkins? (http://jenkins-ci.org).
> Jenkins is a continuous build system that will do the build right
> after the developer does a commit. On a bad build, Jenkins can then
> mail the build results to the developer who did the commit and to the
> development team responsible for the project.
>
> Jenkins has a ton of plugins and can run unit tests, do deployments,
> run code check styles, coverage reports, you name it. It integrates
> with over 2 dozen defect tracking systems including Jira, and
> integrates with web-based version control browsers like Sventon,
> Fisheye, and ViewVC.
>
> Jenkins is webbased, but doesn't need Apache to run. It comes with its
> own application server built into the warfile. All you need is a JRE,
> and the Windows MSI file comes with that.

I also highly discourage performing builds in the pre-commit hook. It
will definitely take too long.

Another suggestion: we use IntelliJ IDEA (Java IDE) and TeamCity
(continuous build system). With this setup, there is a Teamcity
feature (which we can use from within the IDE) called "Pre-tested
commit". It allows you to perform a "remote build" on TeamCity with
your local changes integrated. If the build is successful, you can let
those changes be committed automatically (optionally, you can let it
ask you for confirmation first).

You can do this directly from a changed file or a changelist, or from
within the commit dialog. I have never used it myself, but I know it's
there :-). See here for more info:

http://confluence.jetbrains.net/display/TCD6/Pre-Tested+%28Delayed%29+Commit

I'm not sure if there is a way to enforce this centrally (as far as I
can see, it's up to the developer whether or not to perform a remote
build upon commit). But maybe it's good enough to have this as a
policy, and educate the developers to use this feature as standard
procedure ...

Cheers,
-- 
Johan

Re: Build project in pre-commit

[Daniel Shahaf]

Johan Corveleyn wrote on Wed, Apr 06, 2011 at 13:57:43 +0200:
> Another suggestion: we use IntelliJ IDEA (Java IDE) and TeamCity
> (continuous build system). With this setup, there is a Teamcity
> feature (which we can use from within the IDE) called "Pre-tested
> commit". It allows you to perform a "remote build" on TeamCity with
> your local changes integrated. If the build is successful, you can let
> those changes be committed automatically (optionally, you can let it
> ask you for confirmation first).

The procedure you just described embeds a race condition.  (someone
else's commit getting started after you started your remote building and
finishing before you commit)  What does TeamCity about it?

Re: Build project in pre-commit

[Johan Corveleyn]

On Wed, Apr 6, 2011 at 2:53 PM, Daniel Shahaf  wrote:
> Johan Corveleyn wrote on Wed, Apr 06, 2011 at 13:57:43 +0200:
>> Another suggestion: we use IntelliJ IDEA (Java IDE) and TeamCity
>> (continuous build system). With this setup, there is a Teamcity
>> feature (which we can use from within the IDE) called "Pre-tested
>> commit". It allows you to perform a "remote build" on TeamCity with
>> your local changes integrated. If the build is successful, you can let
>> those changes be committed automatically (optionally, you can let it
>> ask you for confirmation first).
>
> The procedure you just described embeds a race condition.  (someone
> else's commit getting started after you started your remote building and
> finishing before you commit)  What does TeamCity about it?

Hm, you're right. That must be the reason why I never used it ;-).

But you're right, just after I sent my mail I was thinking the same
(what would happen if someone else did a "pre-tested commit" (or just
a regular commit) at around the same time as my "remote build" is
running?). I guess TeamCity would just start my "remote build" with
the latest sources it has (checked out from version control (which
should be updated after every commit) at the time.

OTOH, the same problem would probably come up if you'd try to do this
in a pre-commit hook (unless someone decides to synchronize those
pre-commit-hook-builds, but wow, then it would be even more blocking
:)). And the same problem is also there if you ask your developers to
perform a private local build and set of unit tests before they
commit.

If I were to use this feature in my organisation, I guess I would
handle this pragmatically: there should still be an automatic
build+tests running on TeamCity (or whatever continuous build system)
running builds after every commit. This can catch any problems with
concurrent-commits after the fact ...

Cheers,
-- 
Johan

Re: Build project in pre-commit

[Daniel Shahaf]

Johan Corveleyn wrote on Wed, Apr 06, 2011 at 15:29:05 +0200:
> OTOH, the same problem would probably come up if you'd try to do this
> in a pre-commit hook (unless someone decides to synchronize those
> pre-commit-hook-builds, but wow, then it would be even more blocking
> :)).

True.  As to synchronizing them, one could ensure that no other commit
has snuck in behind his back if one required every commit to append
a line to a well-known file.

I should warn, though: by now I'm talking more as a mathematician
("What's possible") than as an admin ("What's recommended").

Re: How to move my code to another SVN repo

[Ryan Schmidt]

On Apr 6, 2011, at 01:28, richardcav...@mail.com wrote:

> I'm developing an open source Wikipedia bot. Currently it's hosted on an SVN 
> repo that's on a guy's private computer. We'll say it's at blah.com. I don't 
> control that computer and cannot log into it, although I do have commit 
> rights. Now that my code is good enough to post publicly, I want to host it 
> on the SourceForge SVN repo instead of this guy's private computer. 
> Sourceforge says that the SVN repo (which is currently empty) can be checked 
> out using this command:
> 
> svn co https://rcavellbot.svn.sourceforge.net/svnroot/rcavellbot rcavellbot
> 
> Obviously I do not control SourceForge's servers. Is it possible for me to 
> use svnsync to migrate blah.com's repo to SourceForge? If so, what svnsync 
> command do I need to pull the entire repo from blah.com into SourceForge, and 
> use the SourceForge repo for all future commits?  Obviously I want my local 
> working directory to use SourceForge in future.

Yes, you should be able to do that. You may need to first svnsync the current 
repository to a temporary repository on your local machine, then svnsync that 
temporary repository to SourceForge. Or you may be able to do it directly in 
one step. I don't remember exactly what steps I had to do when I migrated one 
of my repositories to Google Code a couple years ago.

RE: Build project in pre-commit

[SUMNER Andrew]

I totally agree.  I have just started using it for a PowerBuilder
project and it has worked very well.

-Original Message-
From: David Weintraub [mailto:qazw...@gmail.com] 
Sent: Wednesday, 6 April 2011 11:05
To: San Martino
Cc: users@subversion.apache.org
Subject: Re: Build project in pre-commit

On Tue, Apr 5, 2011 at 6:08 PM, San Martino  wrote:
> we absolutely need to validate a project in the pre-commit trigger
> with a build of the whole project being committed.
>
> Is this possible? Are there any tools allowing this?

You can't really do it with a pre-commit script since the changes
aren't part of the repository. (well, you can but it's a lot of work).

The big problem is that your developers are sitting there twiddling
their thumbs staring at a blank screen and unable to do any work while
your application builds. Even a fast build takes a couple of minutes
to complete.

Your developers will hate Subversion, hate you, and hate their job.
Well, they actually already may hate Subversion, you and their job,
but this will make it even worse.

May I recommend something like Jenkins? (http://jenkins-ci.org).
Jenkins is a continuous build system that will do the build right
after the developer does a commit. On a bad build, Jenkins can then
mail the build results to the developer who did the commit and to the
development team responsible for the project.

Jenkins has a ton of plugins and can run unit tests, do deployments,
run code check styles, coverage reports, you name it. It integrates
with over 2 dozen defect tracking systems including Jira, and
integrates with web-based version control browsers like Sventon,
Fisheye, and ViewVC.

Jenkins is webbased, but doesn't need Apache to run. It comes with its
own application server built into the warfile. All you need is a JRE,
and the Windows MSI file comes with that.


-- 
David Weintraub
qazw...@gmail.com
The information contained in this e-mail may be privileged and/or sensitive. It 
is intended for the addressee only and is not necessarily the official view or 
communication of the New Zealand Customs Service. If you are not the intended 
recipient you are asked to not disclose, copy, or make use of its contents. If 
received in error you are asked to destroy this e-mail and contact the sender 
immediately. Your assistance is appreciated.

Subversion question

[Danne, Ratnakar]

Hi,

We presently have subversion 1.4.4, planning to upgrade it to 1.6 soon. Could 
you let me know which one I need to download as there are same versions from 
CollabNet, Wandisco and SummerSoft.

How do I figure out which one we have it on the server.

Thanks,
Danne, Ratnakar
Technology Services
920-592-8345

The information contained in this e-mail is privileged and confidential, and 
for use only of the addressees of same and/or those who might have been 
specifically authorized to read it.  If you have received this e-mail by error, 
please destroy it and notify the sender, to his/her e-mail address.  Any 
non-authorized dissemination, distribution or reproduction of this message is 
strictly prohibited, and subject to the sanctions established in the applicable 
laws

RE: Subversion question

[Cooke, Mark]

> -Original Message-
> From: Danne, Ratnakar [mailto:dan...@schneider.com] 
> Sent: 06 April 2011 21:04
> To: users@subversion.apache.org
> Subject: Subversion question
> 
> Hi,
> 
> We presently have subversion 1.4.4, planning to upgrade it to 
> 1.6 soon. Could you let me know which one I need to download 
> as there are same versions from CollabNet, Wandisco and SummerSoft.

It would help if you told us a bit more about your current setup.  Are
you windows or *nix (if so, which flavour)?  Do you know how (& who)
subversion was originally installed (by)?

Subversion is now an apache project, so the first stop should be
http://subversion.apache.org/ where you will also find links to download
the source and some binary packages.  If apache do not host a suitable
binary package for you then a quick web search should help
(http://alagazam.net/ for windows for example).

> How do I figure out which one we have it on the server.

If you have console access to the server then the command:
`svnadmin --version` will tell you what version you have.

Reading the manual also helps: http://svnbook.red-bean.com/

~ mark c

> Thanks,
> 
> Danne, Ratnakar
> 
> Technology Services
>