Re: viewing svn logs?

[Chris Shelton]

Tom,

On Fri, Aug 6, 2010 at 11:58 AM, Tom Cruickshank wrote:

> Preferably real-time (or scheduled).
>
> ie, file(s) get added/committed/updated, etc to the svn server, and viewer
> automatically displays the latest entries.
>
> As long as each piece of information is identified (ie. Revision, Comments,
> path/filename, etc) it should be ok.
>
> The viewers are technically inclined. They have an understanding of what
> subversion is already :)
>
> Tom
>
>
Trac provides all of these attributes by default in the timeline view.  It
needs to be installed on the SVN server, but does provide some basic
searching capabilities, and a nice read-only interface to a subversion
repository.

For an example, see:
http://trac.edgewall.org/timeline?from=08/06/10&daysback=7&authors=&changeset=on&repo-=on&repo-ticket-links=on&update=Update

chris

Re: add * ignores new files in subdirectories.

[Chris Shelton]

David,

On Fri, Aug 27, 2010 at 3:59 PM, David H  wrote:
>
> As a new user it was my expectation that 'svn add *' called from within the 
> root
> of my version-controlled root directory would result in *all* changes that 
> had been
> made within the file system to be scheduled for inclusion on the next commit.
>
> Instead, it ignored a whole raft of new files that were buried in 
> subdirectories.
>
> It took me a while of poking around to find this out.
>
> The behavior I expected was that "svn add *" would schedule a snapshot of the
> entire directory tree. Of course, to actually make this happen, I had to use 
> the "svn add * --force"
> option. It's also worth noting that the option "svn add * --depth infinity" 
> also did not add the files that were
> buried in the subdirectores; they were not added to be included on the next 
> commit.
>
> Why would you have subversion skip a bunch of files? That makes no sense.
>

Its likely that you are seeing the result of the default
global-ignores config value, described here:
http://svnbook.red-bean.com/nightly/en/svn.advanced.confarea.html

---
global-ignores

When running the svn status command, Subversion lists unversioned
files and directories along with the versioned ones, annotating them
with a ? character (see the section called “See an overview of your
changes”). Sometimes it can be annoying to see uninteresting,
unversioned items—for example, object files that result from a
program's compilation—in this display. The global-ignoresoption is a
list of whitespace-delimited globs that describe the names of files
and directories that Subversion should not display unless they are
versioned. The default value is *.o *.lo *.la *.al .libs *.so
*.so.[0-9]* *.a *.pyc *.pyo *.rej *~ #*# .#* .*.swp .DS_Store .

As well as svn status, the svn add and svn import commands also ignore
files that match the list when they are scanning a directory. You can
override this behavior for a single instance of any of these commands
by explicitly specifying the filename, or by using the --no-ignore
command-line flag.


chris

Re: Logging repository accesses other than commits

[Chris Shelton]

Eric,

On Fri, Apr 1, 2011 at 4:32 PM, Eric  wrote:
>
> Is there a way to maintain a log of accesses to the repository other than 
> commits?  Basically anything that results in incrementing the revision number 
> gets logged, but how do I log the event when a user downloads or checks out 
> something from the repository?
>
If you are using apache for serving your repository, this is fairly
straightforward with an extra CustomLog directive in your httpd.conf
file.  See:

http://svnbook.red-bean.com/nightly/en/svn.serverconfig.httpd.html#svn.serverconfig.httpd.extra.logging

for details.

chris

Re: Request for thoughts on working copy enhancement request

[Chris Shelton]

Randon,

On Wed, Dec 21, 2011 at 3:10 PM, Randon Spackman <
randon.spack...@hotdocs.com> wrote:

> One of my common use cases for subversion is to want to split my changes
> into two separate commits.  In the past, I would do the following:
>
> ** **
>
> **1)  **Check out
>
> **2)  **Make changes
>
> **3)  **Realize that this should be more than one commit
>
> **4)  **Copy directory “MyCode” to “MyCode2”
>
> **5)  **Revert changes I don’t want to commit yet from “MyCode2”
>
> **6)  **Commit “MyCode2”
>
> **7)  **Delete “MyCode2”
>
> **8)  **Update “MyCode”; already committed changes are merged and no
> longer appears as diffs.
>
> **9)  **Commit remaining changes in “MyCode”
>
> ** **
>
> Unfortunately, this use case is defeated by the 1.7 changes to a single
> .svn dir.  My current workarounds are as follows:
>
> **1)  **Copy the entire working copy (multiple GBs, waste of time), or
> 
>
> **2)  **Do an “svn info” to get repo and revision, then check this
> out somewhere to obtain the necessary “.svn” folder which is then copied to
> “MyCode”. 
>
> ** **
>
> Neither of these is very elegant.  I’d like to see a new svn command such
> as “svn localize” (don’t keep my terminology if it sucks) that would make
> the directory you specify its own independent working copy that can be
> copied and manipulated individually, and possibly a “svn delocalize” to
> reintegrate it.  (Although this can be accomplished less effectively by
> simply deleting the “.svn” directory and doing an update.)
>
> ** **
>
> Is there already a way to do this?  Thoughts?
>
>
>
This sounds like a good case to use changelists.  See:
http://svnbook.red-bean.com/nightly/en/svn.advanced.changelists.html
for details.

chris

Re: svnadmin

[Chris Shelton]

John

On Fri, Sep 7, 2012 at 3:47 PM, John Maher  wrote:
> Is svnadmin create limited to creating a local repository?

Yes.

> If not then how do you use it for a URL?

You don't.

> If so then is there a command for creating a repository via an URL?  Or
> is this impossible?

It is impossible to create a repository remotely.

Read the book on repository creation:
http://svnbook.red-bean.com/nightly/en/svn.reposadmin.create.html

svnadmin is a server side utility to create a repository within the
local filesystem.

chris

Re: backlogging with subversion?

[Chris Shelton]

Trac must be installed on to the same machine that serves your subversion
repository.  That should simplify your decision a bit.

chris


On Mon, Apr 29, 2013 at 12:00 PM, Ryan Tarrant wrote:

> Thanks! I'm starting to get the Trac setup on my windows client, but would
> it make more sense to put this on my linux server?
>
> Ryan J. Tarrant
> Software Engineer
> National Elevator Industry Benefit Plans
> Telephone: 1-610-325-9100 EXT. 2217
> Fax: 1-610-557-4505
> Email: rtarr...@neibenefits.org
>
> -Original Message-
> From: Cooke, Mark [mailto:mark.co...@siemens.com]
> Sent: Monday, April 29, 2013 10:31 AM
> To: users@subversion.apache.org
> Cc: Ryan Tarrant
> Subject: RE: backlogging with subversion?
>
> > -Original Message-
> > From: Ryan Tarrant [mailto:rtarr...@neibenefits.org]
> > Sent: 29 April 2013 15:19
> > To: users@subversion.apache.org
> > Subject: backlogging with subversion?
> >
> > Is there a way to do product backlogging with subversion? I'm looking
> > for a way to manage tasks associated with projects where I can
> > prioritize tasks that might hopefully be something like a plugin or
> > extension of subversion.
> >
> > Currently I have subversion running on a linux server and we're using
> > TortoiseSVN on windows clients to access the repositories.
> >
> > I'm also looking for something that is not a monthly/yearly fee. I'm
> > already hosting subversion so I would like to also host the backlog
> > with the projects themselves.
>
> Not directly in subversion but we use the Trac tool [1] which has good
> integration with subversion and was i) reasonably easy to get going and ii)
> free.  If you want to go apache, the Bloodhound [2] project takes Trac as
> its base and adds several commononly used plugins (but is not released as
> yet).
>
> [1] http://trac.edgewall.org/wiki
>
> [2] http://bloodhound.apache.org/
>
> ~ mark c
>
> > Thanks,
> >
> > Ryan J. Tarrant
> >
> > Software Engineer
> >
> > National Elevator Industry Benefit Plans
> >
> > Telephone: 1-610-325-9100 EXT. 2217
> >
> > Fax: 1-610-557-4505
> >
> > Email: rtarr...@neibenefits.org 
> >
> >
> >
> >
>

Re: Have an old SVN 1.1 DB corruption issue and need some help

[Chris Shelton]

Dana,

This page of the subversion book sounds like it might be helpful in your
situation:
http://subversion.apache.org/faq.html#wedged-repos

I am sure that switching to a FSFS repository data store with your new
system is advisable.

chris


On Fri, Aug 16, 2013 at 1:37 PM, Dana Epp  wrote:

> I have inherited a REALLY old SVN server that was mismanaged for years.
> They were using WebDAV successfully for so long they never noticed any
> issues under the hood, but the BDB is corrupt and cannot run an svnadmin
> dump on it to move it to a new server that I built that has all the latest
> SVN bits.
>
> The old system is running SVN 1.1.1 with BDB 4.2.52.
>
> At this point after following several different pieces of guidance online
> the system starts a dump, and ends up after several "Dumped revision #"
> pukes out hundreds of the following lines:
>
> svn: bdb: DB_ENV->log_flush: LSN of 56874/862249 past current end-of-log
> of 1/2786
> svn: bdb: Database environment corrupt; the wrong log files may have been
> removed or incompatible database files imported from another environment
>
> Does anyone know where I should go from here? Does anyone know of anyone
> consulting on these sort of repairs? I did a full export of the whole repro
> using WebDAV before I started this, so I have HEAD, but I don't want to
> lose the history if I don't have to.
>
> --
> Regards,
> Dana
>

Re: Looking into using Subversion

[Chris Shelton]

I would suggest looking at the SVN::Notify::Mirror perl module:
http://search.cpan.org/~jpeacock/SVN-Notify-Mirror-0.040/lib/SVN/Notify/Mirror.pm

It includes a Perl script that is intended for using within a
post-commit hook script to perform updates of a working copy after
each commit.  I have been using it for automated deployment of code
changes to a test web server for a few years now with generally
reliable results.

chris

On Mon, Nov 18, 2013 at 8:08 AM,  wrote:
>
> Thank for your response Nico.  We what to debug from our development server.  
> Not sure if
> there maybe is away to develop on the local PC, and check in the file into 
> the repository
> (which will be on the Linux Server) which will copy it to the Tomcat's 
> publish folder on
> the server?
>
>
>
> From:Nico Kadel-Garcia 
> To:vanderwalt.dev...@columbus.co.za
> Cc:Subversion 
> Date:2013/11/18 02:11 PM
> Subject:Re: Looking into using Subversion
>
> 
>
>
>
> They can, in theory, but it's awkward. Two people editing the same
> file, at the same time are really likely to run into conflicts or
> accidentally mix their changes into the same commit. So I don't
> recommend it.
>
> Why can't they work on their own copies, on their own Tomcat servers,
> with tuned local Tomcat configs, and merge their changes in their own
> branches to a single "master" that is what lives on the website?
>
> On Mon, Nov 18, 2013 at 4:09 AM,   wrote:
> > Hi All
> >
> > I have been exploring the Subversion web site, also check out the High-Speed
> > Tutorial.  But stilling trying to work out if Subversion will be useful for
> > us.
> >
> > We are developing a PHP Website hosted on our own Linux Server (a
> > development server).
> > We are also using Tomcat to host our website, and handle our Java Web
> > Services for the
> > website.
> >
> > The Developers are using Windows PC to develop, currently using, NetBeans
> > for PHP
> > development.  And Eclipse for the Java Web services.
> >
> > The question is, can all the developers, work with the same working copy,
> > which will be
> > on the Linux server?
> >
> > Enjoy
> > Devlyn

Re: Hi ; how do i get Subversion to archive a python *.pyc file

[Chris Shelton]

Robert,

On Fri, Jan 22, 2010 at 6:23 PM, Robert Somerville
 wrote:
>
> Subversion thinks it is a binary file and ignores it ...

I suspect that this is caused by the global ignore settings, as I ran
into this issue myself recently.  Try:

svn --no-ignore add myfile.pyc

chris

Re: Perl can't find my libraries when run via the subversion post-commit script

[Chris Shelton]

Craig,

On Thu, Mar 4, 2010 at 12:20 PM, Craig Thayer  wrote:

> Yes, I have tested the script on the Subversion server and it runs just fine. 
>  And I agree it is obvious that Perl is including the directories to my 
> libraries (so the use lib statements are working as designed as you stated).  
> However, it is Perl that is complaining that it can't find my libraries even 
> though they are clearly in the @INC path.  I have never run into this 
> situation before and I believe it has to do with the fact that the Subversion 
> hook is running with no environment defined, but why it makes Perl not able 
> to find my libs ONLY when it runs as a Subversion hook I haven't a clue.

Did you run the script "as the user that runs Subversion" as David
suggested?  This user is generally apache, nobody, www-data or such on
unix type systems.  The /root directory is typically setup with root
user only access, which would prevent a script running as a non-root
user from being able to access files in /root/perl5/lib.

chris

Re: Perl can't find my libraries when run via the subversion post-commit script

[Chris Shelton]

Craig,

On Fri, Mar 5, 2010 at 9:52 AM, Craig Thayer  wrote:
> Thanks again David.
>
> The reason for the post-commit hook is to pull certain files out of 
> Subversion and write them to our server. For example, if 
> tools/perl/trunk/lib/foo.pm is updated we want it to be copied to 
> /usr/lib/perl5/site_perl/foo.pm automatically upon commit.
>
> I am using the svnlook command in the script now to get the 'changed' and 
> 'info' data from the commit operation to determine if any file changed or 
> added is one that we need on our server (i.e., we're attempting to automate 
> our manual process of fetching key Subversion files and psftp'ing them to the 
> server).  The files are a mix of text and binary files.
>
> I was unaware that svnlook had a 'cat' operation, but I'm concerned that if 
> it fails in any way it will overwrite and trash the target file with its 
> error output the same way that 'svn cat' did.
>
> However, I will try it since svnlook doesn't need the credentials to extract 
> the file.

If you are able to let the web server user to create working copies,
you may want to consider using the SVN::Notify::Mirror perl module:
http://search.cpan.org/~jpeacock/SVN-Notify-Mirror-0.038/lib/SVN/Notify/Mirror.pm

I've been using this module to automate a svn update on our test web
server, which runs from a set of working copies from our repository.
The SVN::Notify module also supports the creation of very configurable
post-commit email messages.  Once I worked through the syntax of the
config file, this approach has worked well, with only a few rare
hiccups.

chris