Unsupervised svn import

2010-04-13 Thread Tom Van de Putte

Hey,

I need to do an unsupervised 'svn import' from within a php script run
in bash (so PHP CLI). The svn server runs on a different machine using
apache + webDAV.
I found that in previous versions (svn 1.2) that corresponding manual
indicates the use of --username and --password switches, but these have
diappeared since the 1.4 version.

Is there any reason for this, and or other means to do  an svn import
without user intervention?

Thanks in advance,
Tom Van de Putte


-- 
Met vriendelijke groet,
Tom Van de Putte  |  PHP/MySQL Developer

bSeen.be
Vlaanderenstraat 30/2
B-9000 Gent
Tel. +32 (0)9 331 55 50
Fax +32 (0)9 331 55 51
BE 0473.071.275
Mail: t...@bseen.be
URL: www.bSeen.be

bSeen blogt...
Volg ons op www.bseen.be/blog


Re: Unsupervised svn import

2010-04-13 Thread Volker Kopetzky
Hi Tom,

svn version 1.6.5 supports them, at least in the CLI client.
'svn help ci' documents these options, I'm using them in my own bash importer 
script:

Global options:
  --username ARG   : specify a username ARG
  --password ARG   : specify a password ARG
  --non-interactive: do no interactive prompting


...works smoothely in versions 1.6.x and 1.5.5.

Dunno if they are available in subversion's PHP API, though :-D

Beste Grüße,
kind regards,
Volker Kopetzky
vzk Beratung
Germany & Thailand

phone +49.6809.2163.30
phone +66.86.143.77.27
skype volker.kopetzky
email v...@vzkb.de
wsite http://www.vzkb.de

Am 13.04.2010 um 14:12 schrieb Tom Van de Putte:


Hey,

I need to do an unsupervised 'svn import' from within a php script run
in bash (so PHP CLI). The svn server runs on a different machine using
apache + webDAV.
I found that in previous versions (svn 1.2) that corresponding manual
indicates the use of --username and --password switches, but these have
diappeared since the 1.4 version.

Is there any reason for this, and or other means to do  an svn import
without user intervention?

Thanks in advance,
Tom Van de Putte


-- 
Met vriendelijke groet,
Tom Van de Putte  |  PHP/MySQL Developer

bSeen.be
Vlaanderenstraat 30/2
B-9000 Gent
Tel. +32 (0)9 331 55 50
Fax +32 (0)9 331 55 51
BE 0473.071.275
Mail: t...@bseen.be
URL: www.bSeen.be

bSeen blogt...
Volg ons op www.bseen.be/blog



Re: Automatic upgrade of wc format annoying on shared drives

2010-04-13 Thread Daniel Shahaf
Simon wrote on Tue, 13 Apr 2010 at 01:17 -:
> I think correct behaviour here is that the client should at least
> prompt the user to ask if it should upgrade the wc metadata format
> before messing with the working copy.
> 
> Failing that, is there some way of locking a working copy to
> a particular version of the wc metadata format.

Subversion 1.7 will require explicit user action to upgrade a wc.

% svn info wc1\trunk
..\..\..\subversion\libsvn_wc\upgrade.c:1086: (apr_err=155036)
svn: Working copy format of 'C:\tmp\svn\wc1\trunk' is too old (10); please run 
'svn upgrade'



Server-side enforcement of SVN properties

2010-04-13 Thread Leonid Zeitlin

Hello all,
I have a Subversion server and a bunch of Windows clients accessing it 
with TortoiseSVN via http protocol (Apache mod_dav_svn). I want a 
certain Subversion property (namely, svn:needs-lock) to be set on all 
new files with certain extension. I know this can be done with 
auto-props settings in SVN clients. But is there a way to enforce this 
centrally, on the server, so that these properties are set regardless of 
client configuration?


Thanks a lot,
  Leonid



RE: Server-side enforcement of SVN properties

2010-04-13 Thread Giulio Troccoli
>


Linedata Services (UK) Ltd
Registered Office: Bishopsgate Court, 4-12 Norton Folgate, London, E1 6DB
Registered in England and Wales No 3027851VAT Reg No 778499447

-Original Message-


> From: Leonid Zeitlin [mailto:l...@csltd.com.ua]
> Sent: 13 April 2010 10:03
> To: users@subversion.apache.org
> Subject: Server-side enforcement of SVN properties
>
> Hello all,
> I have a Subversion server and a bunch of Windows clients
> accessing it with TortoiseSVN via http protocol (Apache
> mod_dav_svn). I want a certain Subversion property (namely,
> svn:needs-lock) to be set on all new files with certain
> extension. I know this can be done with auto-props settings
> in SVN clients. But is there a way to enforce this centrally,
> on the server, so that these properties are set regardless of
> client configuration?
>
> Thanks a lot,
>Leonid
>

No, but you can write a pre-commit hook that rejects new files without the 
property set and maybe redirect your user to a wiki or something similar where 
you explain how to setup auto-prop.

G


Re: Server-side enforcement of SVN properties

2010-04-13 Thread Leonid Zeitlin

On 13.04.2010 12:07, Giulio Troccoli wrote:





Linedata Services (UK) Ltd
Registered Office: Bishopsgate Court, 4-12 Norton Folgate, London, E1 6DB
Registered in England and Wales No 3027851VAT Reg No 778499447

-Original Message-



From: Leonid Zeitlin [mailto:l...@csltd.com.ua]
Sent: 13 April 2010 10:03
To: users@subversion.apache.org
Subject: Server-side enforcement of SVN properties

Hello all,
I have a Subversion server and a bunch of Windows clients
accessing it with TortoiseSVN via http protocol (Apache
mod_dav_svn). I want a certain Subversion property (namely,
svn:needs-lock) to be set on all new files with certain
extension. I know this can be done with auto-props settings
in SVN clients. But is there a way to enforce this centrally,
on the server, so that these properties are set regardless of
client configuration?

Thanks a lot,
Leonid



No, but you can write a pre-commit hook that rejects new files without the 
property set and maybe redirect your user to a wiki or something similar where 
you explain how to setup auto-prop.

G



Thank you. Any sample of such pre-commit hook I can start from?

Thanks,
  Leonid



Re: Automatic upgrade of wc format annoying on shared drives

2010-04-13 Thread Simon
On 13/04/2010, at 18:46 , Daniel Shahaf d.s-at-daniel.shahaf.name | 
subversion users list| wrote:



Simon wrote on Tue, 13 Apr 2010 at 01:17 -:

I think correct behaviour here is that the client should at least
prompt the user to ask if it should upgrade the wc metadata format
before messing with the working copy.

Failing that, is there some way of locking a working copy to
a particular version of the wc metadata format.


Subversion 1.7 will require explicit user action to upgrade a wc.

% svn info wc1\trunk
...\..\..\subversion\libsvn_wc\upgrade.c:1086: (apr_err=155036)
svn: Working copy format of 'C:\tmp\svn\wc1\trunk' is too old (10);  
please run 'svn upgrade'




That's great. Thanks for the info.

Simon

cannot break lock due to no matching lock-token

2010-04-13 Thread Tom Jones
A file was created and locked.  The file was unlocked and the project tagged.

the tagged folder was merged with an empty trunk and then the trunk checked 
out.  A file in the project was locked, but later removed without being 
unlocked.  Now the file does not exist in the trunk, but any changes to the 
trunk cannot commit because "cannot verify lock on path...  ; no matching lock- 
token available.  If you wish to break the lock, use the 'Check for 
Modification' dialog" appears and prevents any actions on the trunk (ie, delete 
all files).  I have tried checking for modifications but none are listed (the 
file was deleted).

I cannot merge, delete, copy or anything.  The lock that was there is not 
needed.  How do I remove this lock-token or whatever I need to do?


Tom Jones
Woodward Governor Co.
Turbine Systems (Test Engineering)


P Please consider the environment before printing this email.



***
The information in this e-mail is confidential and intended solely for the 
individual or entity to whom it is addressed.  If you have received this e-mail 
in error please notify the sender by return e-mail delete this e-mail and 
refrain from any disclosure or action based on the information.
***


RE: Automatic upgrade of wc format annoying on shared drives

2010-04-13 Thread Jeremy Mordkoff
> Jeremy Mordkoff wrote:
> > I second that. I support fedora 7, 8, 9, 10, 11 (and soon 12),
various
> > ubuntu releases, plus windows XP, Vista, and Win7, and Mac OS 10.4,
> > 10.5. When one of them upgrades, it causes me to scramble to build
and
> > deploy upgrades to the others.
> >
> 
> But working copies should really be disposable.  As long as you keep
your
> changes commited, if the format is a problem for a different client,
just delete
> it and let that client build what it wants.
> 
> --
>Les Mikesell
> lesmikes...@gmail.com

Our product also supports that variety of platforms. I request that
changes be tested on all platforms before the changes are committed.
That requires the engineer to either use a project branch or access a
view from multiple machines. Since some machines are shared, sometimes
views get inadvertently upgraded.

Thanks Daniel.

JLM


Re: Automatic upgrade of wc format annoying on shared drives

2010-04-13 Thread Les Mikesell

Jeremy Mordkoff wrote:


I second that. I support fedora 7, 8, 9, 10, 11 (and soon 12),

various

ubuntu releases, plus windows XP, Vista, and Win7, and Mac OS 10.4,
10.5. When one of them upgrades, it causes me to scramble to build

and

deploy upgrades to the others.


But working copies should really be disposable.  As long as you keep

your

changes commited, if the format is a problem for a different client,

just delete

it and let that client build what it wants.



Our product also supports that variety of platforms. I request that
changes be tested on all platforms before the changes are committed.
That requires the engineer to either use a project branch or access a
view from multiple machines. Since some machines are shared, sometimes
views get inadvertently upgraded.



And you are not concerned that some uncommitted change in this working copy 
might be the thing that makes all your tests pass?  I like to make 'svn 
checkout' or 'update' the only means to get the source to the testing platforms 
to ensure that the test is of a reproducible state.


--
  Les Mikesell
   lesmikes...@gmail.com



RE: Automatic upgrade of wc format annoying on shared drives

2010-04-13 Thread Jeremy Mordkoff
Jeremy Mordkoff wrote:

>>> I second that. I support fedora 7, 8, 9, 10, 11 (and soon 12),
> various
>>> ubuntu releases, plus windows XP, Vista, and Win7, and Mac OS 10.4,
>>> 10.5. When one of them upgrades, it causes me to scramble to build
> and
>>> deploy upgrades to the others.
>>>
>> But working copies should really be disposable.  As long as you keep
> your
>> changes commited, if the format is a problem for a different client,
> just delete
>> it and let that client build what it wants.
>>
> 
> Our product also supports that variety of platforms. I request that
> changes be tested on all platforms before the changes are committed.
> That requires the engineer to either use a project branch or access a
> view from multiple machines. Since some machines are shared, sometimes
> views get inadvertently upgraded.
> 

And you are not concerned that some uncommitted change in this working copy 
might be the thing that makes all your tests pass?  I like to make 'svn 
checkout' or 'update' the only means to get the source to the testing platforms 
to ensure that the test is of a reproducible state.

-- 
   Les Mikesell
lesmikes...@gmail.com


Absolutely. We use svn:ignore and svn status to make it easy to make sure such 
things don't happen. And then we also have a QA group (this is for developer 
testing). I can't say they always adhere to it, but that can't say that 
their tools don't support it. 

jlm


Re: Server-side enforcement of SVN properties

2010-04-13 Thread David Weintraub
You can take a look at my pre-commit hook at
http://dl.dropbox.com/u/433257/hooks.zip.

This allows you to enforce commit privileges (including the ability to
create, but not edit tags), properties, and file names.

It's written in Perl and needs the Config::IniFile module.

2010/4/13 Leonid Zeitlin 

> On 13.04.2010 12:07, Giulio Troccoli wrote:
>
>>
>>>
>>
>> Linedata Services (UK) Ltd
>> Registered Office: Bishopsgate Court, 4-12 Norton Folgate, London, E1 6DB
>> Registered in England and Wales No 3027851VAT Reg No 778499447
>>
>> -Original Message-
>>
>>
>>  From: Leonid Zeitlin [mailto:l...@csltd.com.ua]
>>> Sent: 13 April 2010 10:03
>>> To: users@subversion.apache.org
>>> Subject: Server-side enforcement of SVN properties
>>>
>>> Hello all,
>>> I have a Subversion server and a bunch of Windows clients
>>> accessing it with TortoiseSVN via http protocol (Apache
>>> mod_dav_svn). I want a certain Subversion property (namely,
>>> svn:needs-lock) to be set on all new files with certain
>>> extension. I know this can be done with auto-props settings
>>> in SVN clients. But is there a way to enforce this centrally,
>>> on the server, so that these properties are set regardless of
>>> client configuration?
>>>
>>> Thanks a lot,
>>>Leonid
>>>
>>>
>> No, but you can write a pre-commit hook that rejects new files without the
>> property set and maybe redirect your user to a wiki or something similar
>> where you explain how to setup auto-prop.
>>
>> G
>>
>>
> Thank you. Any sample of such pre-commit hook I can start from?
>
> Thanks,
>  Leonid
>
>


-- 
David Weintraub
qazw...@gmail.com


Re: Server-side enforcement of SVN properties

2010-04-13 Thread Leonid Zeitlin

Thank you!

  Leonid

On 13.04.2010 20:00, David Weintraub wrote:

You can take a look at my pre-commit hook at
http://dl.dropbox.com/u/433257/hooks.zip.

This allows you to enforce commit privileges (including the ability to
create, but not edit tags), properties, and file names.

It's written in Perl and needs the Config::IniFile module.

2010/4/13 Leonid Zeitlin mailto:l...@csltd.com.ua>>

On 13.04.2010 12:07, Giulio Troccoli wrote:




Linedata Services (UK) Ltd
Registered Office: Bishopsgate Court, 4-12 Norton Folgate,
London, E1 6DB
Registered in England and Wales No 3027851VAT Reg No 778499447

-Original Message-


From: Leonid Zeitlin [mailto:l...@csltd.com.ua
]
Sent: 13 April 2010 10:03
To: users@subversion.apache.org

Subject: Server-side enforcement of SVN properties

Hello all,
I have a Subversion server and a bunch of Windows clients
accessing it with TortoiseSVN via http protocol (Apache
mod_dav_svn). I want a certain Subversion property (namely,
svn:needs-lock) to be set on all new files with certain
extension. I know this can be done with auto-props settings
in SVN clients. But is there a way to enforce this centrally,
on the server, so that these properties are set regardless of
client configuration?

Thanks a lot,
Leonid


No, but you can write a pre-commit hook that rejects new files
without the property set and maybe redirect your user to a wiki
or something similar where you explain how to setup auto-prop.

G


Thank you. Any sample of such pre-commit hook I can start from?

Thanks,
  Leonid




--
David Weintraub
qazw...@gmail.com 




Is there a simple log/diff frontend (like gitk)?

2010-04-13 Thread Thomas Allen
Hello everyone,

One thing that I took for granted when doing all of my development in
Git was the always-reliable gitk which provides cross-platform log and
diff browsing. I'm sure it does more, but those were the main things I
used it for.

I am now working with a Subversion repository. Maybe I have not yet
mastered the "log" command, but  I find the output of the following
two commands to be confusing:

$ svn log -r HEAD

r3617 | tallen | 2010-04-12 15:57:35 -0400 (Mon, 12 Apr 2010) | 1 line

full comments + jslint fixes

$ svn log | grep tallen # outputs nothing

In general it would be very nice to have a tool to facilitate browsing
recent revisions and their diffs; I do not need it to help with
committing my changes or anything along those lines.

So, does anybody know of a simple, cross-platform, open-source
Subversion browser? I am on a Mac, and it seems that the only options
are proprietary and heavy, such as Versions and CornerStone...

Thomas Allen


RE: Is there a simple log/diff frontend (like gitk)?

2010-04-13 Thread Bob Archer

> So, does anybody know of a simple, cross-platform, open-source
> Subversion browser? I am on a Mac, and it seems that the only options
> are proprietary and heavy, such as Versions and CornerStone...
> 
> Thomas Allen

you might want to look at Subclispe http://subclipse.tigris.org/

and Rapid SVN http://rapidsvn.tigris.org/

BOb



Re: How to recover from "Found malformed header in revision file"?

2010-04-13 Thread Stonebraker
Any update on this?  Did svnsync fix your issue?

I am receiving the same error when trying to dump a 46 gb repo
* Dumped revision 1703.
* Dumped revision 1704.
* Dumped revision 1705.
svnadmin: Malformed representation header

svnhotcopy only copies about 6gb of the repo!

(I am using version 1.4.0 (r21228))


Any ideas?  I was thinking about trying svnsync but there is a bug in
that version where i cannot do svnsync over https without accepting
the certificate every time.

On Mar 8, 12:25 pm, Steven Roussey  wrote:
> I can do a full checkout at the moment. Too bad I can't go from that
> and create a new repo. Anyhow, the svnsync idea is a good one, and
> I'll have to give that a try. Thanks!
>
> Steven Roussey
> Network54 Corp.
>
> 2010/3/3 Mariusz Droździel :
>
> > On 4 March 2010 03:24, Steven Roussey  wrote:
>
> >> I also tried svnadmin recover which did not work, and fsfsverify.py. I 
> >> have a
> >> few working copies around that are ok (I think) -- is there a way to use 
> >> that to
> >> fix the repository?
>
> > Check out "Corrupted FSFS commit" and "Broken Revision in FSFS Repo"
> > threads from few days ago. I think me and Martin had very similiar
> > problem and solved it out with svnsync + access control over webdav.
>
> > --
> > Mariusz Drozdziel
>
>


Re: How to recover from "Found malformed header in revision file"?

2010-04-13 Thread Stonebraker
I tried using svnsync because i receive the malformed header error
when attempting to dump my repo.  Svnsync fails after eight revisions

(SVN version 1.4.0 (r21228))

Console output:
...
Committed revision 8.
Copied properties for revision 8.
Committed revision 9.
Copied properties for revision 9.
svnsync: REPORT request failed on 'https://'
svnsync: REPORT of 'https://': 200 OK (https://)


On Apr 13, 1:05 pm, Stonebraker  wrote:
> Any update on this?  Did svnsync fix your issue?
>
> I am receiving the same error when trying to dump a 46 gb repo
> * Dumped revision 1703.
> * Dumped revision 1704.
> * Dumped revision 1705.
> svnadmin: Malformed representation header
>
> svnhotcopy only copies about 6gb of the repo!
>
> (I am using version 1.4.0 (r21228))
>
> Any ideas?  I was thinking about trying svnsync but there is a bug in
> that version where i cannot do svnsync over https without accepting
> the certificate every time.
>
> On Mar 8, 12:25 pm, Steven Roussey  wrote:
>
> > I can do a full checkout at the moment. Too bad I can't go from that
> > and create a new repo. Anyhow, the svnsync idea is a good one, and
> > I'll have to give that a try. Thanks!
>
> > Steven Roussey
> > Network54 Corp.
>
> > 2010/3/3 Mariusz Dro¼dziel :
>
> > > On 4 March 2010 03:24, Steven Roussey  wrote:
>
> > >> I also tried svnadmin recover which did not work, and fsfsverify.py. I 
> > >> have a
> > >> few working copies around that are ok (I think) -- is there a way to use 
> > >> that to
> > >> fix the repository?
>
> > > Check out "Corrupted FSFS commit" and "Broken Revision in FSFS Repo"
> > > threads from few days ago. I think me and Martin had very similiar
> > > problem and solved it out with svnsync + access control over webdav.
>
> > > --
> > > Mariusz Drozdziel
>
>


Re: Is there a simple log/diff frontend (like gitk)?

2010-04-13 Thread Les Mikesell

On 4/13/2010 12:32 PM, Thomas Allen wrote:

Hello everyone,

One thing that I took for granted when doing all of my development in
Git was the always-reliable gitk which provides cross-platform log and
diff browsing. I'm sure it does more, but those were the main things I
used it for.

I am now working with a Subversion repository. Maybe I have not yet
mastered the "log" command, but  I find the output of the following
two commands to be confusing:

$ svn log -r HEAD

r3617 | tallen | 2010-04-12 15:57:35 -0400 (Mon, 12 Apr 2010) | 1 line

full comments + jslint fixes

$ svn log | grep tallen # outputs nothing

In general it would be very nice to have a tool to facilitate browsing
recent revisions and their diffs; I do not need it to help with
committing my changes or anything along those lines.

So, does anybody know of a simple, cross-platform, open-source
Subversion browser? I am on a Mac, and it seems that the only options
are proprietary and heavy, such as Versions and CornerStone...


If you mean cross-platform in the sense that you can use browsers from 
different platforms simultaneously, you might like a web front end like 
viewvc.


--
  Les Mikesell
   lesmikes...@gmail.com


Re: Is there a simple log/diff frontend (like gitk)?

2010-04-13 Thread Pablo Beltran
If you mean web front end then try www.svnflash.com. It's not open source
but it's free for non-profit or open source projects.
The major advantages of SVNFlash are its awesome user interface and revision
graphs (whole history) of files and projects.

Look at the live demo and explore the Apache Repository at real time:

http://svnflash.com/index.php/live-demo

Pablo.

2010/4/13 Thomas Allen 

> Hello everyone,
>
> One thing that I took for granted when doing all of my development in
> Git was the always-reliable gitk which provides cross-platform log and
> diff browsing. I'm sure it does more, but those were the main things I
> used it for.
>
> I am now working with a Subversion repository. Maybe I have not yet
> mastered the "log" command, but  I find the output of the following
> two commands to be confusing:
>
> $ svn log -r HEAD
> 
> r3617 | tallen | 2010-04-12 15:57:35 -0400 (Mon, 12 Apr 2010) | 1 line
>
> full comments + jslint fixes
> 
> $ svn log | grep tallen # outputs nothing
>
> In general it would be very nice to have a tool to facilitate browsing
> recent revisions and their diffs; I do not need it to help with
> committing my changes or anything along those lines.
>
> So, does anybody know of a simple, cross-platform, open-source
> Subversion browser? I am on a Mac, and it seems that the only options
> are proprietary and heavy, such as Versions and CornerStone...
>
> Thomas Allen
>


Re: Is there a simple log/diff frontend (like gitk)?

2010-04-13 Thread Ryan Schmidt

On Apr 13, 2010, at 12:32, Thomas Allen wrote:

> Maybe I have not yet
> mastered the "log" command, but  I find the output of the following
> two commands to be confusing:
> 
> $ svn log -r HEAD
> 
> r3617 | tallen | 2010-04-12 15:57:35 -0400 (Mon, 12 Apr 2010) | 1 line
> 
> full comments + jslint fixes
> 
> $ svn log | grep tallen # outputs nothing

Probably your working is not up to date. "svn up" before running "svn log" 
would probably work.



Unable to checkout files: Can't open file: Permission denied

2010-04-13 Thread Disc Magnet
This is my configuration.


  DAV svn
  SVNParentPath /home/magnet/myrepository/


The checkout command runs fine:

svn co http://localhost/myrepository/hachumachu

However, the commit command results in this error:

mag...@faku:~/hachumachu$ svn commit -m "Additional line"
svn: Commit failed (details follow):
svn: Can't open file
'/home/magnet/myrepository/hachumachu/db/txn-current-lock': Permission
denied

This appears in my Apache error log:

[Wed Apr 14 01:04:58 2010] [error] [client 127.0.1.1] Could not create
activity /myrepository/hachumachu/!svn/act/a3cb143e-3098-499b-b7d1-5d5b7e982881.
 [500, #0]
[Wed Apr 14 01:04:58 2010] [error] [client 127.0.1.1] could not begin
a transaction  [500, #13]
[Wed Apr 14 01:04:58 2010] [error] [client 127.0.1.1] Can't open file
'/home/magnet/myrepository/hachumachu/db/txn-current-lock': Permission
denied  [500, #13]

In case you want to see the permissions on the folders.

mag...@faku:~/myrepository$ ls -l
total 12
drwxr-xr-x 4 magnet magnet 4096 2010-04-11 18:13 ondalabondala
drwxr-xr-x 6 magnet magnet 4096 2010-04-11 18:12 hachumachu
drwxr-xr-x 6 magnet magnet 4096 2010-04-11 19:36 haggupaggu

Please help.


Free Online Subversion Training

2010-04-13 Thread Elaine
Provider of Enterprise Subversion Products is Sponsoring a Series of
Free Subversion Training Courses

San Ramon, CA April 13, 2010 – WANdisco, a leading provider of
infrastructure software for replication, scalability and high
availability, and a corporate sponsor of the Subversion open source
project with core developers from the project on staff, today
announced that it will begin sponsoring a series of free one hour
online Subversion training sessions on a bi-weekly basis later this
month.

The first course in the series, Branching and Merging in Subversion
1.6.9 will take place on Wednesday, April 21, 2010. This course will
cover everything from branching and merging basics to best practices.
The second course in the series, Introduction to Subversion for
Developers will take place on Wednesday, May 5, 2010. Subversion’s
architecture and design principles will be covered and attendees will
be introduced to using Subversion for software development.

Free Registration for Branching and Merging in Subversion 1.6.9 is
available at:
https://www2.gotomeeting.com/register/173903354.

Free Registration for Introduction to Subversion for Developers is
available at:
https://www2.gotomeeting.com/register/342584395.
WANdisco Certified Subversion Binaries Now Available for Free Download

As part of its participation in the Subversion project, WANdisco
offers free downloads of certified Subversion binaries that provide a
complete, fully tested version of Subversion based on the most recent
stable release. WANdisco's core Subversion developers are backed by
dedicated QA and support professionals that enable the company to
deliver the highest quality version of the software.

Download WANdisco’s certified Subversion binaries at:
http://www.wandisco.com/subversion/os/downloads.

WANdisco Enterprise-Class Subversion Support Services Now Available

In addition to free community support for Subversion, WANdisco offers
enterprise-class Subversion support for organizations that require the
guaranteed response times, 24-by-7 access to online and phone support,
automated delivery of the latest fixes and upgrades and other benefits
that typically come with a commercial software vendor's support
contract. Learn more about WANdisco’s Subversion support services at:
http://www.wandisco.com/products/svn/support.php.
Recent News and Resources

Free Download: Subversion Open Source:
http://www.wandisco.com/subversion/os/downloads

Subversion Professional Support:
http://www.wandisco.com/products/svn/support.php

WANdisco Subversion Enterprise:
http://www.wandisco.com/subversion


Re: Unable to checkout files: Can't open file: Permission denied

2010-04-13 Thread Erik Andersson
The user running apache needs write access to your repository.

Cheers / Erik

On Tue, Apr 13, 2010 at 10:01 PM, Disc Magnet  wrote:

> This is my configuration.
>
> 
>  DAV svn
>  SVNParentPath /home/magnet/myrepository/
> 
>
> The checkout command runs fine:
>
> svn co http://localhost/myrepository/hachumachu
>
> However, the commit command results in this error:
>
> mag...@faku:~/hachumachu$ svn commit -m "Additional line"
> svn: Commit failed (details follow):
> svn: Can't open file
> '/home/magnet/myrepository/hachumachu/db/txn-current-lock': Permission
> denied
>
> This appears in my Apache error log:
>
> [Wed Apr 14 01:04:58 2010] [error] [client 127.0.1.1] Could not create
> activity
> /myrepository/hachumachu/!svn/act/a3cb143e-3098-499b-b7d1-5d5b7e982881.
>  [500, #0]
> [Wed Apr 14 01:04:58 2010] [error] [client 127.0.1.1] could not begin
> a transaction  [500, #13]
> [Wed Apr 14 01:04:58 2010] [error] [client 127.0.1.1] Can't open file
> '/home/magnet/myrepository/hachumachu/db/txn-current-lock': Permission
> denied  [500, #13]
>
> In case you want to see the permissions on the folders.
>
> mag...@faku:~/myrepository$ ls -l
> total 12
> drwxr-xr-x 4 magnet magnet 4096 2010-04-11 18:13 ondalabondala
> drwxr-xr-x 6 magnet magnet 4096 2010-04-11 18:12 hachumachu
> drwxr-xr-x 6 magnet magnet 4096 2010-04-11 19:36 haggupaggu
>
> Please help.
>


Re: Unable to checkout files: Can't open file: Permission denied

2010-04-13 Thread Disc Magnet
I did that. I ran these two commands.

chgrp -R www-data myrepository
chown -R 770 myrepository

Now, I get this error:

$ svn commit -m "Updating"
svn: Commit failed (details follow):
svn: Could not open the requested SVN filesystem

Please help.

On Wed, Apr 14, 2010 at 1:59 AM, Erik Andersson  wrote:
> The user running apache needs write access to your repository.
> Cheers / Erik
>
> On Tue, Apr 13, 2010 at 10:01 PM, Disc Magnet  wrote:
>>
>> This is my configuration.
>>
>> 
>>  DAV svn
>>  SVNParentPath /home/magnet/myrepository/
>> 
>>
>> The checkout command runs fine:
>>
>> svn co http://localhost/myrepository/hachumachu
>>
>> However, the commit command results in this error:
>>
>> mag...@faku:~/hachumachu$ svn commit -m "Additional line"
>> svn: Commit failed (details follow):
>> svn: Can't open file
>> '/home/magnet/myrepository/hachumachu/db/txn-current-lock': Permission
>> denied
>>
>> This appears in my Apache error log:
>>
>> [Wed Apr 14 01:04:58 2010] [error] [client 127.0.1.1] Could not create
>> activity
>> /myrepository/hachumachu/!svn/act/a3cb143e-3098-499b-b7d1-5d5b7e982881.
>>  [500, #0]
>> [Wed Apr 14 01:04:58 2010] [error] [client 127.0.1.1] could not begin
>> a transaction  [500, #13]
>> [Wed Apr 14 01:04:58 2010] [error] [client 127.0.1.1] Can't open file
>> '/home/magnet/myrepository/hachumachu/db/txn-current-lock': Permission
>> denied  [500, #13]
>>
>> In case you want to see the permissions on the folders.
>>
>> mag...@faku:~/myrepository$ ls -l
>> total 12
>> drwxr-xr-x 4 magnet magnet 4096 2010-04-11 18:13 ondalabondala
>> drwxr-xr-x 6 magnet magnet 4096 2010-04-11 18:12 hachumachu
>> drwxr-xr-x 6 magnet magnet 4096 2010-04-11 19:36 haggupaggu
>>
>> Please help.
>
>


Re: Unable to checkout files: Can't open file: Permission denied

2010-04-13 Thread David Bartmess

On 4/13/2010 3:27 PM, Disc Magnet wrote:

I did that. I ran these two commands.

chgrp -R www-data myrepository
chown -R 770 myrepository

Now, I get this error:

$ svn commit -m "Updating"
svn: Commit failed (details follow):
svn: Could not open the requested SVN filesystem

Please help.
   


Probably your http server isn't pointing to the correct path.
Check your Location in the httpd.conf

i.e.,


SVNPath /home/magnet/myrepository



--
"Dingo" Dave Bartmess
Broomfield, CO. USA
http://edingo.net




Re: Unable to checkout files: Can't open file: Permission denied

2010-04-13 Thread Ryan Schmidt
On Apr 13, 2010, at 16:36, David Bartmess wrote:
> On 4/13/2010 3:27 PM, Disc Magnet wrote:
>> I did that. I ran these two commands.
>> 
>> chgrp -R www-data myrepository
>> chown -R 770 myrepository
>> 
>> Now, I get this error:
>> 
>> $ svn commit -m "Updating"
>> svn: Commit failed (details follow):
>> svn: Could not open the requested SVN filesystem
> 
> Probably your http server isn't pointing to the correct path.
> Check your Location in the httpd.conf
> 
> i.e.,
> 
> 
> SVNPath /home/magnet/myrepository
> 

No, he already showed us that SVNParentPath, the way he originally had it, is 
correct:


On Tue, Apr 13, 2010 at 10:01 PM, Disc Magnet wrote:
> 
>  DAV svn
>  SVNParentPath /home/magnet/myrepository/
> 

[snip]

> mag...@faku:~/myrepository$ ls -l
> total 12
> drwxr-xr-x 4 magnet magnet 4096 2010-04-11 18:13 ondalabondala
> drwxr-xr-x 6 magnet magnet 4096 2010-04-11 18:12 hachumachu
> drwxr-xr-x 6 magnet magnet 4096 2010-04-11 19:36 haggupaggu


He also said checking out works fine, so the path must be correct.

> The checkout command runs fine:
> 
> svn co http://localhost/myrepository/hachumachu


Unless he's changed the configuration. What does it say in the Apache error log 
- it should show the specific path where it's now looking for (and not finding) 
your repository.



Re: Is there a simple log/diff frontend (like gitk)?

2010-04-13 Thread Lorenz
Ryan Schmidt wrote:
>On Apr 13, 2010, at 12:32, Thomas Allen wrote:
>
>> Maybe I have not yet
>> mastered the "log" command, but  I find the output of the following
>> two commands to be confusing:
>> 
>> $ svn log -r HEAD
>> 
>> r3617 | tallen | 2010-04-12 15:57:35 -0400 (Mon, 12 Apr 2010) | 1 line
>> 
>> full comments + jslint fixes
>> 
>> $ svn log | grep tallen # outputs nothing
>
>Probably your working is not up to date. "svn up" before running "svn log" 
>would probably work.

because "svn log" on a working copy without "-r" defaults to "-r BASE"
which is the last checked-out/updated-to revision.
-- 

Lorenz