ModificationDate after commit

[Claudius Sailer]

Hello,

we have at the moment a little problem with svn and the modification date
of files we want to commit.

we use a software with a lot of EXE-Files where the developer company uses
the modification date as version information. So this informations are
important for us.
the software we get from this company is imported into a vendor branch (for
every patch or hotfix delivery a new vendor brnach) and when we check out
we see the correct modification date in our file structure because we
activated use-commit-times = yes. After imported the sent software we want
to merge this with a branch or trunk and commit the changes. After that the
modification date is lost.

What can we do that the modification date we can see on file structur is
also stored in svn and is also possible to see after checkout/update?

thanks for help

bye


Claudius

Landesbank Baden-Wuerttemberg
Anstalt des oeffentlichen Rechts
Hauptsitze: Stuttgart, Karlsruhe, Mannheim, Mainz
HRA 12704
Amtsgericht Stuttgart

Re: Question about excessive mergeinfo

[Stein Somers]

I have a pre-commit hook to detect mergeinfo
below root, and remove it whenever it occurs


For clarity: the pre-commit hook detects and rejects. The one removing 
the mergeinfo is me, using svn propdel.


Someone asked for the hook code, here it is. It's not my submission for 
a beauty contest and there are some unrelated checks in there. I use the 
SVN command line instead of python bindings because I can't find the 
slightest explanation on them.


--8>

#!/usr/bin/python

# PRE-COMMIT HOOK
SVNLOOK = '/usr/bin/svnlook'

import subprocess
import sys

repos, txn = sys.argv[1:]

rc = 0

"""
logmsg = subprocess.Popen([SVNLOOK, 'log', repos, '--transaction', txn], 
stdout=subprocess.PIPE).stdout.read()

if logmsg.isspace():
sys.stderr.write("Empty log message\n")
rc = 1
"""

changes = subprocess.Popen([SVNLOOK, 'changed', repos, '--transaction', 
txn], stdout=subprocess.PIPE).stdout.readlines()

for change in changes:
action = change[0]
assert(change[3] == ' ')
path = change[4:-1] # strip 2 leading change type characters 
followed by a space, and strip trailing newline

is_dir = path.endswith('/')
is_top_dir = False
if is_dir:
path_parts = path.split('/')
assert(path_parts[-1] == '')
if len(path_parts) == 2 and path_parts[0] == 'trunk':
is_top_dir = True
if len(path_parts) == 3 and path_parts[0] in 
('branches', 'tags'):

is_top_dir = True

if action != 'D': # Delete
props = []
for entry in subprocess.Popen([SVNLOOK, 'proplist', 
repos, '--transaction', txn, path], stdout=subprocess.PIPE).stdout:

assert(entry.startswith('  '))
prop = entry[2:-1]
props.append(prop)

if is_top_dir and not 'svn:mergeinfo' in props:
sys.stderr.write(path + ": missing 
svn:mergeinfo\n")

rc = 1
if not is_top_dir and 'svn:mergeinfo' in props:
sys.stderr.write(path + ": unexpected 
svn:mergeinfo\n")

rc = 1
if not is_top_dir and 'bugtraq:url' in props:
sys.stderr.write(path + ": unexpected 
bugtraq:url\n")

rc = 1
if not is_top_dir and 'bugtraq:logregex' in props:
sys.stderr.write(path + ": unexpected 
bugtraq:logregex\n")

rc = 1
if not is_dir and not 'svn:mimetype' in props: # then 
it's some kind of text file
for line in subprocess.Popen([SVNLOOK, 'cat', 
repos, '--transaction', txn, path], stdout=subprocess.PIPE).stdout:

if "DO_NOT_COMMIT" in line:
sys.stderr.write(path + ": 
found DO_NOT_COMMIT\n")

rc = 1
break

sys.exit(rc)

--8>

--
Stein

Re: online tutorial on setting up new subversion/trac repo?

[James Bailey]

On Tue, Jan 12, 2010 at 7:11 PM, Robert P. J. Day wrote:

>
>  can someone recommend a decent online tutorial to set up a new
> subversion repo plus trac (that's relevant for fedora 12)?  i found
> this:
>
> http://www.yolinux.com/TUTORIALS/LinuxSubversionAndTracServer.html
>
> but it seems to be overly verbose and doesn't specifically mention f12
> (although i'm sure most of it is perfectly fine).
>
>  i'm after the minimum presentation to get something like that going
> as a demo, so i'm quite willing to skip things like, say, advanced
> authentication (at least for now).
>
>  if i have to rewrite that tutorial for fedora, then i'm willing to
> post the final results somewhere.
>
>  thoughts?
>
> rday
> --
>
>
> 
> Robert P. J. Day   Waterloo, Ontario, CANADA
>
>Linux Consulting, Training and Kernel Pedantry.
>
> Web page:  http://crashcourse.ca
> Twitter:   http://twitter.com/rpjday
> 
>
Hi Robert,

I had a quick Google around and found this which shows how to set up Trac
with svn and Apache for FC4 and later.

http://trac.edgewall.org/wiki/TracOnFedoraCore

I hope it might be of some
use to you?


-- 
James Bailey
http://subversion.wandisco.com

Re: copying from another branch [Question about excessive mergeinfo]

[Stein Somers]

On 12/01/2010 10:40, Ulrich Eckhardt wrote:

Why only merge a part of the initial changeset?


Well, you said I should merge, and I only want a part!

Okay, first of all, I have no question. I just brought this up to 
illustrate that excessive mergeinfo exists and you shouldn't assume 
you're doing something wrong and you can prevent it from being 
committed. I did find your point interesting, but now I don't think you 
were making the point I read. But in case you were, here is my 
illustration elaborated.


I want a copy of some kind of file set that was shipped to customers, 
called /branches/fancy_release/sample_input


I want a copy called /trunk/sample_input_of_fancy_release so I can add 
test code to insure that the software is backwards compatibility, at 
least for the input I already shipped myself.


I said: URL -> WC copy, but that adds duplicate mergeinfo. You said, 
merge the addition. But the changeset that originally added sample_input 
contains other stuff I'm not interested in, and I want the final version 
of sample_input. So, quite a complicated 2-stage merge process it seemed.


--
Stein

Re: windows path not modified

[Stein Somers]

It's a useful report in the right hands, but there are many installers 
of SVN on many platforms and none are discussed here. All I can tell is 
that your installer is for Windows and it doesn't look like one I know. 
You should contact the creator of the installer (and mention which 
version of Windows).


--
Stein

Re: online tutorial on setting up new subversion/trac repo?

[Robert P. J. Day]

On Wed, 13 Jan 2010, James Bailey wrote:

> Hi Robert, I had a quick Google around and found this which shows
> how to set up Trac with svn and Apache for FC4 and later.
>
> http://trac.edgewall.org/wiki/TracOnFedoraCore
>
> I hope it might be of some use to you?

  possibly, since FC4 is pretty old by now.  i'm also torn between
setting up trac via apache, or keeping things simple using tracd.  but
i'll give that page a perusal, thanks.

rday
--



Robert P. J. Day   Waterloo, Ontario, CANADA

Linux Consulting, Training and Kernel Pedantry.

Web page:  http://crashcourse.ca
Twitter:   http://twitter.com/rpjday

Re: subversion-1.6.6-1.i386.rpm

[Stein Somers]

I can't answer your question, but I installed the Summersoft packages 
listed on subversion.tigris.org using "yum install --nogpgcheck". This 
subversion-1.6.6-1 package comes with neon-0.28 and sqlite-3.5.9. So you 
can get subversion-1.6.6-1 without sqlite3.4.


--
Stein

file permissions

[Vojtěch Jína]

Hi, Ive got a problem with file permissions.
All files in the project have 644, but one special file should have 777, 
because I need to change content of the file, using web interface...
I set 777 permissions for the file, but after svn update (if this 
file has changed), again the 644...

Can you help me, whats the best sollution ?
- probably I can set umask, but then it will apply to all new files... I 
dont want that...
- is there something like "post-update" hook ? As I know, all hooks are 
executed on svn server, but not on working copies...

Thanks a lot for any help...
VJ


__ Informace od ESET NOD32 Antivirus, verze databaze 4765 (20100112) 
__

Tuto zpravu proveril ESET NOD32 Antivirus.

http://www.eset.cz

Re: file permissions

[Stein Somers]

> one special file should have 777

You can make it 755 by committing the svn:executable property on the 
file, but I don't think there is anything similar for pure access control.


--
Stein

RE: sync bug -> corrupted proxy repo

[Jon Foster]

Hi,

Andersen, Krista [mailto:krista.ander...@itg.com] wrote:
> Twice I have seen one of my proxy repositories become corrupted due
> to an apparent bug in the svnsync sync process.  Has anyone else
> seen this type of behavior from Subversion?

This is probably caused by issue 3546 [1][2].  This is a race
condition - if you have several sync processes running at the same
time then the mirror can get corrupted.  You had three commits which
were 1 second apart, so your hook script started 3 copies of svnsync
within 2 seconds.  I think this is the first practical report of this
bug; previous discussion was theoretical.

> Here is a comparison the output of the svn log -v for the offending
> revisions (324,325) on both the corrupted and non-corrupted proxy
> repo.

It looks like rev 323 got mirrored twice (as mirror revs 323 and 324),
then rev 324 was mirrored (as mirror rev 325).

> I am a bit concerned about the stability of Subversion since this
> is the second time in two months that I have had to fix this issue.
> Is there a patch or something to prevent this in the future?

Suggested workaround: Change your hook scripts to use the lockf or
lockfile tools[3] to ensure that only one instance of svnsync runs
at once.

Kind regards,
 
Jon

[1]
http://mail-archives.apache.org/mod_mbox/subversion-dev/200911.mbox/%3C2
0091127115356.gc9...@jack.stsp.name%3e

[2] http://subversion.tigris.org/issues/show_bug.cgi?id=3546

[3]
http://mail-archives.apache.org/mod_mbox/subversion-dev/200911.mbox/%3C2
0091127132659.ge9...@jack.stsp.name%3e



**
This email and its attachments may be confidential and are intended solely for 
the use of the individual to whom it is addressed. Any views or opinions 
expressed are solely those of the author and do not necessarily represent those 
of Cabot Communications Ltd.

If you are not the intended recipient of this email and its attachments, you 
must take no action based upon them, nor must you copy or show them to anyone.

Cabot Communications Limited
Verona House, Filwood Road, Bristol BS16 3RY, UK
+44 (0) 1179584232

Co. Registered in England number 02817269

Please contact the sender if you believe you have received this email in error.

**


__
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
__

RE: sync bug -> corrupted proxy repo

[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: Jon Foster [mailto:jon.fos...@cabot.co.uk]
> Sent: 13 January 2010 13:13
> To: Andersen, Krista; users@subversion.apache.org
> Cc: ssi-svn_admin
> Subject: RE: sync bug -> corrupted proxy repo
>
> Hi,
>
> Andersen, Krista [mailto:krista.ander...@itg.com] wrote:
> > Twice I have seen one of my proxy repositories become
> corrupted due to
> > an apparent bug in the svnsync sync process.  Has anyone else seen
> > this type of behavior from Subversion?
>
> This is probably caused by issue 3546 [1][2].  This is a race
> condition - if you have several sync processes running at the
> same time then the mirror can get corrupted.  You had three
> commits which were 1 second apart, so your hook script
> started 3 copies of svnsync within 2 seconds.  I think this
> is the first practical report of this bug; previous
> discussion was theoretical.
>
> > Here is a comparison the output of the svn log -v for the offending
> > revisions (324,325) on both the corrupted and non-corrupted proxy
> > repo.
>
> It looks like rev 323 got mirrored twice (as mirror revs 323
> and 324), then rev 324 was mirrored (as mirror rev 325).
>
> > I am a bit concerned about the stability of Subversion
> since this is
> > the second time in two months that I have had to fix this issue.
> > Is there a patch or something to prevent this in the future?
>
> Suggested workaround: Change your hook scripts to use the
> lockf or lockfile tools[3] to ensure that only one instance
> of svnsync runs at once.

Is it not the case that a svn commit cannot start before the post-commit hooks 
has finished? I am asking becuase I will be implementing a DR system using 
svnsync, but I am not planning to let the post-commit finish before svnsync has 
finished (I don't care if it takes a bit longer, I can cope with that and with 
my users).

Giulio

RE: ModificationDate after commit

[Thomas Hemmer]

No chance for that, sorry.

Anyway, version information should rather be stored within the resource
area of the PE file instead of abusing the time stamp for this purpose
(provided that you are really talking about Windows, as the term
"EXE-Files" implies).
Perhaps you might ask them to use the VERSIONINFO statement in their
resource script in order to achieve that. This is the recommended
practice within the Windows world.


Best regards,

Thomas

> -Original Message-
> From: Claudius Sailer [mailto:claudius.sai...@lbbw.de]
> Sent: Wednesday, January 13, 2010 9:52 AM
> To: users@subversion.apache.org
> Subject: ModificationDate after commit
>
>
> Hello,
>
> we have at the moment a little problem with svn and the
> modification date of files we want to commit.
>
> we use a software with a lot of EXE-Files where the developer
> company uses the modification date as version information. So
> this informations are important for us.
> the software we get from this company is imported into a
> vendor branch (for every patch or hotfix delivery a new
> vendor brnach) and when we check out we see the correct
> modification date in our file structure because we activated
> use-commit-times = yes. After imported the sent software we
> want to merge this with a branch or trunk and commit the
> changes. After that the modification date is lost.
>
> What can we do that the modification date we can see on file
> structur is also stored in svn and is also possible to see
> after checkout/update?
>
> thanks for help
>
> bye
>
>
> Claudius
>
> Landesbank Baden-Wuerttemberg
> Anstalt des oeffentlichen Rechts
> Hauptsitze: Stuttgart, Karlsruhe, Mannheim, Mainz HRA 12704
> Amtsgericht Stuttgart
>
>



GO Engineering GmbH - Stolzenbergstr. 13/IV - 76532 Baden-Baden
Geschäftsführer:
Helmut Gerstner, Dipl.-Ing. (FH)
Ralf Wörner, Dipl.-Ing. (FH)
Registergericht: Mannheim HRB 201811

Antwort: RE: ModificationDate after commit

[Claudius Sailer]

Hello,

we asked 2002 for an other version controlling identification, but the
company won't change the ModificationDate-Version-Identification.

With CVS wir imported the files and the modification date is stored and
could be checked out. Now we move to svn and I thought that we can use
there some features (merge and commit). To get the repository date we found
a property, but without the possibility to store/save the modification date
from a file in my WC into the repository by using commit/merge I have only
the chance to Import the files to the repository. In this case the correct
date is stored in the repository. At the moment I don't know why this
works, I have to ask my technical guy.
The recommended practice within the windows world is not known by everybody
so I have to look for solutions. But I see that there is an issue #1256
created 2003 which is waiting for programming where absolutly matches my
problem.


bye


Claudius




Landesbank Baden-Wuerttemberg
Anstalt des oeffentlichen Rechts
Hauptsitze: Stuttgart, Karlsruhe, Mannheim, Mainz
HRA 12704
Amtsgericht Stuttgart

|>
||
||
||
||
|  "Thomas Hemmer"   |
| |
||
|  13.01.2010 14:50  |
|>
  
>---|
  | 
  |
  | 
  |
  | 
An|
  |  "'Claudius Sailer'" , 
 |
  | 
 Kopie|
  | 
  |
  | 
 Thema|
  |  RE: ModificationDate after commit  
  |
  | 
  |
  | 
  |
  | 
  |
  | 
  |
  | 
  |
  
>---|




No chance for that, sorry.

Anyway, version information should rather be stored within the resource
area of the PE file instead of abusing the time stamp for this purpose
(provided that you are really talking about Windows, as the term
"EXE-Files" implies).
Perhaps you might ask them to use the VERSIONINFO statement in their
resource script in order to achieve that. This is the recommended
practice within the Windows world.


Best regards,

Thomas

> -Original Message-
> From: Claudius Sailer [mailto:claudius.sai...@lbbw.de]
> Sent: Wednesday, January 13, 2010 9:52 AM
> To: users@subversion.apache.org
> Subject: ModificationDate after commit
>
>
> Hello,
>
> we have at the moment a little problem with svn and the
> modification date of files we want to commit.
>
> we use a software with a lot of EXE-Files where the developer
> company uses the modification date as version information. So
> this informations are important for us.
> the software we get from this company is imported into a
> vendor branch (for every patch or hotfix delivery a new
> vendor brnach) and when we check out we see the correct
> modification date in our file structure because we activated
> use-commit-times = yes. After imported the sent software we
> want to merge this with a branch or trunk and commit the
> changes. After that the modification date is lost.
>
> What can we do that the modification date we can see on file
> structur is also stored in svn and is also possible to see
> after checkout/update?
>
> thanks for help
>
> bye
>
>
> Claudius
>
> Landesbank Baden-Wuerttemberg
> Anstalt des oeffentlichen Rechts
> Hauptsitze: Stuttgart, Karlsruhe, Mannheim, Mainz HRA 12704
> Amtsgericht Stuttgart
>
>



GO Engineering GmbH - Stolzenberg

Re: RE: ModificationDate after commit

[Andy Levy]

On Wed, Jan 13, 2010 at 09:00, Claudius Sailer  wrote:
>
>
> Hello,
>
> we asked 2002 for an other version controlling identification, but the
> company won't change the ModificationDate-Version-Identification.
>
> With CVS wir imported the files and the modification date is stored and
> could be checked out. Now we move to svn and I thought that we can use
> there some features (merge and commit). To get the repository date we found
> a property, but without the possibility to store/save the modification date
> from a file in my WC into the repository by using commit/merge I have only
> the chance to Import the files to the repository. In this case the correct
> date is stored in the repository. At the moment I don't know why this
> works, I have to ask my technical guy.
> The recommended practice within the windows world is not known by everybody
> so I have to look for solutions.

The recommended practice has been recommended for probably 15 years (I
recall seeing version # info in the Properties dialog on EXEs & DLLs
back when Win95 was first released). If they aren't aware of it yet, I
have to wonder what other poor Windows development practices they
follow.

RE: ModificationDate after commit

[Bob Archer]

> we have at the moment a little problem with svn and the
> modification date
> of files we want to commit.
> 
> we use a software with a lot of EXE-Files where the developer
> company uses
> the modification date as version information. So this informations
> are
> important for us.
> the software we get from this company is imported into a vendor
> branch (for
> every patch or hotfix delivery a new vendor brnach) and when we
> check out
> we see the correct modification date in our file structure because
> we
> activated use-commit-times = yes. After imported the sent software
> we want
> to merge this with a branch or trunk and commit the changes. After
> that the
> modification date is lost.
> 
> What can we do that the modification date we can see on file
> structur is
> also stored in svn and is also possible to see after
> checkout/update?

Create a property with the modification date. This will be a versioned property 
so it will remain with the revision.

You can create a script to use when you check it which will update this 
property to match the modification date. You can have your build script read 
the property to set any files you need to that date or whatever. It shouldn't 
be too dificult to set up.

BOb

Re: Probable bug with svn copy

[Julian Foad]

Hi Alan.

Thanks for this report, and sorry for the long time to respond.

I finally got around to converting your recipe into an executable script
(on Linux) which is attached, and with this it is easy to reproduce the
problem.

On Thu, 2009-12-17, Alan Spencer wrote:
> I've been asked to analyse a problem we have had with subversion and
> come to the conclusion there is a bug in at least the client.
> 
>  
> The scenario was someone committed a new directory that made a build
> fail and in order to free up the build this commit was reverse merges
> (merge -c -)
> 
> The individual in question wanted their changes back and the opportunity
> to fix the problem. This was done by reverse merging the reverse merge.
> 
> They then fixed the problems, which included renaming a file.
> 
> They then committed these changes and updated and all looked OK.
> 
> Updating on other working copy showed that both the original and renamed
> file existed, but the working copy used did not show this.
> 
>  
> 
> I wanted to find out if this is user error or a bug and if it has been
> logged already.

This certainly looks like a bug. It sounds familiar, but I can't find it
in the issue tracker.

> And is there a way to achieve this without hitting this problem.

I'm not sure.


> Here is a log of my reproducing this:
[...]
> C:\dev\projects\build\build\svn-experiments\experiment-1>svn commit -m
> "Revert revert and renaming svn merge -c -1 . svn move
> systemtest\audit\FirstName.txt systemtest\audit\SecondName.txt" .
> Adding experiment-1\systemtest\audit
> Adding experiment-1\systemtest\audit\SecondName.txt
> Committed revision 16667.

With a release candidate for 1.6.8, using the attached script, I get the
same result as you.

With a trunk build (r898816), using the attached script, I get a
different problem here: the commit sort of fails:

+ svn commit -m 'Revert revert and renaming svn merge -c -1 . svn
move systemtest/audit/FirstName.txt systemtest/audit/SecondName.txt' .
Adding experiment-1/systemtest/audit
Deleting   experiment-1/systemtest/audit/FirstName.txt
Adding experiment-1/systemtest/audit/SecondName.txt
svn: Commit succeeded, but other errors follow:
svn: Error bumping revisions post-commit (details follow):
svn: The node 'FirstName.txt' was not found.

This is interesting, and it would be good to turn this script into a
test in the test suite so that we remember to fix the bug. Any
volunteers?

- Julian


> 
> UPDATE ELSEWHERE
> --
> 
> C:\dev\CO\trunk>svn up build\svn-experiments\experiment-1\
> Abuild\svn-experiments\experiment-1\systemtest\audit
> Abuild\svn-experiments\experiment-1\systemtest\audit\FirstName.txt
> Abuild\svn-experiments\experiment-1\systemtest\audit\SecondName.txt
> Updated to revision 16667.



AlanSpencer.sh
Description: application/shellscript

Re: Remote Datasource of my repository

[Juan Jesús Cremades Monserrat]

Hi!

I've reading all the solutions proposed, but the ideal stage will the next:

An user calls the Subversion Server, the project
http://xxx.xxx.xxx.xxx/svn/project.
The Subversion Server receives the request and recovery the information of
the datastore, which is another machine. Later, sends the project to the
user.

Usually, the information now is in my /var/svn/ directory. The ideal will be
that be yyy.yyy.yyy.yyy/svn/directory.

The dump/load cycle is a good solution, but my boss does not like it.
Regards & Thanks!!!

 ==
| Subversion Server |  <> | Datastore |
 ==
/\
||
\/
 ==
| Project User |
 ==

RE: malformed file problem -- version 1.5.7

[James D. Parra]

 
One of my users committed a file to svn and now some users are getting a
'malformed file' error. These users can no longer check out or commit.
'Svnadmin verify /svnrepos' doesn't show any problems, however 'malformed
file' appears when I do a nightly dump export; 

svnadmin dump /svnrepos > /backup/svnrepos.svn_dump 
* Dumped revision 11529.
svnadmin: Malformed file


I believe the problem lies within revision numbers 11530 and 11532.  Other
users who are working on other projects are not having problems. We are
currently at revision 11784.  Is there a way that I can repair this?
~~~


Is there a way to roll back to revision 11529 and start there?  Should I
remove all the revision number files greater that 11529 and have my users
check out again?  Trying to figure out the best way to fix this.

Many thanks,

James

RE: malformed file problem -- version 1.5.7

[Jon Foster]

Hi,

James D. Parra [mailto:jam...@musicreports.com] wrote:
> Is there a way that I can repair this?
No idea, sorry.  But:

> Is there a way to roll back to revision 11529 and start there? 

Try svnadmin dump with the -r parameter to dump just the revisions
you want to keep, then svnadmin load to load them into a new repository.
Any checkouts of r11529 or earlier should be OK; if you have a later
checkout then you'll need to delete it and re-checkout.

> Should I remove all the revision number files greater that 11529

Hand-editing the repository sounds like a bad idea*... you might get
rid of this corruption but introduce a different corruption.
Using dump/load should give you a valid repository.

Kind regards,

Jon

[*] It's number zero on the "Subversion Worst Practices" guide:
http://www.red-bean.com/fitz/presentations/2007-07-27-OSCON-svn-worst-pr
actices.pdf


**
This email and its attachments may be confidential and are intended solely for 
the use of the individual to whom it is addressed. Any views or opinions 
expressed are solely those of the author and do not necessarily represent those 
of Cabot Communications Ltd.

If you are not the intended recipient of this email and its attachments, you 
must take no action based upon them, nor must you copy or show them to anyone.

Cabot Communications Limited
Verona House, Filwood Road, Bristol BS16 3RY, UK
+44 (0) 1179584232

Co. Registered in England number 02817269

Please contact the sender if you believe you have received this email in error.

**


__
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
__

Re: NetDrive and SVN autoversioning - keep getting Broken pipe

[Richard Walker]

2010/1/12 Gunther Mayer 

> Hi guys,
>
> I'm not sure if anyone here is working with the following combination (or
> similar):
>
> Server: svn 1.6.5 (latest) + apache 2.2.12 (latest) on ubuntu karmic(9.10)
> 64bit
> Client: Windows XP or Vista, NetDrive 1.0.8.11 (latest)
>
> Server is configured to do autoversioning via WebDAV as per svnbook:
>
> 
>   DAV svn
>   SVNParentPath /var/svn
>   SVNAutoversioning on
>   ModMimeUsePathInfo on
> 
>
> My client can mount(connect) this "drive" just fine and browse through the
> directory hierarchy but when trying to open any files they are corrupted
> because they're only half retrieved from the server (tried it on a couple of
> large text files). Every now and then NetDrive reports errors but nothing
> helpful. At the same time the following appears in my apache error logs over
> and over again:
>
> [Tue Jan 12 13:42:32 2010] [error] [client xx.xx.xx.xx] (32)Broken pipe:
> Could not write data to filter.  [500, #0]
> [Tue Jan 12 13:42:32 2010] [error] [client xx.xx.xx.xx] Unable to deliver
> content.  [500, #0]
>
> and occasionally
>
> [Tue Jan 12 13:42:31 2010] [error] [client 196.7.14.173] Unable to deliver
> content.  [500, #0]
> [Tue Jan 12 13:42:31 2010] [error] [client 196.7.14.173] (104)Connection
> reset by peer: Could not write data to filter.  [500, #0]
>
> This happens almost all the time and makes my repo kind of useless on
> Windows (no, tortoisesvn won't work because we're dealing with very
> non-technical users...). I know NetDrive is commercial software but firstly
> it did come recommended in the svn book with supposedly no known issues and
> secondly it is (apart from WebDrive) my only option when it comes to
> mounting my svn repository as a file system on Windows. It seems like some
> kind of buffering problem but not sure how helpful the Novell support will
> be in trouble shooting this one...
>
> Any help or pointers would be greatly appreciated.
>
> Gunther
>

Hi Gunther.

Good on you for trying! I used a similar combination for a while to version
my My Documents folder in Windows. I also enthusiastically pushed this setup
on a couple of non-technical people as a backup solution. The idea of it is
fantastic - just working with files as normal but having all changes
automatically versioned behind the scenes. Although I didn't see the problem
you're describing, I did have issues and eventually gave it up.

It ate disk space. Webdrive/netdrive used to buffer everything. It also
really slowed my machine down. Putting the entire My Documents folder in
there was also a mistake -  iTunes and other programs filled the repository
with gigabytes of temporary file history. I also seem to remember the drives
would drop out occasionally which led to me getting lynched!

I guess a big part of the problem is the lack of webDav file system support
in Windows. I didn't feel that webdrive/netdrive really cut it. However, I
did always wonder how it would behave if you mounted the repository as a
webDAV directory in the file system of your linux server, and then shared
that via samba to expose it to the windows machines rather than have them
run netdrive? Perhaps it would be worth a try?

Wishing you the best of luck! I'd like to know how you get on. Anybody else
out there tried anything like this?

Best regards,
Richard.

svnserve: Interacting in tunnel mode

[Piotr Sipika]

Hi,
I'm trying to write a notification application which would monitor 
specific repositories and pop-up a dialog when an update has been 
detected. I noticed that 'svn log svn+ssh://...' launches 'svnserve -t' 
via ssh and believe this to be the best way for me to proceed. I tried 
running 'svnserve -t' on the command line and entering sample 'client' 
responses (following the syntax described in 
subversion/libsvn_ra_svn/protocol) to see if that approach would work, 
but no responses were visible. What is the best way for me to interact 
with svnserve in tunnel mode?

Any and all help and suggestions will be much appreciated.
Thanks,
Pete

Re: ModificationDate after commit

[Ryan Schmidt]

On Jan 13, 2010, at 02:52, Claudius Sailer wrote:

> we use a software with a lot of EXE-Files where the developer company uses
> the modification date as version information. So this informations are
> important for us.
> the software we get from this company is imported into a vendor branch (for
> every patch or hotfix delivery a new vendor brnach) and when we check out
> we see the correct modification date in our file structure because we
> activated use-commit-times = yes. After imported the sent software we want
> to merge this with a branch or trunk and commit the changes. After that the
> modification date is lost.
> 
> What can we do that the modification date we can see on file structur is
> also stored in svn and is also possible to see after checkout/update?

As you've discovered, Subversion does not store the modification date/time in 
the repository. It stores only the commit date/time. The request to have 
Subversion store the modification date/time was filed years ago; I wouldn't 
count on it getting resolved soon.

http://subversion.tigris.org/issues/show_bug.cgi?id=1256


When you check out, file modification dates are either "now" (use-commit-times 
in your Subversion client's config file is off) or the commit time 
(use-commit-times is on). If you have this feature turned on, you could 
manually set the svn:date property of the merge revision to the date of the 
original revision, but note that if this causes your revision dates not to be 
in chronological order, it means you cannot use Subversion's date-based 
revision search feature; it will happily return a result revision to you, but 
it might not be the correct one.

http://svnbook.red-bean.com/en/1.5/svn.tour.revs.specifiers.html#svn.tour.revs.dates

Note also that the revision date of course applies to every file committed in 
that revision. If it's important that different files in a single revision be 
shown to have different modification times, then this won't help you. You could 
merge each file one at a time and set that revision's svn:date to that file's 
desired modification time, but this gets unwieldy.


As Bob mentioned, you could instead add a custom property with this information 
and manage it manually.

RE: svnserve: Interacting in tunnel mode

[Thomas Loy]

Why not use SVN Notifier available at http://svnnotifier.tigris.org?

Cheers,
 
Tom Loy

-Original Message-
From: Piotr Sipika [mailto:psip...@cengen.com] 
Sent: Wednesday, January 13, 2010 2:54 PM
To: users@subversion.apache.org
Subject: svnserve: Interacting in tunnel mode

Hi,
I'm trying to write a notification application which would monitor 
specific repositories and pop-up a dialog when an update has been 
detected. I noticed that 'svn log svn+ssh://...' launches 'svnserve -t' 
via ssh and believe this to be the best way for me to proceed. I tried 
running 'svnserve -t' on the command line and entering sample 'client' 
responses (following the syntax described in 
subversion/libsvn_ra_svn/protocol) to see if that approach would work, 
but no responses were visible. What is the best way for me to interact 
with svnserve in tunnel mode?
Any and all help and suggestions will be much appreciated.
Thanks,
Pete

Re: svnserve: Interacting in tunnel mode

[Piotr Sipika]

SVN Notifier is Windows-specific. All of my workstations are linux-based.
Thanks for the suggestion, though.
Pete

On 01/13/2010 04:28 PM, Thomas Loy wrote:

Why not use SVN Notifier available at http://svnnotifier.tigris.org?

Cheers,

Tom Loy

-Original Message-
From: Piotr Sipika [mailto:psip...@cengen.com]
Sent: Wednesday, January 13, 2010 2:54 PM
To: users@subversion.apache.org
Subject: svnserve: Interacting in tunnel mode

Hi,
I'm trying to write a notification application which would monitor
specific repositories and pop-up a dialog when an update has been
detected. I noticed that 'svn log svn+ssh://...' launches 'svnserve -t'
via ssh and believe this to be the best way for me to proceed. I tried
running 'svnserve -t' on the command line and entering sample 'client'
responses (following the syntax described in
subversion/libsvn_ra_svn/protocol) to see if that approach would work,
but no responses were visible. What is the best way for me to interact
with svnserve in tunnel mode?
Any and all help and suggestions will be much appreciated.
Thanks,
Pete

Verifying a file version

[Headley, Ronald (PSC/ISMS/EAD-CTR)]

Good evening.

 

We recently encountered an issue where an incorrect version, or more
specifically, a non-existing version, of a file was promoted to
production.  We want to enhance our process to ensure we, at a minimal,
export an existing version of a file.  Can anyone suggest a command that
will check the file version (without parsing the output of the list
command; I'd rather check the execution of the command with "echo $?" or
something to that effect)?  See examples below for further details.

 

In this example, we execute a list on a file for a specific version.  As
you can see, the list succeeded.

 

$ svn list -r42 -v
svn://...:000/Repository/

 42540672 Feb 17  2009 

$ echo $?

0

 

In this example, we execute a list on a file for a specific version.  As
you can see, the list succeeded.  However, we hoped it would fail since
the only version of the file is 42.

 

$ svn list -r61 -v
svn://...:000/Repository/

 42540672 Feb 17  2009 

$ echo $?

0

 

In this example, we again execute a list on a file for a specific
version.  This time the version exceeded the highest versioned directory
tree, which is 61.

 

$ svn list -r65 -v
svn://...:000/Repository/

svn: No such revision 65

$ echo $?

1

 

Thank you,

 

Ron Headley
Contractor 
HHS/PSC/ISMS/ESS PMO (Program Management Office)

(a SDVOSB)
301-525-3801 (cell)

 

Re: Verifying a file version

[Ryan Schmidt]

On Jan 13, 2010, at 16:02, Headley, Ronald (PSC/ISMS/EAD-CTR) wrote:

> We recently encountered an issue where an incorrect version, or more 
> specifically, a non-existing version, of a file was promoted to production.  
> We want to enhance our process to ensure we, at a minimal, export an existing 
> version of a file.  Can anyone suggest a command that will check the file 
> version (without parsing the output of the list command; I’d rather check the 
> execution of the command with “echo $?” or something to that effect)?  See 
> examples below for further details.

To correct the terminology, you're trying to verify the "last changed revision" 
of the file. And I don't think you're going to find a solution that doesn't 
involve parsing the output of some svn command.

Re: Verifying a file version

[Andy Levy]

On Wed, Jan 13, 2010 at 17:02, Headley, Ronald (PSC/ISMS/EAD-CTR)
 wrote:
> Good evening.
>
>
>
> We recently encountered an issue where an incorrect version, or more
> specifically, a non-existing version, of a file was promoted to production.
> We want to enhance our process to ensure we, at a minimal, export an
> existing version of a file.  Can anyone suggest a command that will check
> the file version (without parsing the output of the list command; I’d rather
> check the execution of the command with “echo $?” or something to that
> effect)?  See examples below for further details.
>

Use svn info.  svn list really seems like the wrong tool for the job
here. You'll still have to parse the output of svn info to read the
Last Changed Revision line.

>
> In this example, we execute a list on a file for a specific version.  As you
> can see, the list succeeded.
>
>
>
> $ svn list -r42 -v
> svn://...:000/Repository/
>
>  42    540672 Feb 17  2009 
>
> $ echo $?
>
> 0
>
>
>
> In this example, we execute a list on a file for a specific version.  As you
> can see, the list succeeded.  However, we hoped it would fail since the only
> version of the file is 42.

Why would you expect it to fail? You asked for svn ls as of revision
42, and the file existed at that revision.

>
> $ svn list -r61 -v
> svn://...:000/Repository/
>
>  42    540672 Feb 17  2009 
>
> $ echo $?
>
> 0


If the file hasn't been changed since r42, this still seems correct.

Re: Copy data from one repos to another and history should not be losed

[Ryan Schmidt]

On Jan 11, 2010, at 02:48, Ullrich Jans wrote:

> Ryan Schmidt wrote:
> 
>> On Jan 5, 2010, at 06:02, Chetan Chatwani wrote:
>> 
>>> We have two repositories names as  : bmrepos and bmdevrepos.
>>> We want to copy/add data from bmrepos to bmdevrepos but history
>>> should not losed. 
>>> 
>>> Note: bpmrepos already have some contents.
>> 
>> Yes, you can do this with "svnadmin dump" and "svnadmin load".
> 
> But watch out: the dates in the revisions will not be linear afterwards, so 
> searching for revisions by date will not work any more. (AFAIK)

That's right. If that's a concern, dump both repositories, merge them together 
interlacing their revisions in chronological order, and load them into a third 
new repository. This is one of the tasks the svndumptool script can help you 
accomplish.

http://svn.borg.ch/svndumptool/

Antwort: Re: ModificationDate after commit

[Claudius Sailer]

we have this "problem" only with our EXE-Files and there we have 1200 of
them. It will be difficult to handle these manually. I also found #1256 and
red the history. poor situation for a development team. I have the benefit
that we don't use date informations for merge, diff or whatever.

we will see forward for issue #1256 ;-))
and we are looking forward for other solutions (workarounds) like we had
with CVS. The hint with the property is something we will have a look on
it.

Thanks


bye


Claudius




Landesbank Baden-Wuerttemberg
Anstalt des oeffentlichen Rechts
Hauptsitze: Stuttgart, Karlsruhe, Mannheim, Mainz
HRA 12704
Amtsgericht Stuttgart

|->
| |
| |
| |
| |
|  Ryan Schmidt   |
|   |
| |
|  13.01.2010 22:05   |
|->
  
>---|
  | 
  |
  | 
  |
  | 
An|
  |  Claudius Sailer   
  |
  | 
 Kopie|
  |  users@subversion.apache.org
  |
  | 
 Thema|
  |  Re: ModificationDate after commit  
  |
  | 
  |
  | 
  |
  | 
  |
  | 
  |
  | 
  |
  
>---|




On Jan 13, 2010, at 02:52, Claudius Sailer wrote:

> we use a software with a lot of EXE-Files where the developer company
uses
> the modification date as version information. So this informations are
> important for us.
> the software we get from this company is imported into a vendor branch
(for
> every patch or hotfix delivery a new vendor brnach) and when we check out
> we see the correct modification date in our file structure because we
> activated use-commit-times = yes. After imported the sent software we
want
> to merge this with a branch or trunk and commit the changes. After that
the
> modification date is lost.
>
> What can we do that the modification date we can see on file structur is
> also stored in svn and is also possible to see after checkout/update?

As you've discovered, Subversion does not store the modification date/time
in the repository. It stores only the commit date/time. The request to have
Subversion store the modification date/time was filed years ago; I wouldn't
count on it getting resolved soon.

http://subversion.tigris.org/issues/show_bug.cgi?id=1256


When you check out, file modification dates are either "now"
(use-commit-times in your Subversion client's config file is off) or the
commit time (use-commit-times is on). If you have this feature turned on,
you could manually set the svn:date property of the merge revision to the
date of the original revision, but note that if this causes your revision
dates not to be in chronological order, it means you cannot use
Subversion's date-based revision search feature; it will happily return a
result revision to you, but it might not be the correct one.

http://svnbook.red-bean.com/en/1.5/svn.tour.revs.specifiers.html#svn.tour.revs.dates


Note also that the revision date of course applies to every file committed
in that revision. If it's important that different files in a single
revision be shown to have different modification times, then this won't
help you. You could merge each file one at a time and set that revision's
svn:date to that file's desired modification time, but this gets unwieldy.


As Bob mentioned