Adding a file with a space in the file name and committing it works fine,
however any subsequent edit and commit of this file will fail with:
"Error: Delta source ended unexpectedly"
A file with identical content and name, except with no space in the file
name, works perfectly, I can edit and com
Let's say I have an exisiting repository at /var/lib/svn/projectA with
(tags, branches, trunk structure) on my Linux system.
I am using the mailer.py script and mailer.conf file [1] in my post-commit
hook for sending out emails whenever a new release tag (like
projectA/tags/REL-1.0) is created and
I guess my biggest hurdle at this time is how to extract the file from the
repository that I would like to send it as an attachment.
Most of the examples on the net simply specifies an explicit filename (to
show as an example) like this:
>
> You can checkout the file to /tmp and include it from there. You
> cannot reference a file in your repository with a file path.
I had thought about that but it would mean that I will need to include a svn
checkout command to /tmp/ directory in my post-commit hook, right?
If that is the case
OK I have managed to get the name of the file (after checking out to the
/tmp directory) to be attached in the commit email in a variable called
$ATTACHFILE in my post-commit hook.
But here is another issue that I am now running into:
How do I pass the value of the variable $ATTACHFILE to the mai
>
> svnadmin dump -rHEAD /path/to/oldrepo > dump
> svnadmin load /path/to/newrepo < dump
>
Thanks Ryan! That worked!
So I am relatively new to subversion as compared to most of the folks on
this mailing list. After seeing lot of examples over the web and reading
official subversion book it seems that almost every body creates their
repository in some or the other way with tags, branches and trunk structure
even t
I just noticed that the CollabNet's Subversion Edge has this feature when
you create the repository from the web browser interface.
I guess at least I am not the only one (perhaps) who thought about this.
All my repositories live under /var/lib/svn/.
Let's the output of the following command (on the SVN server):
# svn changed /var/lib/svn/projectA/
is
A PartA/tags/DEV-1.00_RC5/
Now in my post-commit hook I need the following value in a variable (say
EMAIL_URL):
EMAIL_URL=/var/lib/svn/projectA/Pa
>
> I assume you mean to also pass "-t $TXN" to svnlook in there somewhere.
>
Yes. I just copied the command from the shell prompt although I noticed that
svnlook command works just fine without the "-t $TXN" argument inside the
post-commit hook.
> Or are you asking if there's a simpler way?
Yes
Daniel,
>That is not possible for SVN to determine, as it does not know *how* you
are serving the repository (HTTP, HTTPS, svn+ssh, svn, >etc). $REPOS will
give you the physical path to the repository, not necessarily the publicly
accessible path.
That not a problem. I can always prefix the protoco
Our repositories lives in /var/lib/svn/ on a Linux server. We use the
following sturcture on per project per repository basis:
/var/lib/svn/projectA/tags/
/var/lib/svn/projectA/trunk/
/var/lib/svn/projectA/branches/
/var/lib/svn/projectB/tags/
/var/lib/svn/projectB/trunk/
/var/lib/svn/projec
David:
The standard Python pre-commit hook that comes with Subversion's
> source tarball will do the job.
Are you referring to the files svnperms.conf.example and svnperms.py found
at [1].
> I have a Perl version that does the same thing.
>
Thanks for sharing your scripts. I will take a detaile
Hi,
My repository path is /var/lib/svn for the SVN server. However I encountered
a unique situation as follow:
The following works:
#svnadmin create /var/lib/svn/projectA
>From a svn client:
#svn co http://svnserver/svn/projectA projectA
However the following does NOT work:
#mkdir /var/lib/sv
oops...I had a typo:
> However the following does NOT work:
> #mkdir /var/lib/svn/projectB/
> #sudo svnadmin create /var/lib/svn/projectB/partA
> #sudo svnadmin create /var/lib/svn/projectB/partB
>
> From a svn client:
> #svn co http://svnserver/svn/projectB/partA partB
>
However the followi
Sorry for bumping this one...We really need to find a solution/workaround
for this in order for our SVN implementation to be final.
Thanks in advance!
On Mon, Oct 18, 2010 at 6:00 PM, Tech Geek wrote:
> oops...I had a typo:
>
>
>> However the following does NOT work:
>>
>The other way you could do this, if you insist upon PartA & PartB being
separate repositories, is to have a different >block for each
project, and specify SVNParentPath as /var/lib/svn/ProjectB . Then you could
have PartA & PartB set up as separate >repositories - albeit with a lot more
manageme
Andy:
> As I asked earlier, why must PartA & PartB in a given project be
> separate repositories? Why is the more conventional approach not
> workable for you?
>
I understand what you are trying to say and I agree but let's just say that
my hands are tied without going into too much details. Thi
We are using svn, version 1.6.12 (r955767) on a Linux based machine (SVN
Server) and use TortoiseSVN as clients. However, I do not see command
svn-bisect on both of them. How can I get svn-bisect just like there is
git-bisect?
I would like to point out to guys on this list who may be looking for the
svn-bisect tool (just like I was) that it is being included in the next
release of Debian [1] and in the backported version of Debian [2].
Also see [3] if you are using a Linux distribution that does not include the
svn-bise
We have a SVN server running on a Debian Linux box. Running svn
--version returns:
svn, version 1.6.12 (r955767)
compiled Jul 28 2010, 08:58:12
Users uses TortoiseSVN client to access repositories residing on the
SVN server. My question is it OK to use the latest TSVN client
"TortoiseSVN-1.6.15
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
> 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?
We are trying to reorganize some our projects and hence repositories
so that it makes some kind of logical sense (naming wise). Our
existing repository that we want to move i.e. ProjectA has very few
commits (4 to 5) in it and we do not care if the revision numbers
change as long as we have commit
Hi,
I am just getting started with SVN and I am running the latest version of
subversion on a Windows Server. I am looking for a pre-commit.bat hook that
will check for presence of a particular file (say project.xml) before
commiting to the repository. If the working copy that is about to be
commi
>Perhaps if you explain why you want to check for the existence of this file
in the working copy we can help you find a different way of >going about it.
OK. Let me try to explain this.
The code that we are trying to commit is generated by an IDE - a software
development tool. The particular file (
>It is possible to verify that a project.xml is one of the files being
>committed because you can use "svn changed" at the time of the
>transaction to see what files are being added or modified. It would be
>possible to fail the transaction if svnlook changed doesn't have a
>project.xml file in the
>You want to enforce that the developer cannot commit unless they have this
project.xml in >their working copy, though it will never be sent to the
repository.
That's not true. The project.xml (or whatever file that particular file is)
should also be a part of commit.
I will again repeat my questi
>Is it a requirement that the file be changed each time (and thus part of a
commit), or just that it exists somewhere on the client side >(versioned or
unversioned)? The server will only know about it when it changes since the
svn client is smart enough to only send >differences.
Great question. L
Ryan - Thanks for the sample script. As mentioned before the SVN server
is on a Windows server. I will convert it to a Windows environment and give
it a shot.
I am running subversion server on a Windows machine. Right now I am in the
process of converting my exisiting projects to start using subversion and my
projects are located at different paths/locations. For example:
C:\data\project1
C:\project\bluecat
C:\software\abc
Now it seems that wehn we star
>I may have totally misunderstood you. Are the above paths you show working
copy paths, or are they existing svn repositories?
Those are not existing svn repositories yet. Let's just say that those
project folders should be at those locations only and I want to create SVN
repositories at each of th
If I understand you correctly this would mean that somebody (user/developer)
has to checkout the code for each of the projects from the repository
location (say C:\svn\data\repositories) to:
C:\data\project1
C:\project\bluecat
C:\software\abc
so that the above locations reflect the latest code?
So the concepts of trunks, branches, tags are transparent to SVN. We are in
a situation where we might need to have two trunks in one SVN repository.
The reason is that we have a family of projects - say ProjectA, ProjectB,
ProjectC and so on, each one has it's own repository and have just one trun
I am thinking something like this:
ProjectD
ProjectD/PartA/trunk
ProjectD/PartA/tags
ProjectD/PartA/branches
ProjectD/PartB/trunk
ProjectD/PartB/tags
ProjectD/PartB/branches
Beleive me or not in our scenario the code of Part A and Part B never gets
merged at any point. The only common part is tha
store binary objects
too) in my proposed repostiroy structure?
I would like this to be as simple as it can be because the developers/users
of this system are not very SVN savvy.
Thanks!
On Thu, Sep 9, 2010 at 1:43 PM, Itamar O wrote:
> On Thu, Sep 9, 2010 at 11:23 PM, Tech Geek wrote:
>
Geoff,
I think I am beginning to undestand what you are suggesting.
Right now I am in process of implementing this setup. At this point nothing
exits - no ProjectD, no PartA and no PartB. So I will try to summarize what
I have undestood so far:
1. All our SVN repositories lives under the followi
>In SVN a working copy does not include the revision history, which remains
on the server (as opposed to Git or Hg).
Yes. I am aware of that.
> In order to see a revision graph (TortoiseSVN feature), you need to
communicate with the repository.
Yes. True.
>In fact, you don't even need a working c
For some reasons this message was returned to me by the mailer daemon. So
resending it again.
>In SVN a working copy does not include the revision history, which remains
on the server (as opposed to Git or Hg).
Yes. I am aware of that.
> In order to see a revision graph (TortoiseSVN feature), you
I have the subversion server running on a Debian Linux machine. The
repositories are residing on a Windows domain shared network drive on the
network which is mapped on the Linux machine as:
mount -t cifs //software/svn_repositories /var/lib/svn/ -o
username=mynet/techgeek,password=**,uid=www-d
>I don't know what the repository version numbers are that correspond to
each svn/TSVN version (and you didn't mention which >versions you have
installed).
Linux SVN Server version 1.5.1 (r32289)
TSVN - 1.6.10 (32-bit)
Daniel,
> Or do (the Tortoise equivalent of) 'svnadmin create --pre-1.6-compatible'
>
Actually I would prefer to do the other way around. Can we tell TSVN to
create repositories which are compatible with Subversion Engine 1.5 because
we would be usually creating repositories using the TSVN.
AFA
>
> Do not put your repository on a shared drive. Do not use file:
>> protocol to access it. It is not designed to work in such way. Read
>> the documentation (aka svnbook) and configure a proper server.
>
>
> This should be emphasized more. Although the OP said he wanted the users
> to be able
Les,
> The point remains that if they have write access through mapped files,
>> they have the capability of destroying everything there.
>>
>> You could probably whip up a cgi script to create new repositories from a
>> web request form if something like that doesn't already exist. Or you coul
OK guys so I ended up upgrading the subversion server to 1.6.12 the same as
TortoiseSVN is built against.
Now I am able to checkout the repositories through TSVN but whenever I try
to commit I get the following error message:
$Commit failed (details follow):
$Couldn't perform atomic initialization
I also experimented with http:// protocol and the same error message. I have
spent last 2 days just working on these issues and here is what I would like
to summarize:
1. Repositories created on shared network drive with 1.6.12 subversion
engine (svnadmin) or 1.6.10 TSVN, will not commit through T
Neil,
> Not that I can help, but I wanted to clarify: you have a repo on a
> CIFS-mounted shared drive, and are then using a Linux SVN server?
>
Yes that is correct.
Although I admit that may not always be practical, esp. in an enterprise (we
> plan to move to using NFS-mapped repos. when our S
>
> Can you actually use a new repository created by svnadmin 1.5 with your
> 1.6.12 server install? Or is it just previous repositories that are working?
>
>
Yes. With my 1.6.12 server install, if I create a new repository like this:
#svnadmin create --pre-1.6-compatible myproject
then it works
I have a repository called "sandbox" whose HEAD is at revision 20. I would
like to dump revisions 1 to15 and then from 18 to19. Basically I want to
skip revision 16,17 and 20.
The command:
# svnadmin dump -r 1:15 -r 18:19 sandbox > sanbox-dumpfile
gives error message:
svnadmin: Multiple revision
We use one repository per project. All repository lives in /var/lib/svn/.
Also we use the hooks post-commit and pre-commit for every repository. Right
now we have to manually copy these two hooks whenever a new repository is
created.
For example:
cd /var/lib/svn/
cp /path-to-my-hooks/* projectA/ho
Thank you all for sharing the information. Really appreciate it.
Ryan,
> sudo -u "$USER" ln -s ../../conf "$REPO" || exit $?
> sudo -u "$USER" ln -s ../../hooks "$REPO" || exit $?
>
I just realized that the above two commands will fail, if the repositories
are on a SMB/CIFS mounted share on the Linux system, with the following
message:
ln: creating symbolic li
>$SVNLOOK changed -t $2 $1 | grep "/tags/" && /bin/echo "Cannot commit to
tags" 1>&2 && exit 1
I had a question regarding the above command. How do we know what value is
going to be passed in $2 i.e. the name of the transaction so that we can
test/debug our script. Can we somehow simulate the above
>
> svnadmin dump -r 1:15 sandbox > sandbox-dumpfile
> svnadmin dump -r 18:19 sandbox > sandbox-dumpfile2
>
> Then when it comes time to load, load the first file, then the second
Tried but does not work...
# svnadmin load sandbox-restore < sandbox-dumpfile
The above command restored it up to 15
I have an exisiting repository at /var/lib/svn/projectA with (tags,
branches, trunk structure) whose HEAD is at Revision 25
I just created a new/fresh repository at /var/lib/svn/projectB with (tags,
branches, trunk structure) whose HEAD is at Revision 1 (because of importing
the tags, branches and
>
> and load project a as project b and take all the history with you.
> Just create a new project b without adding trunk etc. in revision 1.
>
I do not want all the revision history of projectA into projectB. I just
need to start projectB with the latest code (trunk HEAD of) projectA.
May be I am
56 matches
Mail list logo
