Re: Possible bug in SVN server with MIME formatted files

[Ulrich Eckhardt]

On Wednesday 22 June 2011, Nuno Cruces wrote:
> I believe I have found a bug the subversion server.
> 
> It seems that, after committing a MIME formatted file (such as the one
> attached), I can't do anything to the file.
> 
> Committing changes, returns the following:
> 
> Commit failed (details follow):
> CHECKOUT of
> '/(.)/recover.eml':
> Could not read status line: connection was closed by server
> (http://.ydreams.com)

What is in the server logs? Why did it close the connection? What I'm also 
wondering is if there is some kind of filter in between your machine and the 
server that could e.g. misdetect this as incoming mail traffic which you're 
not supposed to use.

BTW: Using HTTP to communicate with a server on the web for authenticated 
access is a security risk. You should use HTTPS instead. With that, you would 
probably also work around the bug in above filter software, since it can't 
sniff the content of the communication.


> I'm on windows, and have tried multiple clients, which is why I've
> assumed it is a problem with the server.

That or in between server and client.


> The rest of the repository is available and working. I can checkout the
> project (this file included).

This and the fact that you can't even delete it (which shouldn't transmit any 
content) speaks against my assumptions above. However, SVN usually ignores the 
content of files, so the fact that it's MIME-formatted shouldn't matter.


Good luck!

Uli

**
Domino Laser GmbH, Fangdieckstra�e 75a, 22547 Hamburg, Deutschland
Gesch�ftsf�hrer: Thorsten F�cking, Amtsgericht Hamburg HR B62 932
**
Visit our website at http://www.dominolaser.com
**
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. Domino Laser GmbH ist f�r diese Folgen nicht 
verantwortlich.
**

Re: Exclude a directory from a copy.

[Kurt Pruenner]

On 24.06.11 05:17, Gavin Baumanis wrote:
> Initially I thought I would check if there was some "little gem" to
> be used that would do it without me having to the extra work of
> manually;
> 
> * Deleting the unwanted directory from myNewBranch 
> * Reverting the delete in the trunk after reintegration.

Seems you missed Daniel's answer to that:

On 23.06.11 14:48, Daniel Shahaf wrote:
> But actually I suggest to do it as you suggested, with 'svn rm URL' as
> a separate commit, which is then 'merge --record-only'ed to trunk.
> (assuming it's a branch intended for reintegration)

-- 
Kurt Bernhard Pruenner --- Haendelstrasse 17 --- 4020 Linz --- Austria

np: Atmosphere - Bad Bad Daddy (The Family Sign)

Apache is exposing my Subversion repository internals (e.g. conf, db, hooks, etc.)

[Joshua Davies]

I'm new to Subversion repository administration - after reading the O'Reilly
book "Version Control with Subversion", and following the instructions there
and on the web site, I've got a repository installed under "/var/svn/repos":

[jdavies@hostname repos]$ pwd
/var/svn/repos
[jdavies@hostname repos]$ ls
README.txt  conf  dav  db  format  hooks  locks

I want to expose this over HTTP, so I've added the following to my Apache
config:


  DAV svn
  SVNPath /var/svn/repos
  AuthType Basic
  AuthName "Subversion Repository"
  AuthUserFile /path/to/auth-file
  Require valid-user
  Order deny,allow
  Deny from all
  Allow from ...
  Allow from ...
  Allow from ...


(slightly edited, of course).

Everything seems to be working, but when I load my repository from a web
server - e.g.

https://hostname/repos

I see my projects listed, along with the Subversion repository internals:

repos - Revision 64: /

   - Project1
   - README.txt 
   - conf/ 
   - db/ 
   - format 
   - hooks/ 
   - P roject2
   - locks/ 
   - Project3

What have I gotten wrong here?  I'm sure there's a way to have only the
projects, and not the repository internals, exposed.

Re: Apache is exposing my Subversion repository internals (e.g. conf, db, hooks, etc.)

[Stefan Sperling]

On Fri, Jun 24, 2011 at 11:05:32AM -0500, Joshua Davies wrote:
> Everything seems to be working, but when I load my repository from a web
> server - e.g.
> 
> https://hostname/repos
> 
> I see my projects listed, along with the Subversion repository internals:
> 
> repos - Revision 64: /
> 
>- Project1
>- README.txt 
>- conf/ 
>- db/ 
>- format 
>- hooks/ 
>- P roject2
>- locks/ 
>- Project3
> 
> What have I gotten wrong here?  I'm sure there's a way to have only the
> projects, and not the repository internals, exposed.

It's a wild guess, but maybe you didn't load mod_dav_svn into Apache?

Re: Apache is exposing my Subversion repository internals (e.g. conf, db, hooks, etc.)

[Andy Levy]

On Fri, Jun 24, 2011 at 12:05, Joshua Davies  wrote:
> I'm new to Subversion repository administration - after reading the O'Reilly
> book "Version Control with Subversion", and following the instructions there
> and on the web site, I've got a repository installed under "/var/svn/repos":
>
> [jdavies@hostname repos]$ pwd
> /var/svn/repos
> [jdavies@hostname repos]$ ls
> README.txt  conf  dav  db  format  hooks  locks
> I want to expose this over HTTP, so I've added the following to my Apache
> config:
> 
>   DAV svn
>   SVNPath /var/svn/repos
>   AuthType Basic
>   AuthName "Subversion Repository"
>   AuthUserFile /path/to/auth-file
>   Require valid-user
>   Order deny,allow
>   Deny from all
>   Allow from ...
>   Allow from ...
>   Allow from ...
> 
> (slightly edited, of course).
> Everything seems to be working, but when I load my repository from a web
> server - e.g.
> https://hostname/repos
> I see my projects listed, along with the Subversion repository internals:
>
> repos - Revision 64: /
>
> Project1
> README.txt
> conf/
> db/
> format
> hooks/
> Project2
> locks/
> Project3
>
> What have I gotten wrong here?  I'm sure there's a way to have only the
> projects, and not the repository internals, exposed.

This looks like someone has committed a repository database (the
results of svnadmin create) to your repository. Check the log of your
repository, it should indicate when & what happens.

Re: Apache is exposing my Subversion repository internals (e.g. conf, db, hooks, etc.)

[Joshua Davies]

Nope, here are my modules:

LoadModule dav_svn_module modules/mod_dav_svn.so
LoadModule authz_svn_module   modules/mod_authz_svn.so

but thanks for the quick response!

On Fri, Jun 24, 2011 at 11:26 AM, Stefan Sperling  wrote:

> On Fri, Jun 24, 2011 at 11:05:32AM -0500, Joshua Davies wrote:
> > Everything seems to be working, but when I load my repository from a web
> > server - e.g.
> >
> > https://hostname/repos
> >
> > I see my projects listed, along with the Subversion repository internals:
> >
> > repos - Revision 64: /
> >
> >- Project1
> >- README.txt 
> >- conf/ 
> >- db/ 
> >- format 
> >- hooks/ 
> >- P roject2
> >- locks/ 
> >- Project3
> >
> > What have I gotten wrong here?  I'm sure there's a way to have only the
> > projects, and not the repository internals, exposed.
>
> It's a wild guess, but maybe you didn't load mod_dav_svn into Apache?
>



-- 
Managing Director - Architecture
2Xoffice.com
(214)636-2679

Re: Apache is exposing my Subversion repository internals (e.g. conf, db, hooks, etc.)

[Stefan Sperling]

On Fri, Jun 24, 2011 at 06:26:25PM +0200, Stefan Sperling wrote:
> On Fri, Jun 24, 2011 at 11:05:32AM -0500, Joshua Davies wrote:
> It's a wild guess, but maybe you didn't load mod_dav_svn into Apache?

I guessed wrong :) Andy's explanation makes a lot more sense.

RE: Apache is exposing my Subversion repository internals (e.g. conf, db, hooks, etc.)

[Bob Archer]

> On Fri, Jun 24, 2011 at 11:26 AM, Stefan Sperling 
> wrote:
> On Fri, Jun 24, 2011 at 11:05:32AM -0500, Joshua Davies wrote:
> > Everything seems to be working, but when I load my repository
> from a web
> > server - e.g.
> >
> > https://hostname/repos
> >
> > I see my projects listed, along with the Subversion repository
> internals:
> >
> > repos - Revision 64: /
> >
> >    - Project1
> >    - README.txt 
> >    - conf/ 
> >    - db/ 
> >    - format 
> >    - hooks/ 
> >    - P roject2
> >    - locks/ 
> >    - Project3
> >
> > What have I gotten wrong here?  I'm sure there's a way to have
> only the
> > projects, and not the repository internals, exposed.
> It's a wild guess, but maybe you didn't load mod_dav_svn into
> Apache?
> 
> Nope, here are my modules:
> 
> LoadModule dav_svn_module modules/mod_dav_svn.so
> LoadModule authz_svn_module   modules/mod_authz_svn.so
> 
> but thanks for the quick response!
>

Can you use the svn cmd line client to list your repository using the file 
protocol. Perhaps someone imporated the repo folders into the repository?

BOb

Re: Apache is exposing my Subversion repository internals (e.g. conf, db, hooks, etc.)

[Andy Levy]

On Fri, Jun 24, 2011 at 12:29, Joshua Davies  wrote:
> Nope, here are my modules:
> LoadModule dav_svn_module     modules/mod_dav_svn.so
> LoadModule authz_svn_module   modules/mod_authz_svn.so
> but thanks for the quick response!

Are they being loaded properly? Anything in the Apache error log?


> On Fri, Jun 24, 2011 at 11:26 AM, Stefan Sperling  wrote:
>>
>> On Fri, Jun 24, 2011 at 11:05:32AM -0500, Joshua Davies wrote:
>> > Everything seems to be working, but when I load my repository from a web
>> > server - e.g.
>> >
>> > https://hostname/repos
>> >
>> > I see my projects listed, along with the Subversion repository
>> > internals:
>> >
>> > repos - Revision 64: /
>> >
>> >    - Project1
>> >    - README.txt 
>> >    - conf/ 
>> >    - db/ 
>> >    - format 
>> >    - hooks/ 
>> >    - P roject2
>> >    - locks/ 
>> >    - Project3
>> >
>> > What have I gotten wrong here?  I'm sure there's a way to have only the
>> > projects, and not the repository internals, exposed.
>>
>> It's a wild guess, but maybe you didn't load mod_dav_svn into Apache?
>
>
>
> --
> Managing Director - Architecture
> 2Xoffice.com
> (214)636-2679
>
>

Re: Apache is exposing my Subversion repository internals (e.g. conf, db, hooks, etc.)

[Joshua Davies]

Ah... I never even thought of that.  You're right, it looks like that's what
happened.  Sorry for blaming Subversion for what appears to be an internal
mistake ; )

On Fri, Jun 24, 2011 at 11:32 AM, Bob Archer  wrote:

> > On Fri, Jun 24, 2011 at 11:26 AM, Stefan Sperling 
> > wrote:
> > On Fri, Jun 24, 2011 at 11:05:32AM -0500, Joshua Davies wrote:
> > > Everything seems to be working, but when I load my repository
> > from a web
> > > server - e.g.
> > >
> > > https://hostname/repos
> > >
> > > I see my projects listed, along with the Subversion repository
> > internals:
> > >
> > > repos - Revision 64: /
> > >
> > >- Project1
> > >- README.txt 
> > >- conf/ 
> > >- db/ 
> > >- format 
> > >- hooks/ 
> > >- P roject2
> > >- locks/ 
> > >- Project3
> > >
> > > What have I gotten wrong here?  I'm sure there's a way to have
> > only the
> > > projects, and not the repository internals, exposed.
> > It's a wild guess, but maybe you didn't load mod_dav_svn into
> > Apache?
> >
> > Nope, here are my modules:
> >
> > LoadModule dav_svn_module modules/mod_dav_svn.so
> > LoadModule authz_svn_module   modules/mod_authz_svn.so
> >
> > but thanks for the quick response!
> >
>
> Can you use the svn cmd line client to list your repository using the file
> protocol. Perhaps someone imporated the repo folders into the repository?
>
> BOb
>
>


-- 
Managing Director - Architecture
2Xoffice.com
(214)636-2679

Moving an existing Repository to a newly created repository

[Tech Geek]

All our SVN repositories are stored at /var/lib/svn.

Let's say we have an existing repository called "ProjectA" i.e.
/var/lib/svn/ProjectA. We created a brand new fresh repository called
"Projects" like this /var/lib/svn/Projects.

Now we would like to rename our existing repository "ProjectA" to
simply "A" and then move it (maintaining all the revisions,
prop-changes, etc.) under /var/lib/svn/Projects repository.

So before:
/var/lib/svn/
/var/lib/svn/ProjectA

After:
/var/lib/svn/
/var/lib/svn/Projects/A

I tried using export/import command and also SVN move command from
TSVN client but I am not able to figure out what's is the correct way
to do this.

Re: Moving an existing Repository to a newly created repository

[Geoff Hoffman]

You should be able to use regular old mv on the command line for this.
I just did this yesterday and was happily surprised that everything just
worked.
(Requires svn switch on the client side working copies.)


On Fri, Jun 24, 2011 at 11:28 AM, Tech Geek  wrote:

> All our SVN repositories are stored at /var/lib/svn.
>
> Let's say we have an existing repository called "ProjectA" i.e.
> /var/lib/svn/ProjectA. We created a brand new fresh repository called
> "Projects" like this /var/lib/svn/Projects.
>
> Now we would like to rename our existing repository "ProjectA" to
> simply "A" and then move it (maintaining all the revisions,
> prop-changes, etc.) under /var/lib/svn/Projects repository.
>
> So before:
> /var/lib/svn/
> /var/lib/svn/ProjectA
>
> After:
> /var/lib/svn/
> /var/lib/svn/Projects/A
>
> I tried using export/import command and also SVN move command from
> TSVN client but I am not able to figure out what's is the correct way
> to do this.

SVN 1.7 - check out single file?

[Andy Levy]

With the new way WCs are managed, will it be possible to check out a
single file, instead of having to do multiple steps with sparse
directories just to get a single file in a directory? Looking at the
release notes and CHANGES file, I think the answer is "no", but I need
someone more knowledgeable to back me up here before I take the answer
back to the person who asked me. Thanks.

Re: SVN 1.7 - check out single file?

[Stefan Sperling]

On Fri, Jun 24, 2011 at 02:49:58PM -0400, Andy Levy wrote:
> With the new way WCs are managed, will it be possible to check out a
> single file, instead of having to do multiple steps with sparse
> directories just to get a single file in a directory? Looking at the
> release notes and CHANGES file, I think the answer is "no", but I need
> someone more knowledgeable to back me up here before I take the answer
> back to the person who asked me. Thanks.

No, you still need to checkout a directory. But it sounds like the
new --parents option of svn update might help you a bit:
http://subversion.apache.org/docs/release-notes/1.7.html#update-parents

Re: Moving an existing Repository to a newly created repository

[Tech Geek]

> You should be able to use regular old mv on the command line for this.
So,
svadmin create /var/lib/svn/Projects # Create new repo Projects
mv /var/lib/svn/ProjectA A   # Rename ProjectA to A
and then?
how do I move repository "A" under "Projects" repository?

Re: Moving an existing Repository to a newly created repository

[Geoff Hoffman]

On Fri, Jun 24, 2011 at 2:28 PM, Tech Geek  wrote:

> > You should be able to use regular old mv on the command line for this.
> So,
> svadmin create /var/lib/svn/Projects # Create new repo Projects
> mv /var/lib/svn/ProjectA A   # Rename ProjectA to A
> and then?
> how do I move repository "A" under "Projects" repository?
>


Actually, trick question -- I was about to say svn copy -- but you can't use
svn copy between two different repositories, instead:

You use the *svnadmin dump* command to generate the dump data, and *svnadmin
load* to populate a new repository with it (see the section called
“Migrating a 
Repository”
).

Re: Moving an existing Repository to a newly created repository

[Les Mikesell]

On 6/24/2011 5:06 PM, Geoff Hoffman wrote:

On Fri, Jun 24, 2011 at 2:28 PM, Tech Geek mailto:techgeek12...@gmail.com>> wrote:

 > You should be able to use regular old mv on the command line for
this.
So,
svadmin create /var/lib/svn/Projects # Create new repo Projects
mv /var/lib/svn/ProjectA A   # Rename ProjectA to A
and then?
how do I move repository "A" under "Projects" repository?



Actually, trick question -- I was about to say svn copy -- but you can't
use svn copy between two different repositories, instead:

You use the *svnadmin dump* command to generate the dump data, and
*svnadmin load* to populate a new repository with it (see the section
called “Migrating a Repository”
).


That is, if you really need to move the contents of one repository into 
a different one instead of just changing the location and name of the 
existing one in the filesystem.  The goal here doesn't seem clear.  If 
you are trying to combine multiple repositories into one, you can't keep 
the old revision numbers of more than one and you'll have to abandon all 
checked out working copies and check them out again.


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