svn factoids

the -F switch lets you put the checkin comment in a file, instead of specifying it on the command line with -m, or interactively via an editor.

--no-auth-cache disables caching only for *new* passwords/credentials
--no-auth-cache does *not* prevent already-cached credentials from being used

the -F switch lets you put the checkin comment in a file, instead of specifying it on the command line with -m, or interactively via an editor.

.NET bindings are available in SharpSvn (See http://sharpsvn.net). They include libsvn_client and a subset of the APIs from the rest of the libraries

DON'T TOUCH FILES IN ".svn"! They are not meant to be edited manually.

You can do "in-place" imports -- of, e.g., your /etc directory. See http://subversion.apache.org/faq.html#in-place-import

"svn: PROPFIND of '/some/path': 200 OK" _might_ mean that you're not accessing your Subversion repository, you're accessing some other Web page.

http://subversion.apache.org/faq.html#http-301-error

http://sergiy.kyrylkov.name/blog/2005/07/propfind-302-found-error-in-subversion.html

when you apply the difference between two URLs to a working copy: "svn merge $URL/foo $URL/bar working_copy/bar". See also "svn help merge".

maybe your proxy isn't allowing WebDAV verbs through: http://svn.haxx.se/users/archive-2004-02/0982.shtml

403 Forbidden usually means permissions problems.

405 sometimes simply means you mistyped the URL; once someone got that because they'd accidentally put dav_svn instead of mod_dav_svn in subversion.conf
remove the trailing slash in <Location /svn>

500 Internal Server Error means you need to read your Apache error log

If you have a file or URL with @ in the name, append another @ to the filename or URL to avoid it being falsely parsed as a peg revision.
http://svnbook.red-bean.com/nightly/en/svn.advanced.pegrevs.html

Apache Portable Runtime

a Subversion SCC implementation for Visual Studio 2005, 2008 and 2010 (older version for 2002 and 2003). It supports all the common Subversion operations directly from Visual Studio. Discussion about AnkhSVN happens in #ankhsvn on this network.

<book/>

http://subversion.apache.org/faq.html#proxy

http://www.timeanddate.com/weather/germany/berlin
http://www.weather.com/weather/tenday/GMXX0007
http://wetterstationen.meteomedia.de/messnetz/forecast/103840.html

Listing all repositories under SVNParentPath is described at http://svnbook.red-bean.com/nightly/en/svn.serverconfig.httpd.html#svn.serverconfig.httpd.extra.browsing.reposlisting

The complete release change log is at http://svn.apache.org/repos/asf/subversion/trunk/CHANGES

CIA is at home at http://cia.navi.cx/ . check it out. it rules.

Can't copy is http://svn.haxx.se/users/archive-2004-09/1115.shtml

http://svn.apache.org/repos/asf/subversion/trunk/CHANGES

http://svn.apache.org/repos/asf/subversion/trunk/subversion/libsvn_fs_base/notes/structure

DannyB is a gnu caveman, toolchain lawyer, and svn hacker

Subversion looks for an editor in the following places (in order):
The --editor-cmd command-line flag; the SVN_EDITOR, VISUAL, and EDITOR environment variables; the 'editor-cmd' option in the Subversion configuration file; or a built-in default.

'HACKING' is at http://subversion.apache.org/docs/community-guide/

RTFM: Real Truth comes From the Manual. http://www.svnbook.org/

http://web-cpan.berlios.de/modules/SVN-RaWeb-Light/

http://svn.elixus.org/svnweb/repos/browse/member/clkao/SVN-Web/

Be sure to understand the difference between SVNPath and SVNParentPath. Read about it here: http://svnbook.red-bean.com/nightly/en/svn.serverconfig.httpd.html#svn.serverconfig.httpd.basic

Be sure to understand the difference between SVNPath and SVNParentPath. Read about it here: http://svnbook.red-bean.com/nightly/en/svn.serverconfig.httpd.html#svn.serverconfig.httpd.basic

SVNPathAuthz is an apache directive introduced in svn 1.1.1 after fixing a security bug in 1.1.0 which caused unacceptable delays over http. See also http://svn.haxx.se/users/archive-2004-11/0271.shtml

Syntax error is "Syntax error parsing revision" when you do "svn list svn+ssh://user@host.com/"? See http://subversion.tigris.org/issues/show_bug.cgi?id=2349

Want to help out translating Subversion into other languages? Read more about it at http://subversion.apache.org/docs/community-guide/#l10n

Tortoise SVN :-)

The Subversion Book is at http://www.svnbook.org/
If that site is down try http://stsp.name/svnbook/

TortoiseSVN is a Subversion client, implemented as a windows shell extension. http://tortoisesvn.tigris.org .

an acronym for Working Copy.

^/ expands to what svn info says in the 'Repository Root:' line. This is called the caret notation and is available on the command line since 1.6.
In many shells you'll have to escape the ^ character.

^/ expands to what svn info says in the 'Repository Root:' line. This is called the caret notation and is available on the command line since 1.6.
In many shells you'll have to escape the ^ character.

I am a bot. I am written in Python, and serve factoids in #svn on freenode. My home is http://repos.borg.ch/svn/wayita/trunk/

To accept invalid SSL certificates without prompting, use 'svn --trust-server-cert'.

If you use svn+ssh:// you can avoid typing your password constantly by using ssh-agent. A nice wrapper around ssh-agent is http://www.gentoo.org/proj/en/keychain/index.xml . A nice tutorial about key based authentication can be found in http://www-106.ibm.com/developerworks/library/l-keyc.html. On Windows you should look at pageant and plink from the putty package: http://www.chiark.greenend.org.uk/~sgtatham/putty/

http://subversion.apache.org/faq.html#already-under-version-control

AnkhSVN is a Subversion SCC implementation for Visual Studio 2005, 2008 and 2010 (older version for 2002 and 2003). It supports all the common Subversion operations directly from Visual Studio. Discussion about AnkhSVN happens in #ankhsvn on this network.

Arfrever, danielsh, gstein; announce-owner@subversion.a.o

The Subversion Book is at http://www.svnbook.org/
If that site is down try http://stsp.name/svnbook/

No, they're all sleeping, I think.

No, they're all sleeping, I think.

nobody here but us zombie processes.

no. please leave a message after the tone. *beeeeeep*

no. please leave a message after the tone. *beeeeeep*

apache authorization setup is described in the Subversion book (http://svnbook.red-bean.com/nightly/en/svn.serverconfig.httpd.html#svn.serverconfig.httpd.authz)

"authz" is an abbreviation for "authorization". In the context of Subversion, it's often used to when talking about "Path Based Authorization" a.k.a. "Per-Directory Access Control" - see http://svnbook.red-bean.com/nightly/en/svn.serverconfig.pathbasedauthz.html

the documentation of the public subversion API can be found at http://subversion.apache.org/docs/api/latest/

The mailing list archives are listed here: http://subversion.apache.org/mailing-lists.html

The mailing list archives are listed here: http://subversion.apache.org/mailing-lists.html

I prefer 'electronically composed'

I have to stay home and wash my dishes

Yeah, I guess. *sigh*

In order to answer your questions we need lots of details. Things that might be relevant:
* Subversion version (client and possibly server) [svn --version will tell you about your clients version]
* which command did you run exactly? (provide a transcript if possible)
* is your repository local or on a server?
* In case of a server, which access method do you use? [svn://, http://, svn+ssh://]

asmodai is a bsd compiler guy

Subversion does not version permissions (except for the executable bit). There exists a wrapper script which you can use instead of "svn" for commit, checkout, update, etc., and store permissions in properties: http://svn.apache.org/repos/asf/subversion/trunk/contrib/client-side/asvn

authorised is spelled 'authorized' in the western hemisphere

"authz" is an abbreviation for "authorization". In the context of Subversion, it's often used to when talking about "Path Based Authorization" a.k.a. "Per-Directory Access Control" - see http://svnbook.red-bean.com/nightly/en/svn.serverconfig.pathbasedauthz.html

The mod_authz_svn metadata leak was fixed in 1.0.8 and 1.1.0-rc4, and is described at http://subversion.apache.org/security/CAN-2004-0749-advisory.txt

How to do automatic updates of websites and other server side working copies is in http://subversion.apache.org/faq.html#website-auto-update

Automatic setting of properties for particular kinds of files is described at http://svnbook.red-bean.com/nightly/en/svn.advanced.props.html#svn.advanced.props.auto

Automatic setting of properties for particular kinds of files is described at http://svnbook.red-bean.com/nightly/en/svn.advanced.props.html#svn.advanced.props.auto

Autoversioning is described in the Subversion book: http://svnbook.red-bean.com/nightly/en/svn.webdav.autoversioning.html

ayita is not here, haven't seen her for a very long time :(

ayita's source code is at http://hix.nu/svn-public/alexis/trunk/. Ask me about 'wayita source'.

ayita's source code is at http://hix.nu/svn-public/alexis/trunk/. Ask me about 'wayita source'.

ayiti is my little brother.

an opaque context object that's passed to a callback function. See http://mid.gmane.org/4D55A6E8.30103@e-reka.si
A baton always coupled with a callback. A (concrete) baton type is always coupled with a (concrete) callback type.

FSFS is a non-database back-end for the Subversion repositories. You can read about FSFS and Berkeley DB in the book at http://svnbook.red-bean.com/nightly/en/svn.reposadmin.planning.html#svn.reposadmin.basics.backends

bdb2fsfs is svnadmin create --fs-type fsfs /path/to/fsfs ; svnadmin dump -q /path/to/bdb | svnadmin load -q /path/to/fsfs; then copy across any customizations you might have in the conf/ and hooks/ directories.

configuring the bdb logs system is discussed at http://www.sleepycat.com/docs/ref/log/config.html

bdb2fsfs is svnadmin create --fs-type fsfs /path/to/fsfs ; svnadmin dump -q /path/to/bdb | svnadmin load -q /path/to/fsfs; then copy across any customizations you might have in the conf/ and hooks/ directories.

Normally, to upgrade a BDB repository 'in-place' to a new version of BDB, 'svnadmin recover' is all that's needed. For BDB 4.3 upgrades, however, see this FAQ: http://subversion.apache.org/faq.html#bdb43-upgrade

bdb2fsfs is svnadmin create --fs-type fsfs /path/to/fsfs ; svnadmin dump -q /path/to/bdb | svnadmin load -q /path/to/fsfs; then copy across any customizations you might have in the conf/ and hooks/ directories.

http://www.red-bean.com/kfogel/beautiful-code/bc-chapter-02.html

the cause of, and cure for, all life's problems

http://developer.berlios.de/docman/display_doc.php?docid=394&group_id=2

http://svn.apache.org/repos/asf/subversion/trunk/doc/user/svn-best-practices.html

bikeshed is http://subversion.apache.org/faq.html#bikeshed

The Subversion Book is at http://www.svnbook.org/
If that site is down try http://stsp.name/svnbook/

you are on a trip and want to read the svn book? but you only own a palm? no problem. check here: http://code.plkr.org/svn/

Yes, I am indeed a bot. How could you tell.

bots are wayita, ayita and lisppaste.

branching is described in a book by Brad Appleton et al (http://www.cmcrossroads.com/bradapp/acme/branching/)
Get the branch point using svn log --stop-on-copy -r 1:HEAD --limit 1 -q URL.
http://svnbook.red-bean.com/nightly/en/svn.branchmerge.html

svn log --stop-on-copy -r 1:HEAD --limit 1 -q URL

branching is described in a book by Brad Appleton et al (http://www.cmcrossroads.com/bradapp/acme/branching/)
Get the branch point using svn log --stop-on-copy -r 1:HEAD --limit 1 -q URL.
http://svnbook.red-bean.com/nightly/en/svn.branchmerge.html

branching is described in a book by Brad Appleton et al (http://www.cmcrossroads.com/bradapp/acme/branching/)
Get the branch point using svn log --stop-on-copy -r 1:HEAD --limit 1 -q URL.
http://svnbook.red-bean.com/nightly/en/svn.branchmerge.html

branching strategies are discussed in a book by Brad Appleton et al which is published at http://www.cmcrossroads.com/bradapp/acme/branching/references.html

svn log --stop-on-copy -r 1:HEAD --limit 1 -q URL

Listing all repositories under SVNParentPath is described at http://svnbook.red-bean.com/nightly/en/svn.serverconfig.httpd.html#svn.serverconfig.httpd.extra.browsing.reposlisting

Subversion repository web viewers include:
ViewVC, WebSVN, SVN::Web, Insurrection, Chora, SVN::RaWeb::Light, mod_svn_view, Trac, Collaboa, FlexySVN, perl_svn

a tool to integrate svn with bugtrackers can be found here http://sean-janus.optionpc.com/me/software/bugtraq/

- There are no bugs in Subversion, only features. :) If you find a bug, please follow the directions found at http://subversion.apache.org/docs/community-guide/issues.html#reporting-bugs

http://subversion.apache.org/buildbot

https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/subversion.conf (committers only)

http://svn.apache.org/repos/asf/subversion/trunk/subversion/bindings/swig/INSTALL

http://buildix.thoughtworks.com/

You are using osx? You have bundles under version control? And everytime you edit them they get fscked? see this link for a workaround: http://www.darcynorman.net/2004/08/18/subversion-and-eomodeld-files

http://svnbook.red-bean.com/buy/

http://svnbook.red-bean.com/buy/

cables is http://www.red-bean.com/kfogel/pix/office-setup-day/

cdr

^/ expands to what svn info says in the 'Repository Root:' line. This is called the caret notation and is available on the command line since 1.6.
In many shells you'll have to escape the ^ character.

^/ expands to what svn info says in the 'Repository Root:' line. This is called the caret notation and is available on the command line since 1.6.
In many shells you'll have to escape the ^ character.

http://svn.apache.org/repos/asf/subversion/trunk/contrib/hook-scripts/case-insensitive.py

http://svn.apache.org/repos/asf/subversion/trunk/contrib/hook-scripts/case-insensitive.py

CollabNet Enterprise Edition is a Web-based, integrated collaborative software development platform. It powers tigris.org and many other opensource projects. The latest version is 3.5 and has full Subversion support. see http://www.collab.net/ for more.

death and taxes

cfgarch is a tool which collects configuration files from different machines in order to store them within a subversion repository. http://sourceforge.net/projects/cfgarch

Changelists are a way to keep separate lists of files to be committed. See http://svnbook.red-bean.com/nightly/en/svn.advanced.changelists.html and `svn help changelist'.

Changelists are a way to keep separate lists of files to be committed. See http://svnbook.red-bean.com/nightly/en/svn.advanced.changelists.html and `svn help changelist'.

changesets are http://svnbook.red-bean.com/nightly/en/svn.branchmerge.copychanges.html#svn.branchmerge.copychanges.bestprac

#svn => http://colabti.org/irclogger/irclogger_logs/svn , #svn-dev => http://colabti.org/irclogger/irclogger_logs/svn-dev

#svn => http://colabti.org/irclogger/irclogger_logs/svn , #svn-dev => http://colabti.org/irclogger/irclogger_logs/svn-dev

chapter 4 is http://svnbook.red-bean.com/nightly/en/svn.branchmerge.html

chapter 6 covers networking a repos. It presents all possibilities and discusses them. http://svnbook.red-bean.com/nightly/en/svn.serverconfig.html

the best way to see if your permissions are ok: 'find -ls' in your repos dir

http://svnbook.red-bean.com/nightly/en/svn.tour.initial.html

find maxb, he seems to know what to do

CIA is at home at http://cia.navi.cx/ . check it out. it rules.

'rm -rf ~/.subversion/auth/svn.simple/' will remove cached usernames/passwords. (Windows: remove %APPDATA%\Subversion\auth\svn.simple)

client side hooks are not implemented in Subversion; only server side hooks are supported (atm).

windows: tortoisesvn, ankhsvn (visual studio .net) | cross platform: workbench, svn-up, subclipse (eclipse), supervision, subcommander, rapidsvn, jsvn, psvn.el, esvn, qsvn, eric3, kdesvn | OSX: scplugin, SvnX | *nix: KDevelop | If you're learning svn, it's easier for us to help you if you _don't_ use a GUI.

If you see "Connection closed unexpectedly" while using svn+ssh:, perhaps your shell is outputting stuff when you log in. That's a Bad Thing. Make sure your shell's init files only emit output if the shell is interactive.

cmpilato is C-Mike. C-Mike run. C-Mike jump. Good Mike!

the collaboa website is at http://www.collaboa.org/

gstein, Arfrever; commits-owner@subversion.a.o

configuring the bdb logs system is discussed at http://www.sleepycat.com/docs/ref/log/config.html

http://svnbook.red-bean.com/nightly/en/svn.tour.cycle.html#svn.tour.cycle.resolve

http://svnbook.red-bean.com/nightly/en/svn.tour.cycle.html#svn.tour.cycle.resolve

http://svnbook.red-bean.com/nightly/en/svn.tour.cycle.html#svn.tour.cycle.resolve

http://www.red-bean.com/svnproject/contribulyzer/

Read http://svn.haxx.se/users/archive-2004-10/0360.shtml for the issues involved with rsyncing or copying fsfs repositories.

CVS is nice, but Subversion is better ... and Subversion for CVS users is http://svnbook.red-bean.com/nightly/en/svn.forcvs.html

cvs crossover guide: http://svn.apache.org/repos/asf/subversion/trunk/doc/user/cvs-crossover-guide.html

you can emulate cvs modules with svn:externals. for more see this link http://pixel.global-banlist.de./site/svn/cvsmodules

cvs2svn is a project to convert your cvs history to Subversion; check the homepage at http://cvs2svn.tigris.org

dance

danderson is our fearless release manager!

http://article.gmane.org/gmane.comp.version-control.subversion.devel/105238

I reckon that dannas loves snow

debugging hooks is explained at http://subversion.apache.org/faq.html#hook-debugging
quick tips: use absolute path (or set $PATH, and maybe other vars needed), write a logfile, test it with "env -i"

debugging hooks is explained at http://subversion.apache.org/faq.html#hook-debugging
quick tips: use absolute path (or set $PATH, and maybe other vars needed), write a logfile, test it with "env -i"

debugging hooks is explained at http://subversion.apache.org/faq.html#hook-debugging
quick tips: use absolute path (or set $PATH, and maybe other vars needed), write a logfile, test it with "env -i"

debugging hooks is explained at http://subversion.apache.org/faq.html#hook-debugging
quick tips: use absolute path (or set $PATH, and maybe other vars needed), write a logfile, test it with "env -i"

http://svnbook.red-bean.com/nightly/en/svn.advanced.sparsedirs.html

depth bug in svn 1.6.0 and 1.6.1: http://subclipse.tigris.org/wiki/PluginFAQ#head-c861d00ee626de8b1209689a31d4c8c5ede7b87d

detecting changes is documented in the FAQ at http://subversion.apache.org/faq.html#wc-change-detection

The Subversion Development mailing list archive is at http://svn.haxx.se/dev/

gstein, khmarbaise, ewong, lorenz; dev-owner@subversion.a.o

Please don't paste in the channel, visit http://paste.lisp.org/new/svn-dev or http://pastebin.ca/ instead.

Please don't paste in the channel, visit http://paste.lisp.org/new/svn-dev or http://pastebin.ca/ instead.

http://subversion.apache.org/faq.html#diff-cmd

digest auth does not work with apache 2.0.48: upgrading recommended.

ehu is daddy

How you set up your repository is really up to you. It's a management question. See http://svnbook.red-bean.com/nightly/en/svn.reposadmin.planning.html#svn.reposadmin.projects.chooselayout for a discussion on what the Subversion team thinks is best practice.

to disable gnome keyring and kde kwallet add "password-stores =" to your ~/.subversion/config.

to disable gnome keyring and kde kwallet add "password-stores =" to your ~/.subversion/config.

To discover what version of BDB a repository is using, see: http://subversion.apache.org/faq.html#divining-bdb-version

To discover what version of BDB a repository is using, see: http://subversion.apache.org/faq.html#divining-bdb-version

http://www.sunbase.org/weirdstuff/pDont_Touch.jpg

http://svn.apache.org/repos/asf/subversion/trunk/notes/dump-load-format.txt

The most common ways to duplicate a repository are: 'svnadmin dump | svnadmin load' cycle, svnadmin hotcopy, svnsync.

Distributed version control systems --- like Subversion but without a central server. Examples: svk, git, mercurial(hg), bazaar(bzr), and friends. They can be used standalone or to interface Subversion repositories.

an absent father

http://svnbook.red-bean.com/nightly/en/svn.advanced.props.file-portability.html#svn.advanced.props.special.eol-style

svn doesn't translate eols unless explicitly instructed.
Read more this subject in the book, chapter 7 in the discussion of the svn:eol-style property.

http://svnbook.red-bean.com/nightly/en/svn.advanced.props.file-portability.html#svn.advanced.props.special.eol-style

You can do "in-place" imports -- of, e.g., your /etc directory. See http://subversion.apache.org/faq.html#in-place-import

http://winpcap.mirror.ethereal.com/301a/download.htm

svn:ignore won't ignore files that were explicitly added (use 'svn revert' or 'svn remove'). Do not use '/' in your svn:ignore patterns, you have to set svn:ignore on each dir separately. See <http://svnbook.red-bean.com/nightly/en/svn.advanced.props.special.ignore.html>.

http://lwn.net/Articles/10904/

http://svnbook.red-bean.com/nightly/en/svn.advanced.externals.html

My factoids are available as HTML ( http://svn.borg.ch/wayita/factoids.html ), in a web interface with search function ( http://svn.borg.ch/wayita/ ) and as text file in a subversion repos ( http://repos.borg.ch/svn/wayita/trunk/factoids/ ).

the faq can be found at http://subversion.apache.org/faq.html . Check it before asking a question and search the mailing list archives: http://svn.haxx.se/.

rpms for redhat and fedora core can be found on http://dag.wieers.com/packages/subversion, http://summersoft.fay.ar.us/pub/subversion/latest/ or http://people.redhat.com/jorton/.

rpms for redhat and fedora core can be found on http://dag.wieers.com/packages/subversion, http://summersoft.fay.ar.us/pub/subversion/latest/ or http://people.redhat.com/jorton/.

find + xargs rock the house: find -type f -name \*.txt -and -not -path \*/.svn/\* -print0 | xargs -r0 svn propset svn:eol-style "native"

fitz is a GoogleBot

tails!

Rather than pasting in the channel, visit http://paste.lisp.org/new/svn or http://pastebin.ca/.

http://subversion.apache.org/docs/community-guide/mailing-lists.html#fresh-post

FSFS is a non-database back-end for the Subversion repositories. You can read about FSFS and Berkeley DB in the book at http://svnbook.red-bean.com/nightly/en/svn.reposadmin.planning.html#svn.reposadmin.basics.backends

a list of pros and cons of the FSFS repository filesystem is at http://web.mit.edu/ghudson/info/fsfs

cat $REPOSPATH/db/fs-type

FSVS is a complete backup/restore/versioning tool for all files in a directory tree or whole filesystems, with a subversion repository as the backend. see http://fsvs.tigris.org/

Dispelling Subversion FUD: http://www.red-bean.com/sussman/svn-anti-fud.html

Mr. Smarty Pants (and we like it that way)

http://github.com/blog/626-announcing-svn-support

http://subversion.apache.org/faq.html#globalrev

google is http://www.google.com/

gregburd: the sleepy cat.

gstein needs more beer!

windows: tortoisesvn, ankhsvn (visual studio .net) | cross platform: workbench, svn-up, subclipse (eclipse), supervision, subcommander, rapidsvn, jsvn, psvn.el, esvn, qsvn, eric3, kdesvn | OSX: scplugin, SvnX | *nix: KDevelop | If you're learning svn, it's easier for us to help you if you _don't_ use a GUI.

heads!

hi there!

You need to tell us: 1) _exactly_ what you typed; 2) _exactly_ what you saw; 3) _exactly_ how what you saw differed from what you expected to see. Do 1) and 2) by reproducing the problem while keeping a transcript, then pasting that transcript to http://paste.lisp.org/new/svn. Unix users: the "script" program is probably the easiest way to make a transcript. This is a lot of work, but it will save time.

http://pastebin.com/WG367WiU

of course I'm here.

hello there!

http://subversion.apache.org/faq.html#hidden-log

The Subversion Book is at http://www.svnbook.org/
If that site is down try http://stsp.name/svnbook/

Keep your home directory under Subversion, like Joey do! http://www.kitenet.net/~joey/svnhome.html

debugging hooks is explained at http://subversion.apache.org/faq.html#hook-debugging
quick tips: use absolute path (or set $PATH, and maybe other vars needed), write a logfile, test it with "env -i"

Hook scripts are described at http://svnbook.red-bean.com/nightly/en/svn.reposadmin.create.html#svn.reposadmin.create.hooks

debugging hooks is explained at http://subversion.apache.org/faq.html#hook-debugging
quick tips: use absolute path (or set $PATH, and maybe other vars needed), write a logfile, test it with "env -i"

Hook scripts are described at http://svnbook.red-bean.com/nightly/en/svn.reposadmin.create.html#svn.reposadmin.create.hooks

Just get a new working copy, copy any changed-but-not-yet-checked-in files from the old working copy to the new one, commit the new working copy, and then (once you're satisfied you haven't lost any work) delete the old one. OR take a look at the various scenarios described at http://subversion.tigris.org/issues/show_bug.cgi?id=2505

hotcopy / hotbackup is there to copy a repository while possibly being accessed while keeping it consistent.

Rather than pasting in the channel, visit http://paste.lisp.org/new/svn or http://pastebin.ca/.

Much better now, thanks.

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

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

hwright can drive safe even on the left side of the road!
hwright is also a friend of stsp

http://www.apache.org/licenses/#clas

svn:ignore won't ignore files that were explicitly added (use 'svn revert' or 'svn remove'). Do not use '/' in your svn:ignore patterns, you have to set svn:ignore on each dir separately. See <http://svnbook.red-bean.com/nightly/en/svn.advanced.props.special.ignore.html>.

Don't put your config file into svn, create a template and add that one. See http://subversion.apache.org/faq.html#ignore-commit

http://subversion.apache.org/faq.html#ignore-commit

Don't put your config file into svn, create a template and add that one. See http://subversion.apache.org/faq.html#ignore-commit

importing is confusing sometimes: unlike with CVS the files won't appear in the filesystem of your server; instead, the data representing your files is stored in a custom format (this holds for both fsfs and bdb)
Also note that import does not turn the imported directory into a working copy.

You can do "in-place" imports -- of, e.g., your /etc directory. See http://subversion.apache.org/faq.html#in-place-import

You can do "in-place" imports -- of, e.g., your /etc directory. See http://subversion.apache.org/faq.html#in-place-import

You can do "in-place" imports -- of, e.g., your /etc directory. See http://subversion.apache.org/faq.html#in-place-import

an index of all my factoids is at http://svn.borg.ch/wayita/factoids.html

Listing all repositories under SVNParentPath is described at http://svnbook.red-bean.com/nightly/en/svn.serverconfig.httpd.html#svn.serverconfig.httpd.extra.browsing.reposlisting

http://svnbook.red-bean.com/nightly/en/svn.tour.initial.html

http://www.garion.org/irssi/features.php

Arfrever, prikid

Don't ask if you can ask; just ask. Don't ask if anyone has time/clue; just ask your question!

http://www.alwins-world.de/programs/kdesvn/

keep-local is Move the file out of the way before running 'svn rm', or use the --keep-local flag in the upcoming 1.5 release.

svn:keywords is http://svnbook.red-bean.com/nightly/en/svn.advanced.props.special.keywords.html

kfogel is the answer to the question "How many light-bulb jokes does it take to screw in a light-bulb?"

http://wiki.osuosl.org/display/LNX/Subversion+SVN+and++LDAP+and+Webdav

Subversion is now licensed under the Apache License. See this document for details: http://svn.apache.org/repos/asf/subversion/trunk/LICENSE

The old links page is no longer maintained, but its last existing version can be read at http://svn.apache.org/viewvc/subversion/trunk/www/links.html?revision=900404&view=co&pathrev=900404

The old links page is no longer maintained, but its last existing version can be read at http://svn.apache.org/viewvc/subversion/trunk/www/links.html?revision=900404&view=co&pathrev=900404

If no one answers here (we're sleeping or don't know the answer), feel free to post a question to the public users@subversion.apache.org mailing list. Please read http://subversion.apache.org/mailing-lists.html before posting. Thanks!

Posting to the svn mailing lists doesn't require subscription. It may just take some extra time to leak into the list because of moderating unsubscribed posters.

Listing all repositories under SVNParentPath is described at http://svnbook.red-bean.com/nightly/en/svn.serverconfig.httpd.html#svn.serverconfig.httpd.extra.browsing.reposlisting

http://svnbook.red-bean.com/nightly/en/svn.advanced.locking.html

#svn-dev is logged at http://colabti.org/irclogger/irclogger_logs/svn-dev

'svn log --diff' in 1.7; https://svn.apache.org/repos/asf/subversion/trunk/tools/client-side/showchange.pl in any version.

http://subversion.apache.org/faq.html#log-in-source

channel logs are kept at http://colabti.de/irclogger/irclogger_logs

known working scripts for mailing commit messages and stuff are: mailer.py/commit-email.pl. those can be found in the svn repository under tools/hook-scripts. svnmailer (ayita: svnmailer?) or http://commitmessage.tigris.org

known working scripts for mailing commit messages and stuff are: mailer.py/commit-email.pl. those can be found in the svn repository under tools/hook-scripts. svnmailer (ayita: svnmailer?) or http://commitmessage.tigris.org

http://svn.apache.org/repos/asf/subversion/trunk/tools/hook-scripts/mailer/

http://svn.apache.org/repos/asf/subversion/trunk/tools/hook-scripts/mailer/

No. Get your own.

http://www.red-bean.com/kfogel/maltron.html

Merging is explained in one key section of the svnbook: http://svnbook.red-bean.com/nightly/en/svn.branchmerge.html

Merging is explained in one key section of the svnbook: http://svnbook.red-bean.com/nightly/en/svn.branchmerge.html

white
not black

a sample script for mirroring svn and a lot of links about it it can be found on http://pixel.global-banlist.de./svnmirror.sh.txt . the script is now available via the svn repository as well see: http://svn.apache.org/repos/asf/subversion/trunk/contrib/server-side/svnmirror.sh

missing or not locked is ".svn directories have been improperly tampered with, or svn has a bug". It's also rumoured that doing a merge, but passing the wrong revision numbers, can trigger this.

missing or not locked is ".svn directories have been improperly tampered with, or svn has a bug". It's also rumoured that doing a merge, but passing the wrong revision numbers, can trigger this.

http://svnbook.red-bean.com/nightly/en/svn.basic.in-action.html#svn.basic.in-action.mixedrevs
mixed revs

http://svnbook.red-bean.com/nightly/en/svn.basic.in-action.html#svn.basic.in-action.mixedrevs

The Mailing List Archives are at http://svn.haxx.se/

The Mailing List Archives are at http://svn.haxx.se/

mod_authz_svn is described at http://svnbook.red-bean.com/nightly/en/svn.serverconfig.httpd.html#svn.serverconfig.httpd.authz.perdir

http://www.outoforder.cc/projects/apache/mod_highlight/

mod_macro is very helpful if you need to administer complex setups. examples can be found here: http://pixel.global-banlist.de./files/svn/svn_and_mod_macro.txt

http://www.outoforder.cc/projects/apache/mod_svn_view/

http://www.outoforder.cc/projects/apache/mod_umask/

gstein, arfrever, danielsh, khmarbaise, ewong, and others (contact $list-owner@ directly if needed)

If you access a repository from different user accounts, be sure to understand this section in the book: http://svnbook.red-bean.com/nightly/en/svn.serverconfig.multimethod.html

http://subversion.apache.org/faq.html#need-apache

neels is my friend :)

The neon debug layer is turned on client-side in your ~/.subversion/servers file, by the option "neon-debug-mask = 130". Look at the commented example in the default "servers" file. (This only makes sense when you use neon, http:// URL scheme)

chapter 6 covers networking a repos. It presents all possibilities and discusses them. http://svnbook.red-bean.com/nightly/en/svn.serverconfig.html

http://subversion.apache.org/faq.html#adm-dir

- If no one answers here (we're sleeping or helpless), feel free to post a question to the public users-at-subversion.apache.org mailinst list. Please read http://subversion.apache.org/mailing-lists.html before posting. Thanks!
If no one answers here (we're sleeping or don't know the answer), feel free to post a question to the public users@subversion.apache.org mailing list. Please read http://subversion.apache.org/mailing-lists.html before posting. Thanks!

To make --no-auth-cache permanent set "store-passwords" (and maybe also "store-auth-creds") to "no" in ~/.subversion/config (on Windows something like ...\Application Data\Subversion\config) and delete the cache file in ~/.subversion/auth/svn.simple (see also http://svnbook.red-bean.com/en/1.1/ch07.html#svn-ch-7-sect-1.3.2 ).

a friend of stsp
a friend of danilesh

You don't have to subscribe, just post. If you haven't posted before, your first post will go via a moderator.

missing or not locked is ".svn directories have been improperly tampered with, or svn has a bug". It's also rumoured that doing a merge, but passing the wrong revision numbers, can trigger this.

Anybody who finds their needs aren't served well with Subversion or even the centralized model should not be using svn. We encourage them to use other software and *not* stay with svn. for example svk.

basically the answer is ... "no". svn will never forget about stuff. but under some conditions you can force the amnesia. see this FAQ: http://subversion.apache.org/faq.html#removal , and also http://subversion.tigris.org/issues/show_bug.cgi?id=516

ignorant of apache, and despite previous reports, is neither proud nor ashamed of that fact

ojacobson is frustrated.

The old links page is no longer maintained, but its last existing version can be read at http://svn.apache.org/viewvc/subversion/trunk/www/links.html?revision=900404&view=co&pathrev=900404

opaque collections are long time overdue; there is even an issue for them: http://subversion.tigris.org/issues/show_bug.cgi?id=707

p4 is short for perforce

packages for various platforms/distributions can be found on http://subversion.apache.org/packages.html

pagaent is a nice ssh-agent for windows; see http://the.earth.li/~sgtatham/putty/latest

For svn+ssh:// on Windows we recommand PuTTY's plink and pageant. Both can be found at http://www.chiark.greenend.org.uk/~sgtatham/putty/

you are on a trip and want to read the svn book? but you only own a palm? no problem. check here: http://code.plkr.org/svn/

passwords is http://subversion.apache.org/faq.html#plaintext-passwords

Rather than pasting in the channel, visit http://paste.lisp.org/new/svn or http://pastebin.ca/.

Rather than pasting in the channel, visit http://paste.lisp.org/new/svn or http://pastebin.ca/.

Rather than pasting in the channel, visit http://paste.lisp.org/new/svn or http://pastebin.ca/.

http://subversion.apache.org/docs/community-guide/general.html#patches

Problem Exists Between Keyboard And Chair

peg revisions is you look at logs for files that aren't present in HEAD: http://svnbook.red-bean.com/nightly/en/svn.advanced.pegrevs.html

peg revisions is you look at logs for files that aren't present in HEAD: http://svnbook.red-bean.com/nightly/en/svn.advanced.pegrevs.html

peg revisions is you look at logs for files that aren't present in HEAD: http://svnbook.red-bean.com/nightly/en/svn.advanced.pegrevs.html

http://svnbook.red-bean.com/nightly/en/svn.advanced.pegrevs.html

http://subversion.apache.org/faq.html#permissions

A nice tutorial about setting up permissions for svn repositories can be found at http://pixel.global-banlist.de./svn/permissions . It is mainly for bdb users, but it doesnt harm fsfs users either. :) For the basics, see http://svnbook.red-bean.com/nightly/en/svn.serverconfig.multimethod.html

BerkeleyDB can get 'wedged' for a number of reasons, ususally because of bad permissions or ownership. Read this FAQ, and the various links it points to: http://subversion.apache.org/faq.html#stuck-bdb-repos

pong

pinky: are you pondering what I'm pondering?!

For ssh+svn:// on Windows we recommand PuTTY's plink and pageant. Both can be found at http://www.chiark.greenend.org.uk/~sgtatham/putty/

svnserve, by default, listens on port 3690 (check http://svnbook.red-bean.com/nightly/en/svn.serverconfig.svnserve.html if you don't believe me)

Producing Open Source Software - How to Run a Successful Free Software Project (http://producingoss.com/)

http://svn.apache.org/repos/asf/subversion/trunk/contrib/hook-scripts/case-insensitive.py

gstein, danielsh; private-owner@subversion.a.o

https://svn.apache.org/repos/private/subversion/pmc/

the faq can be found at http://subversion.apache.org/faq.html . Check it before asking a question and search the mailing list archives: http://svn.haxx.se/.

packages for various platforms/distributions can be found on http://subversion.apache.org/packages.html

http://www.red-bean.com/dav/sussman/proofbypoem

Properties are explained in http://svnbook.red-bean.com/nightly/en/svn.advanced.props.html

http://subversion.apache.org/faq.html#proxy

python is cool

In order to answer your questions we need lots of details. Things that might be relevant:
* Subversion version (client and possibly server) [svn --version will tell you about your clients version]
* which command did you run exactly? (provide a transcript if possible)
* is your repository local or on a server?
* In case of a server, which access method do you use? [svn://, http://, svn+ssh://]

It is always more useful to ask a direct question, than to ask if there are people around to answer a question.

A Quick Start guide is part of the Subversion Book: http://svnbook.red-bean.com/nightly/en/svn.intro.quickstart.html

Fourty-two.

http://people.apache.org/~danielsh/svnrev?r%ld

The svn:// protocol is documented at https://svn.apache.org/repos/asf/subversion/trunk/libsvn_ra_svn/protocol

rabbits are small

Offby1's rather outdated rantings on GUI clients is at http://docs.google.com/View?docid=dgp7832_2f6pxbq.

http://subversion.apache.org/faq.html#readonly

http://subversion.apache.org/faq.html#readonly

shut down all process -> run svnadmin recover on the repos -> the 'hanging' bit ususally means a leftover lock on db.lock, hence the "copy and recover" trick, the 'db_recover -vech' is what we recommend when svnadmin recover recommends running recovery.

BerkeleyDB can get 'wedged' for a number of reasons, ususally because of bad permissions or ownership. Read this FAQ, and the various links it points to: http://subversion.apache.org/faq.html#stuck-bdb-repos

shut down all process -> run svnadmin recover on the repos -> the 'hanging' bit ususally means a leftover lock on db.lock, hence the "copy and recover" trick, the 'db_recover -vech' is what we recommend when svnadmin recover recommends running recovery.

rpms for redhat and fedora core can be found on http://dag.wieers.com/packages/subversion, http://summersoft.fay.ar.us/pub/subversion/latest/ or http://people.redhat.com/jorton/.

rpms for redhat and fedora core can be found on http://dag.wieers.com/packages/subversion, http://summersoft.fay.ar.us/pub/subversion/latest/ or http://people.redhat.com/jorton/.

a svn refcard can be found at http://tinyurl.com/6nraa

When you're done with development on a branch, you reintegrate it to its main line of development (e.g. trunk): http://svnbook.red-bean.com/nightly/en/svn.branchmerge.basicmerging.html#svn.branchemerge.basicmerging.reintegrate
If you don't want to delete a reintegrated branch, see http://svnbook.red-bean.com/nightly/en/svn.branchmerge.advanced.html#svn.branchmerge.advanced.reintegratetwice
If you want to know why --reintegrate is necessary, see http://mail-archives.apache.org/mod_mbox/subversion-users/201009.mbox/%3C20100929200923.GC7378@ted.stsp.name%3E

If the address of the repository has changed, and you want to make your working copies use it, use the command "svn switch --relocate OLD_URL NEW_URL [PATH]". The svn switch command is documented at http://svnbook.red-bean.com/nightly/en/svn.ref.svn.c.switch.html

basically the answer is ... "no". svn will never forget about stuff. but under some conditions you can force the amnesia. see this FAQ: http://subversion.apache.org/faq.html#removal , and also http://subversion.tigris.org/issues/show_bug.cgi?id=516

How you set up your repository is really up to you. It's a management question. See http://svnbook.red-bean.com/nightly/en/svn.reposadmin.planning.html#svn.reposadmin.projects.chooselayout for a discussion on what the Subversion team thinks is best practice.

- There are no bugs in Subversion, only features. :) If you find a bug, please follow the directions found at http://subversion.apache.org/docs/community-guide/issues.html#reporting-bugs

How you set up your repository is really up to you. It's a management question. See http://svnbook.red-bean.com/nightly/en/svn.reposadmin.planning.html#svn.reposadmin.projects.chooselayout for a discussion on what the Subversion team thinks is best practice.

http://subversion.apache.org/faq.html#permissions

http://svnbook.red-bean.com/nightly/en/svn.serverconfig.multimethod.html

http://svn.apache.org/repos/asf/subversion/trunk/notes/repos_upgrade_HOWTO

http://svn.apache.org/repos/asf/subversion/trunk/notes/repos_upgrade_HOWTO

How you set up your repository is really up to you. It's a management question. See http://svnbook.red-bean.com/nightly/en/svn.reposadmin.planning.html#svn.reposadmin.projects.chooselayout for a discussion on what the Subversion team thinks is best practice.

You need to tell us: 1) _exactly_ what you typed; 2) _exactly_ what you saw; 3) _exactly_ how what you saw differed from what you expected to see. Do 1) and 2) by reproducing the problem while keeping a transcript, then pasting that transcript to http://paste.lisp.org/new/svn. Unix users: the "script" program is probably the easiest way to make a transcript. This is a lot of work, but it will save time.

http://svnbook.red-bean.com/nightly/en/svn.tour.cycle.html#svn.tour.cycle.resolve

http://svnbook.red-bean.com/nightly/en/svn.tour.cycle.html#svn.tour.cycle.resolve

resurrect is http://svnbook.red-bean.com/nightly/en/svn.branchmerge.basicmerging.html#svn.branchmerge.basicmerging.resurrect

resurrecting deleted items: http://svnbook.red-bean.com/nightly/en/svn.branchmerge.advanced.html#svn.branchmerge.advanced.resurrect

Undoing Changes is described at http://svnbook.red-bean.com/nightly/en/svn.branchmerge.basicmerging.html#svn.branchmerge.basicmerging.undo

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

http://subversion.apache.org/roadmap.html

rpms for redhat and fedora core can be found on http://dag.wieers.com/packages/subversion, http://summersoft.fay.ar.us/pub/subversion/latest/ or http://people.redhat.com/jorton/.

rsvn is a python script which allows multiple repository-side operations in a single, atomic transaction. https://opensvn.csie.org/traccgi/rsvn/trac.cgi/wiki

Read http://svn.haxx.se/users/archive-2004-10/0360.shtml for the issues involved with rsyncing or copying fsfs repositories.

RTFM: Real Truth comes From the Manual. http://www.svnbook.org/

rule #12: never let people without clue make decisions.

rule #12.a: never work for someone who doesn't have a clue (TTimo)

sabor is my boss

http://svnbook.red-bean.com/nightly/en/svn.serverconfig.svnserve.html#svn.serverconfig.svnserve.sasl

http://subversion.apache.org/faq.html#self-tree-conflict

selinux can cause additional trouble with svn. you can read at http://subversion.apache.org/faq.html#reposperms how to properly configure selinux.

a nice tutorial to setup a svn server on windows can be found at http://tortoisesvn.sourceforge.net/docs/release/TortoiseSVN_en/ch03.html

http://svnbook.red-bean.com/nightly/en/svn.serverconfig.html

sex has something to do with birds and bees and flowers.

bad

Paste the commands (and any errors) in a pastebin where we can see it.

gstein's masterpiece.

https://svn.apache.org/repos/asf/subversion/site/

how to ask questions the smart way: http://www.catb.org/~esr/faqs/smart-questions.html

An excellent book about SSH is at http://snailbook.com

sonda is my friend

ayita's source code is at http://hix.nu/svn-public/alexis/trunk/. Ask me about 'wayita source'.

of course I can handle spaces in keys!

Rather than pasting in the channel, visit http://paste.lisp.org/new/svn or http://pastebin.ca/.

http://svnbook.red-bean.com/nightly/en/svn.advanced.sparsedirs.html

http://svnbook.red-bean.com/nightly/en/svn.advanced.sparsedirs.html

http://svnbook.red-bean.com/nightly/en/svn.advanced.sparsedirs.html

http://svnbook.red-bean.com/nightly/en/svn.advanced.sparsedirs.html

http://svn.apache.org/repos/asf/subversion/trunk/notes/sql-backend

If you use svn+ssh:// you can avoid typing your password constantly by using ssh-agent. A nice wrapper around ssh-agent is http://www.gentoo.org/proj/en/keychain/index.xml . A nice tutorial about key based authentication can be found in http://www-106.ibm.com/developerworks/library/l-keyc.html. On Windows you should look at pageant and plink from the putty package: http://www.chiark.greenend.org.uk/~sgtatham/putty/

If you use svn+ssh:// you can avoid typing your password constantly by using ssh-agent. A nice wrapper around ssh-agent is http://www.gentoo.org/proj/en/keychain/index.xml . A nice tutorial about key based authentication can be found in http://www-106.ibm.com/developerworks/library/l-keyc.html. On Windows you should look at pageant and plink from the putty package: http://www.chiark.greenend.org.uk/~sgtatham/putty/

http://svnbook.red-bean.com/nightly/en/svn.serverconfig.svnserve.html#svn.serverconfig.svnserve.sshtricks
http://svn.apache.org/repos/asf/subversion/trunk/notes/ssh-tricks

If you use svn+ssh:// you can avoid typing your password constantly by using ssh-agent. A nice wrapper around ssh-agent is http://www.gentoo.org/proj/en/keychain/index.xml . A nice tutorial about key based authentication can be found in http://www-106.ibm.com/developerworks/library/l-keyc.html. On Windows you should look at pageant and plink from the putty package: http://www.chiark.greenend.org.uk/~sgtatham/putty/

http://svnbook.red-bean.com/nightly/en/svn.serverconfig.svnserve.html#svn.serverconfig.svnserve.sshtricks
http://svn.apache.org/repos/asf/subversion/trunk/notes/ssh-tricks

To accept invalid SSL certificates without prompting, use 'svn --trust-server-cert'.

SSPI FAQ at http://subversion.apache.org/faq.html#sspi

you can find static binaries for linux/macosx/sparc at http://www.uncc.org/svntools/clients/

subversion-bot: stop build "svn-debian-x86_64-32 shared gcc" wayita
subversion-bot: stop build svn-slik-w2k3-x64-local wayita
subversion-bot: stop build svn-slik-w2k3-x64-ra wayita
subversion-bot: stop build svn-trunk-rat-report wayita
subversion-bot: stop build "svn-x64-centos gcc" wayita
subversion-bot: stop build "svn-x64-ubuntu gcc" wayita
subversion-bot: stop build "svn-x86-macosx-gnu shared" wayita
subversion-bot: stop build "svn-x86-macosx-gnu shared daily ra_serf" wayita

Subversion does not version permissions. There exists a wrapper script which you can use instead of "svn" for commit, checkout, update, etc., and store permissions in properties: http://svn.apache.org/repos/asf/subversion/trunk/contrib/client-side/asvn

Subversion does not version permissions. There exists a wrapper script which you can use instead of "svn" for commit, checkout, update, etc., and store permissions in properties: http://svn.apache.org/repos/asf/subversion/trunk/contrib/client-side/asvn

There's an article, "Understanding Strict Aliasing", at: http://www.cellperformance.com/mike_acton/2006/06/understanding_strict_aliasing.html

I like stsp

BerkeleyDB can get 'wedged' for a number of reasons, ususally because of bad permissions or ownership. Read this FAQ, and the various links it points to: http://subversion.apache.org/faq.html#stuck-bdb-repos

BerkeleyDB can get 'wedged' for a number of reasons, ususally because of bad permissions or ownership. Read this FAQ, and the various links it points to: http://subversion.apache.org/faq.html#stuck-bdb-repos

Subversion is a Next-Generation Open Source Version Control System: http://subversion.apache.org/

The Subversion Book is at http://www.svnbook.org/
If that site is down try http://stsp.name/svnbook/

http://subversionary.org/

BLT okay for you?

No, not yet, please.

a viking

waiting for ayita

sussbot is a lobotomized eliza.

sussman is mostly harmless.

svk is a decentralized version control system written in Perl. It uses the Subversion repository and is somewhat interoperable with regular Subversion, but provides additional powerful features. http://svk.elixus.org (Its mystery is only exceeded by its power.)

svkantifud is http://svk.elixus.org/?SVKAntiFUD

svl is p2p svk. for more see http://crucially.typepad.com/

Subversion is a Next-Generation Open Source Version Control System: http://subversion.apache.org/

http://search.cpan.org/~infinoid/App-SVN-Bisect-1.1/bin/svn-bisect

The Subversion Book is at http://www.svnbook.org/
If that site is down try http://stsp.name/svnbook/

a forum about svn can be found on http://www.svnforum.org/

Subversion is now licensed under the Apache License. See this document for details: http://svn.apache.org/repos/asf/subversion/trunk/LICENSE

svn port is 3690

ayita's source code is at http://hix.nu/svn-public/alexis/trunk/. Ask me about 'wayita source'.

Packaged source code for Subversion can be found on http://subversion.apache.org/source-code.html#source-release

To find support for Subversion, check http://tinyurl.com/acqg8

http://svn.apache.org/repos/asf/subversion/trunk

http://search.cpan.org/~infinoid/App-SVN-Bisect-1.1/bin/svn-bisect

svn-load is a useful tool for loading a series of versioned directories into a Subversion repository. http://packages.debian.org/unstable/devel/svn-load

Access to a repository via svn+ssh:// does NOT involve any svnserve daemon or inetd setup you may have on the server in ANY WAY WHATSOEVER!
Individual svnserve processes are spawned by ssh for each connection, and they WILL NOT be magically aware of any arguments - including --root (-r) - that you may be specifying in your daemon startup or inetd.conf file.

http://svnbook.red-bean.com/nightly/en/svn.advanced.props.file-portability.html#svn.advanced.props.special.eol-style

http://svnbook.red-bean.com/nightly/en/svn.advanced.externals.html

http://svnbook.red-bean.com/nightly/en/svn.advanced.externals.html

svn:ignore won't ignore files that were explicitly added (use 'svn revert' or 'svn remove'). Do not use '/' in your svn:ignore patterns, you have to set svn:ignore on each dir separately. See <http://svnbook.red-bean.com/nightly/en/svn.advanced.props.special.ignore.html>.

svn:keywords is http://svnbook.red-bean.com/nightly/en/svn.advanced.props.special.keywords.html

svn_load_dirs is http://svn.apache.org/repos/asf/subversion/trunk/contrib/client-side/svn_load_dirs/

svnadmin is http://svnbook.red-bean.com/nightly/en/svn.reposadmin.maint.html#svn.reposadmin.maint.tk.svnadmin

The Subversion Book is at http://www.svnbook.org/
If that site is down try http://stsp.name/svnbook/

monthly svnbook mirror: http://svn.borg.ch/

http://svnbook.red-bean.com/nightly/en/svn.reposadmin.maint.html#svn.reposadmin.maint.tk.svndumpfilter

svndumptool is a cool tool to mangle dump files. see http://svn.borg.ch/svndumptool/

http://svnbook.red-bean.com/nightly/en/svn.reposadmin.maint.html#svn.reposadmin.maint.tk.svnlook

Svnmailer is a tool to post subversion repository commit information by mail, news or XML (to a CIA tracker). For more see http://opensource.perlig.de/svnmailer/

http://www.orcaware.com/svn/wiki/Svnmerge.py

a sample script for mirroring svn and a lot of links about it it can be found on http://pixel.global-banlist.de./svnmirror.sh.txt . the script is now available via the svn repository as well see: http://svn.apache.org/repos/asf/subversion/trunk/contrib/server-side/svnmirror.sh

svnmucc can combine a list of mv, cp and rm commands on URLs into a single commit. http://svn.apache.org/repos/asf/subversion/trunk/tools/client-side/svnmucc/

http://svn.apache.org/repos/asf/subversion/trunk/tools/hook-scripts/svnperms.py

http://svn.apache.org/repos/asf/subversion/trunk/tools/hook-scripts/svnperms.py

svnpubsub is a hook script that advertises commits via streaming json/xml as they happen. https://svn.apache.org/repos/infra/infrastructure/trunk/projects/svnpubsub

svnrdump is the equivalent of 'svnadmin dump' and 'svnadmin load' for remote repositories (http:// or svn:// repositories, as opposed to ones on local disk). It is available in Subversion 1.7 and newer.

'svnserve', the dedicated protocol Subversion server, is documented at http://svnbook.red-bean.com/nightly/en/svn.serverconfig.svnserve.html

svnserve auth is Uncomment anon-access, auth-access, and password-db in svnserve.conf and try again.

http://svn.apache.org/repos/asf/subversion/trunk/notes/svnsync.txt
svnsync is a mature (available since Subversion 1.4) for keeping incrementally-updated repository mirrors or for downloading remote repositories with history. See the book for details (http://www.svnbook.org/).

http://svn.apache.org/repos/asf/subversion/trunk/notes/svnsync.txt
svnsync is a mature (available since Subversion 1.4) for keeping incrementally-updated repository mirrors or for downloading remote repositories with history. See the book for details (http://www.svnbook.org/).

http://repos.borg.ch/svn/svntar/trunk/

A collection of utilities for Subversion. http://svnutils.tigris.org

svnversion is the most reliable way to get version information into your built program. http://svnbook.red-bean.com/nightly/en/svn.ref.svnversion.re.html

t-shirts are available at http://www.cafepress.com/subversion

http://svnbook.red-bean.com/nightly/en/svn.branchmerge.tags.html

Packaged source code for Subversion can be found on http://subversion.apache.org/source-code.html#source-release

Don't put your config file into svn, create a template and add that one. See http://subversion.apache.org/faq.html#ignore-commit

that's all right

The Subversion Book is at http://www.svnbook.org/
If that site is down try http://stsp.name/svnbook/

the book chapter on vendor branches is located at http://svnbook.red-bean.com/nightly/en/svn.advanced.vendorbr.html

FSFS, symlink support, and history-tracing for commands like "svn diff -rN file".

Programming today is a race between software engineers striving to build bigger and better idiot-proof programs and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.

the trac homepage is at http://www.edgewall.com/trac/

of course I'm here.

http://www.cafeshops.com/subversion.4410563

when you apply the difference between two URLs to a working copy: "svn merge $URL/foo $URL/bar working_copy/bar". See also "svn help merge".

the trac homepage is at http://www.edgewall.com/trac/

a script to track changes from cvs into a read only svn can be found at https://open.datacore.ch/DCwiki.open/Wiki.jsp?page=CVS2SVNtracking. 14:35:53 <clkao> you could also try svk mirror from cvs. it works quite well these days. 02:40:30 < autrijus> darix: care to add the http://svk.elixus.org/?MirrorVCP link?

a transcript is an exact cut-and-paste of the commands you typed, and the resulting output. developers need to see transcripts to diagnose problems. It's very hard to help people without them, since anecdotal descriptions of problems tend to accidentally leave out information.

a transcript is an exact cut-and-paste of the commands you typed, and the resulting output. developers need to see transcripts to diagnose problems. It's very hard to help people without them, since anecdotal descriptions of problems tend to accidentally leave out information.

To get English error messages, set the environment variable "LC_ALL" to "C". (Unix: export LC_ALL=C; windows: SET LC_ALL=C)

Want to help out translating Subversion into other languages? Read more about it at http://subversion.apache.org/docs/community-guide/#l10n

Want to help out translating Subversion into other languages? Read more about it at http://subversion.apache.org/docs/community-guide/#l10n

http://svnbook.red-bean.com/nightly/en/svn.tour.treeconflicts.html

http://svnbook.red-bean.com/nightly/en/svn.tour.treeconflicts.html

https://launchpad.net/distros/ubuntu/+source/subversion/+bug/43557

Subversion UI's have been reviewed on ONlamp right here: http://www.onlamp.com/pub/a/onlamp/2005/03/10/svn_uis.html

http://svn.haxx.se/tsvnusers/archive-2006-01/0134.shtml

undo is done using 'svn merge' or 'svn copy': http://svnbook.red-bean.com/nightly/en/svn.branchmerge.basicmerging.html#svn.branchmerge.basicmerging.undo

undo 'svn mv': run 'svn revert' on both the new and old targets to undo the change.

To remove a file from version control without deleting it, run 'svn rm --keep-local'. In Subversion 1.4 and earlier, you'll have to make a copy of the file, then run "svn rm" on it, then (after committing the "rm"), restore the file from the copy.

http://svn.apache.org/repos/asf/subversion/trunk/notes/repos_upgrade_HOWTO

Normally, to upgrade a BDB repository 'in-place' to a new version of BDB, 'svnadmin recover' is all that's needed. For BDB 4.3 upgrades, however, see this FAQ: http://subversion.apache.org/faq.html#bdb43-upgrade

The Subversion Users mailing list archive is at http://svn.haxx.se/users/

gstein, khmarbaise, ewong, lorenz; users-owner@subversion.a.o

the book chapter on vendor branches is located at http://svnbook.red-bean.com/nightly/en/svn.advanced.vendorbr.html

the book chapter on vendor branches is located at http://svnbook.red-bean.com/nightly/en/svn.advanced.vendorbr.html

the book chapter on vendor branches is located at http://svnbook.red-bean.com/nightly/en/svn.advanced.vendorbr.html

svnadmin verify needs exclusive access to the repos. so shutdown all accessing process and try it again. if you use apache or svnserve make sure you chmod it back to the user the daemon runs with.

http://svn.haxx.se/users/archive-2010-09/att-0122/verify-revisions.sh.txt

http://subversion.apache.org/faq.html#version-value-in-source

http://subversion.apache.org/faq.html#version-value-in-source

http://subversion.apache.org/faq.html#version-value-in-source

Subversion repository web viewers include:
ViewVC, WebSVN, SVN::Web, Insurrection, Chora, SVN::RaWeb::Light, mod_svn_view, Trac, Collaboa, FlexySVN, perl_svn

ViewVC (formerly ViewCVS) is a repository browser, originally for CVS, but from version 1.0 also supports Subversion. Homepage: http://www.viewvc.org/ . Example: http://svn.apache.org/viewvc/subversion/trunk/ .

ViewVC (formerly ViewCVS) is a repository browser, originally for CVS, but from version 1.0 also supports Subversion. Homepage: http://www.viewvc.org/ . Example: http://svn.apache.org/viewvc/subversion/trunk/ .

a neat refcard for vim can be found at http://tnerual.eriogerg.free.fr/vim.html

http://betterexplained.com/articles/a-visual-guide-to-version-control/

http://www.wadhome.org/MicroSoft.jpg

vss2svn is http://vss2svn.tigris.org/

here!

I am a bot. I am written in Python, and serve factoids in #svn on freenode. My home is http://repos.borg.ch/svn/wayita/trunk/

an acronym for Working Copy.

sqlite3 .svn/wc.db 'pragma user_version;'

it's partly cloudy and dry, some rain and the sun is shining.

How to do automatic updates of websites and other server side working copies is in http://subversion.apache.org/faq.html#website-auto-update

How to do automatic updates of websites and other server side working copies is in http://subversion.apache.org/faq.html#website-auto-update

incomplete list of web-svnadmin tools: http://svnmanager.sourceforge.net/ http://www.usvn.info/ http://www.ohloh.net/p/SVNAdmin http://supermind.nl/submin/

incomplete list of web-svnadmin tools: http://svnmanager.sourceforge.net/ http://www.usvn.info/ http://www.ohloh.net/p/SVNAdmin http://supermind.nl/submin/

How to do automatic updates of websites and other server side working copies is in http://subversion.apache.org/faq.html#website-auto-update

http://websvn.tigris.org/

BerkeleyDB can get 'wedged' for a number of reasons, ususally because of bad permissions or ownership. Read this FAQ, and the various links it points to: http://subversion.apache.org/faq.html#stuck-bdb-repos

BerkeleyDB can get 'wedged' for a number of reasons, ususally because of bad permissions or ownership. Read this FAQ, and the various links it points to: http://subversion.apache.org/faq.html#stuck-bdb-repos

main reasons for wedges are 1. permissions are broken. (see "ayita: permissions?") 2. process which didnt close correctly and left the repos in some inconsistent state.

http://subversion.apache.org/faq.html#def-wedged-repository

Definitely, yes!

nah. I'd say no.

svk is a decentralized version control system written in Perl. It uses the Subversion repository and is somewhat interoperable with regular Subversion, but provides additional powerful features. http://svk.elixus.org (Its mystery is only exceeded by its power.)

http://pixel.global-banlist.de./whythedot

http://subversionary.org/

http://svn.haxx.se/users/archive-2009-07/0764.shtml

sqlite3 .svn/wc.db "select work from work_queue;"

sqlite3 .svn/wc.db "select work from work_queue;"

sqlite3 .svn/wc.db "select work from work_queue;"

"/usr/lib/libgdbm.so: could not read symbols: File in wrong format" is probably a 32/64 bit issue, try "CFLAGS=-m32 ./configure"

Ask about what you want to do at the end of the day, not about the steps you think would lead you there. http://s.apache.org/xy-problem

I am a bot. I am written in Python, and serve factoids in #svn on freenode. My home is http://repos.borg.ch/svn/wayita/trunk/