Fair enough, the same pattern is still applicable. For example, in our
CVS repo what separated one "project" from another was basically a
root-level folder.
In kind, you could similarly use cvs2svn to "chunk/dump" subdirectories
at a time.
For example, if in CVS you have something like:
/Fo
2011/1/3 Pazmiño Mazón, Iván Andrés :
> Hello,
>
> I've moved some files (java classes) from a directory to another, and
> now commit fails complaining the containing folder doesn't exist
One of the things that trip many people up is that Subversion doesn't
know you've moved something until you te
On Jan 3, 2011, at 15:32, Pazmiño Mazón, Iván Andrés wrote:
> Nick wrote:
>
>> svn update on the client
>
> what do you mean? using the client instead of the ide?
Using whatever. Presumably if you're using an IDE that has Subversion support,
it will have a menu or button or something that wil
what do you mean? using the client instead of the ide?
-Original Message-
From: Nick
To: iapazm...@sri.gob.ec
Cc: users@subversion.apache.org
Subject: Re: Commit fails with path not found
Date: Mon, 03 Jan 2011 16:19:56 -0500
svn update on the client
"Clausula de Confidencialidad: La in
On Mon, 2011-01-03 at 16:18 -0500, Pazmiño Mazón, Iván Andrés wrote:
> I've moved some files (java classes) from a directory to another, and
> now commit fails complaining the containing folder doesn't exist
>
> svn: Commit failed (details follow):
> svn:
> '/svn/app-project/trunk/app-project-web/
On Mon, Jan 3, 2011 at 15:56, Nick wrote:
> On Mon, 2011-01-03 at 11:49 -0500, Mark Phippard wrote:
>> > Apologies in advance if this is covered somewhere, but can someone
>> > explain (or point me to some references on) why using SVN w/ Apache
>> > (HTTPS) is insecure? I've seen some references
Hello,
I've moved some files (java classes) from a directory to another, and
now commit fails complaining the containing folder doesn't exist
svn: Commit failed (details follow):
svn: '/svn/app-project/trunk/app-project-web/src/main/webapp/templates'
path not found: 404 Not Found (https://xxx)
T
On Mon, 2011-01-03 at 11:49 -0500, Mark Phippard wrote:
> > Apologies in advance if this is covered somewhere, but can someone
> > explain (or point me to some references on) why using SVN w/ Apache
> > (HTTPS) is insecure? I've seen some references to plain text
> password
> > storage, but I don'
On Mon, Jan 3, 2011 at 4:18 PM, Mark Phippard wrote:
> On Mon, Jan 3, 2011 at 10:13 AM, wrote:
>> Wow...for some reason I was under the impression that file level
>> restrictions didn't work...I really don't know why, but there it is.
>>
>> I don't suppose there's a way to use wild cards in the
a post-commit hook or a crontab coils update the file to keep the security
on newly created branches (top post a result of this stupid phone... sorry)
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype
On Mon, Jan 03, 2011 at 12:51:41PM -0500, Karl Fogel wrote:
> Due to some recent press releases and blog posts by WANdisco, Inc, the
> Apache Software Foundation has felt it necessary to post a response:
>
> https://blogs.apache.org/foundation/entry/apache_subversion_to_wandisco_1
>
> It basica
Due to some recent press releases and blog posts by WANdisco, Inc, the
Apache Software Foundation has felt it necessary to post a response:
https://blogs.apache.org/foundation/entry/apache_subversion_to_wandisco_1
It basically clarifies that WANdisco participates in Subversion
development the s
On Mon, Jan 3, 2011 at 11:09 AM, Nick wrote:
> On Sun, 2011-01-02 at 22:43 -0500, Nico Kadel-Garcia wrote:
>
>> It's possible to do secure Subversion. Use svn+ssh access, disable or
>> block other services at the firewall, and keep it away from HTTP/HTTPS
>> in order to prevent UNIx or Linux clien
On 1/2/2011 9:43 PM, Nico Kadel-Garcia wrote:
It's possible to do secure Subversion. Use svn+ssh access, disable or
block other services at the firewall,
If ssh is permitted and you didn't personally set it up, what are the
odds that port tunneling or ssh's built in socks proxy will allow acc
On Sun, 2011-01-02 at 22:43 -0500, Nico Kadel-Garcia wrote:
> It's possible to do secure Subversion. Use svn+ssh access, disable or
> block other services at the firewall, and keep it away from HTTP/HTTPS
> in order to prevent UNIx or Linux client plaintext password storage.
Apologies in advance
You've definitely given me enough to work off here, thanks!
Benjamin Ortega
-Original Message-
From: Mark Phippard [mailto:markp...@gmail.com]
Sent: Monday, January 03, 2011 9:18 AM
To: Ortega, Benjamin
Cc: users@subversion.apache.org
Subject: Re: On commit attempt, Server sent unexpe
On Mon, Jan 3, 2011 at 10:13 AM, wrote:
> Wow...for some reason I was under the impression that file level restrictions
> didn't work...I really don't know why, but there it is.
>
> I don't suppose there's a way to use wild cards in the path as well?
Wild-cards are not supported in authz.
If y
Wow...for some reason I was under the impression that file level restrictions
didn't work...I really don't know why, but there it is.
I don't suppose there's a way to use wild cards in the path as well? Like:
[repos:/folder/structure/*/RestrictedFile]
To allow for one entry restricting access
On Mon, Jan 3, 2011 at 9:55 AM, wrote:
> I suppose another fundamental question in all this -- Is there any other way
> to provide file level restrictions
> while using the svn authz file for authorization?
Can you explain why you cannot just add a rule to the file like this:
[repos:/folder/st
I suppose another fundamental question in all this -- Is there any other way to
provide file level restrictions while using the svn authz file for
authorization?
Benjamin Ortega
-Original Message-
From: benjamin.ort...@wellsfargo.com [mailto:benjamin.ort...@wellsfargo.com]
Sent: Mo
On Sat, Jan 01, 2011 at 12:30:23AM +0530, shirish शिरीष wrote:
> Hi all,
> This is going to be a long post and actually a repost of what I asked
> in Debian forum few days ago.
> http://forums.debian.net/viewtopic.php?f=10&t=58799 but got no answer.
>
> This is from svn version 1.6.12 .
>
>
> H
The /*/*/*/ in the path is to compensate for the temporary location
/!svn/ver//. This works without the svnauthz file in place.
Is there an internal user that the subversion server utilizes to perform the
checkout of the last-committed-revision of the file prior to the put? That
seems to be w
On Fri, Dec 31, 2010 at 11:04 AM, wrote:
> I'm trying to integrate a SVN Authz authorization file with apache
> configuration files to provide a solution for not just directory level
> restrictions, but also file level restrictions. It's my understanding that
> the SVN Authorization file is not c
Addition at bottom :-
2011/1/1 shirish शिरीष :
> Hi all,
> This is going to be a long post and actually a repost of what I asked
> in Debian forum few days ago.
> http://forums.debian.net/viewtopic.php?f=10&t=58799 but got no answer.
>
> This is from svn version 1.6.12 .
>
>
> Hi all,
> I am no
Hi all,
This is going to be a long post and actually a repost of what I asked
in Debian forum few days ago.
http://forums.debian.net/viewtopic.php?f=10&t=58799 but got no answer.
This is from svn version 1.6.12 .
Hi all,
I am no programmer, just a user who sometimes downloads svn snapshots
or t
I'm trying to integrate a SVN Authz authorization file with apache
configuration files to provide a solution for not just directory level
restrictions, but also file level restrictions. It's my understanding that the
SVN Authorization file is not capable of handling file-specific restrictions,
On Mon, Jan 3, 2011 at 14:16, Torsten Krah
wrote:
> Hi,
>
> ive got a large repository (using svn version 1.5.1 r32289) and want to dump
> the repository.
> Dumping with svnadmin dump $repo > dumpfile does result in:
>
> svnadmin: Can't write to stream: File too large
>
> The file at this time is
On Sat, Jan 01, 2011 at 11:58:09PM -0700, Philip Prindeville wrote:
> On 12/30/10 7:29 AM, Stefan Sperling wrote:
> >You may conveniently argue that you don't care about this problem
> >because it doesn't concern you. But Subversion developers cannot just
> >add options and functionality without co
On Sat, Jan 01, 2011 at 10:29:22PM -0500, Nico Kadel-Garcia wrote:
> You've just made my point that it should be automated upstream.
Instead of riding on the obvious shortcomings of a two-line shell
script I was using to badly illustrate an idea, why don't you spend
time writing up a "Setting up S
Hi,
ive got a large repository (using svn version 1.5.1 r32289) and want to dump
the repository.
Dumping with svnadmin dump $repo > dumpfile does result in:
svnadmin: Can't write to stream: File too large
The file at this time is around 17 GiB in size.
The only workaround found at the moment is
30 matches
Mail list logo
