Re: difference between subversion 1.4.2 repository and 1.6.12 repository
On Tue, Oct 19, 2010 at 11:51 AM, Kriparam Faraday kripa...@gmail.com wrote: Can someone tell me the difference between a 1.4.2 repository and 1.6.12 repository? I recently upgraded all our repositories(along with the subversion server) from 1.4.2 to 1.6.12. I ran the svnadmin verify, tested check-in, check-out,add,delete file etc... Everything looks good. But, I wanted to know if the repositories are truly 1.6 now? How do I find that out? what is the difference between the two repositories. I found this online, but it didnt help much: http://svn.apache.org/repos/asf/subversion/trunk/notes/repos_upgrade_HOWTO Good for you! They should be working just fine if you used svnadmin upgrade. What's not necessarily obvious to a new admin is that it can be worth doing a dump and reload, in order to take advantage of the more efficient storage now. This can particularly clean up logs with end-of-line whackiness, and significantly improve the performance of large repositories. The larger the repository, the longer this takes to do the dump and reload, of course.
can I checkout only a revision files ?
Is it possible to checkout only files (not patch, but entire files) from a specific revision ? Thanks, A.
Re: can I checkout only a revision files ?
On Wed, Oct 20, 2010 at 09:17, Andrea Antonio Maleci a.mal...@iwbank.it wrote: Is it possible to checkout only files (not patch, but entire files) from a specific revision ? Yes, use the --revision option for svn co.
RE: can I checkout only a revision files ?
It retrieves entire repository at specified revision, not only the modified one... -Original Message- From: Andy Levy [mailto:andy.l...@gmail.com] Sent: mercoledì 20 ottobre 2010 15.25 To: Andrea Antonio Maleci Cc: users@subversion.apache.org Subject: Re: can I checkout only a revision files ? On Wed, Oct 20, 2010 at 09:17, Andrea Antonio Maleci a.mal...@iwbank.it wrote: Is it possible to checkout only files (not patch, but entire files) from a specific revision ? Yes, use the --revision option for svn co.
Re: can I checkout only a revision files ?
On Wed, Oct 20, 2010 at 09:33, Andrea Antonio Maleci a.mal...@iwbank.it wrote: It retrieves entire repository at specified revision, not only the modified one... You cannot check out an individual file. You can update specific files to a particular revision with svn update --revision num FILE You can export an individiual file at a particular revision with the same syntax as update (just swap in export instead). The output of svn help command can be very informative. -Original Message- From: Andy Levy [mailto:andy.l...@gmail.com] Sent: mercoledì 20 ottobre 2010 15.25 To: Andrea Antonio Maleci Cc: users@subversion.apache.org Subject: Re: can I checkout only a revision files ? On Wed, Oct 20, 2010 at 09:17, Andrea Antonio Maleci a.mal...@iwbank.it wrote: Is it possible to checkout only files (not patch, but entire files) from a specific revision ? Yes, use the --revision option for svn co.
RE: can I checkout only a revision files ?
[Please do not top-post on this list, add / insert your response in line] -Original Message- From: Andy Levy [mailto:andy.l...@gmail.com] Sent: mercoledì 20 ottobre 2010 15.25 To: Andrea Antonio Maleci Cc: users@subversion.apache.org Subject: Re: can I checkout only a revision files ? On Wed, Oct 20, 2010 at 09:17, Andrea Antonio Maleci a.mal...@iwbank.it wrote: Is it possible to checkout only files (not patch, but entire files) from a specific revision ? Yes, use the --revision option for svn co. -Original Message- From: Andrea Antonio Maleci [mailto:a.mal...@iwbank.it] Sent: 20 October 2010 14:34 To: 'Andy Levy' Cc: users@subversion.apache.org Subject: RE: can I checkout only a revision files ? It retrieves entire repository at specified revision, not only the modified one... That is the way subversion works. A revision number identifies a state of the complete repository and includes all files / folders / metadata etc. So, are you asking for only the files changed from the previous revision? If so, why would you want that? Subversion only sends diffs between client and server, so that is already efficient. If you want a list of the changes you can use the 'log' command. Remember that metadata can also change in a revision, not just files/folders. I am not aware that you can ask subversion to give you a working copy only containing the files updated by a particular rev but I fail to see how that would be useful... If that does not help, try rephrasing your question and/or providing more background. Cheers, ~ Mark C
Re: can I checkout only a revision files ?
On Wed, Oct 20, 2010 at 9:17 AM, Andrea Antonio Maleci a.mal...@iwbank.it wrote: Is it possible to checkout only files (not patch, but entire files) from a specific revision ? You can use the -r parameter on a checkout or update to specify the revision. You cannot checkout a single file, but you can checkout the directory it is in with no files and then update just that one file: $ # Checks out the directory, but with no files $ svn co -r $rev --depth empty http://svn/repos/project/dir localdir $ # Now update the file you want $ cd localdir $ svn update myfile Or, you can checkout just a directory, but without the subdirectories: $svn co -r $rev --depth files http://svn/repos/project/dir localdir -- David Weintraub qazw...@gmail.com
RE: can I checkout only a revision files ?
[Please do not top-post on this list, add / insert your response in line] -Original Message- From: Cooke, Mark [mailto:mark.co...@siemens.com] Sent: mercoledì 20 ottobre 2010 15.43 To: Andrea Antonio Maleci; Andy Levy Cc: users@subversion.apache.org Subject: RE: can I checkout only a revision files ? [Please do not top-post on this list, add / insert your response in line] -Original Message- From: Andy Levy [mailto:andy.l...@gmail.com] Sent: mercoledì 20 ottobre 2010 15.25 To: Andrea Antonio Maleci Cc: users@subversion.apache.org Subject: Re: can I checkout only a revision files ? On Wed, Oct 20, 2010 at 09:17, Andrea Antonio Maleci a.mal...@iwbank.it wrote: Is it possible to checkout only files (not patch, but entire files) from a specific revision ? Yes, use the --revision option for svn co. -Original Message- From: Andrea Antonio Maleci [mailto:a.mal...@iwbank.it] Sent: 20 October 2010 14:34 To: 'Andy Levy' Cc: users@subversion.apache.org Subject: RE: can I checkout only a revision files ? It retrieves entire repository at specified revision, not only the modified one... That is the way subversion works. A revision number identifies a state of the complete repository and includes all files / folders / metadata etc. So, are you asking for only the files changed from the previous revision? Yes, I need only last changes, but entire files, not only diffs. If so, why would you want that? Subversion only sends diffs between client and server, so that is already efficient. It seems, from your answer, that I need to write a script, getting output from svn log e requiring to svn last revision of changed files. If you want a list of the changes you can use the 'log' command. Remember that metadata can also change in a revision, not just files/folders. I am not aware that you can ask subversion to give you a working copy only containing the files updated by a particular rev but I fail to see how that would be useful... If you version and commit your classes, you need to get only changed one to patch you application server. That's why I need last committed files. If that does not help, try rephrasing your question and/or providing more background. Cheers, ~ Mark C Thanks, Andrea
Re: can I checkout only a revision files ?
On Wed, Oct 20, 2010 at 09:17, Andrea Antonio Maleci
a.mal...@iwbank.it wrote:
Is it possible to checkout only files (not patch, but entire files)
from a specific revision ?
From: Andy Levy [mailto:andy.l...@gmail.com]
Yes, use the --revision option for svn co.
Andrea Antonio Maleci a.mal...@iwbank.it wrote:
It retrieves entire repository at specified revision, not only the
modified one...
Right,
As others have said, you cannot 'svn co' files,
you can only checkout directories.
The ability to export files exists, but to export
only modified files is not built in, either.
I've been trying to learn Bash scripting better
and wrote the following.
If you're on Windows, install Cygwin.
It may not be exactly what you
want, because it exports the files
instead of checking them out.
You have to do something like...
svn log --verbose -r 2345 | grep M files.txt
...then something like... (vi svncomod.sh)
#!/bin/bash
FILE=$1
REPO=$2
while read line
do
for ARG in $line; do
F=${ARG}
if [ $F != M ]
then
echo ${REPO}${F}
svn export ${REPO}${F}
fi
done
done ${FILE}
... then...
chmod +x svncomod.sh
...and finally...
svncomod.sh files.txt http://path-to/repo
RE: can I checkout only a revision files ?
[Please do not top-post on this list, add / insert your response in line] -Original Message- From: Cooke, Mark [mailto:mark.co...@siemens.com] Sent: mercoledì 20 ottobre 2010 15.43 To: Andrea Antonio Maleci; Andy Levy Cc: users@subversion.apache.org Subject: RE: can I checkout only a revision files ? [Please do not top-post on this list, add / insert your response in line] -Original Message- From: Andy Levy [mailto:andy.l...@gmail.com] Sent: mercoledì 20 ottobre 2010 15.25 To: Andrea Antonio Maleci Cc: users@subversion.apache.org Subject: Re: can I checkout only a revision files ? On Wed, Oct 20, 2010 at 09:17, Andrea Antonio Maleci a.mal...@iwbank.it wrote: Is it possible to checkout only files (not patch, but entire files) from a specific revision ? Yes, use the --revision option for svn co. -Original Message- From: Andrea Antonio Maleci [mailto:a.mal...@iwbank.it] Sent: 20 October 2010 14:34 To: 'Andy Levy' Cc: users@subversion.apache.org Subject: RE: can I checkout only a revision files ? It retrieves entire repository at specified revision, not only the modified one... That is the way subversion works. A revision number identifies a state of the complete repository and includes all files / folders / metadata etc. So, are you asking for only the files changed from the previous revision? Yes, I need only last changes, but entire files, not only diffs. If so, why would you want that? Subversion only sends diffs between client and server, so that is already efficient. It seems, from your answer, that I need to write a script, getting output from svn log e requiring to svn last revision of changed files. If you want a list of the changes you can use the 'log' command. Remember that metadata can also change in a revision, not just files/folders. I am not aware that you can ask subversion to give you a working copy only containing the files updated by a particular rev but I fail to see how that would be useful... If you version and commit your classes, you need to get only changed one to patch you application server. That's why I need last committed files. If that does not help, try rephrasing your question and/or providing more background. My NAnt build scripts have a task that will create a delta of the changed deployables to create a hotfix for example. Just pulling out the changed stuff from svn wouldn't work anyway... since new binaries need to be built most of the time. BOb
Re: Having a path name after specifying repository location
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 techgeek12...@gmail.com wrote: 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 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 partA I get the error message: SVN: Could not open the requested filesystem.
Re: Having a path name after specifying repository location
On Mon, Oct 18, 2010 at 20:52, Tech Geek techgeek12...@gmail.com wrote: 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/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 Is it true that all the directories directly under /var/lib/svn/ should be an *actual* repository? No, they will not be a single, unified repository. You have created two separate repositories, /var/lib/svn/projectB/partA and /var/lib/svn/projectB/partB Can't we have some pathname like ProjectB under /var/lib/svn/ and then have repositories (like PartA and PartB) under it without changing the root path of the repository which is /var/lib/svn? Subversion does not support nesting like this. Your repository must be an immediate child directory of /var/lib/svn . How do you overcome this situation? I want PartA and PartB to be separate SVN repository but I do not want to place them under /var/lib/svn/ directory because they beloing to ProjectB and in future other projects like ProjectD could have PartA and PartB in the same manner. If PartA PartB are part of the same project, why are they in separate repositories in the first place? A more conventional approach would be: /var/lib/svn/ProjectB /var/lib/svn/ProjectD And then PartA PartB would be paths *inside* the ProjectB repository - not distinct repositories themselves.
Re: Having a path name after specifying repository location
On Wed, Oct 20, 2010 at 12:11, Andy Levy andy.l...@gmail.com wrote: On Mon, Oct 18, 2010 at 20:52, Tech Geek techgeek12...@gmail.com wrote: 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/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 Is it true that all the directories directly under /var/lib/svn/ should be an *actual* repository? No, they will not be a single, unified repository. You have created two separate repositories, /var/lib/svn/projectB/partA and /var/lib/svn/projectB/partB Can't we have some pathname like ProjectB under /var/lib/svn/ and then have repositories (like PartA and PartB) under it without changing the root path of the repository which is /var/lib/svn? Subversion does not support nesting like this. Your repository must be an immediate child directory of /var/lib/svn . Edit: I should have specified this as the path you have set as your SVNParentPath How do you overcome this situation? I want PartA and PartB to be separate SVN repository but I do not want to place them under /var/lib/svn/ directory because they beloing to ProjectB and in future other projects like ProjectD could have PartA and PartB in the same manner. If PartA PartB are part of the same project, why are they in separate repositories in the first place? A more conventional approach would be: /var/lib/svn/ProjectB /var/lib/svn/ProjectD And then PartA PartB would be paths *inside* the ProjectB repository - not distinct repositories themselves. The other way you could do this, if you insist upon PartA PartB being separate repositories, is to have a different Location 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 management overhead as you add projects/repositories, and potentially more confusion.
svn:externals and local directories
Hi SVN, We're stuck for the time being with server 1.4.2 but have updated our svn client(s) on Windows PCs (most of use Cygwin, CollabNet command line client and Tortoise) periodically over the last year or two. About 7 or 8 months ago, we began using svn:externals heavily. At the time, I could've sworn we got errors when trying to tell an external to stream in to a subdirectory that didn't exist, e.g. our svn:externals on /app/trunk looks like this, for an arbitrary web app: modules/foo http://server/repo/path/to/foo/tags/01 modules/bar http://server/repo/path/to/bar/tags/02 modules/baz http://server/repo/path/to/baz/tags/03 In order for this to work, we had to create an empty `modules` folder under /app/trunk otherwise checking out would fail for foo, bar and baz externals. Well, we recently hired some new people and started seeing modules folders disappearing from the repository. Nobody's complaining about breakage... and so we did some tests and realized that the client can create folders at arbitrary depths when building the path necessary for an external. Can someone confirm this was changed recently for svn client? Otherwise I think I'm losing my mind because I swear this was not possible before. I tried to find the release notes for the different versions on the collabnet site but was unsuccessful. One other question about svn:externals. If you change or delete the local paths you're pointing your externals to, it leaves stray folders from before in the wc. Is this a bug or the intended behavior? Manually deleting these folders (not svn delete) works fine, but is there any more automated, foolproof way to check to see whether a certain tree in a wc has no reason for being there? (eg the external that created it it is no longer there?) specifically: svn propset svn:externals modules/foo http://server/repo/path/to/foo/tags/03 svn up svn propset svn:externals modules/bar http://server/repo/path/to/bar/tags/02 svn up svn ls modules/foo modules/bar Why does foo stick around? Thanks, Geoff
How to mirror a SVN GitHub Repo to a SVN repo elsewhere
Hello Maybe you can help me to achieve this: GitHub has support for Read Only SVN repo of every Git repo. I want to use this to mirror the GitHub repo to a SVN Repo in the servers of my School. But I got some errors messages that I don't understand. I am stuck. Maybe you can enlighten my path :) The details of my situation are here: http://stackoverflow.com/questions/3978109/how-to-mirror-a-github-svn-repository-to-svn-repository-hosted-in-other-place Feel free to answer me wherever you want. Thank you a lot.
Re: How to mirror a SVN GitHub Repo to a SVN repo elsewhere
2010/10/20 Gonzalo Rodríguez-Baltanás Díaz siot...@gmail.com Hello Maybe you can help me to achieve this: GitHub has support for Read Only SVN repo of every Git repo. I want to use this to mirror the GitHub repo to a SVN Repo in the servers of my School. But I got some errors messages that I don't understand. I am stuck. Maybe you can enlighten my path :) The details of my situation are here: http://stackoverflow.com/questions/3978109/how-to-mirror-a-github-svn-repository-to-svn-repository-hosted-in-other-place Feel free to answer me wherever you want. Thank you a lot. you can try out svnsync to mirror the svn repo at github -- Vishwajeet Singh +91-9657702154 | dextrou...@gmail.com | http://bootstraptoday.com Twitter: http://twitter.com/vishwajeets | LinkedIn: http://www.linkedin.com/in/singhvishwajeet
RE: Users cannot reliably view SVN log messages remotely
I got past the issue and wanted to post my solution here for other SVN admins/users. HTH. I've got a distant user who cannot reliably view the SVN log messages Using TortoiseSVN. If he 'refreshes', he can view the SVN log messages fine. Also, checkouts work fine. Other users at his (distant) site seem to have the same issue, but I can't reproduce the issue here and haven't heard of similar issues from other sites. From inspecting the Apache logs, I found that the user's client was in an invalid state. Somehow it was sending the server requests for revisions that did not modify any files in the selected directory. For example, Revision 2688 does not exist on Path/To/Directory, but this was in the access_log: REPORT /svn/RepoName/!svn/bc/2688/Path/To/Directory HTTP/1.1 404 247 His TSVN client was also displaying revision 2689 in the Show Log windows. After asking the user to disable log caching and clear his saved data he was able to view the log messages again without clicking 'refresh' and the invalid revision 2689 disappeared from his TSVN window. Provider encountered an error while streaming a REPORT response. [500, #0] A failure occurred while driving the update report editor [500, #103] Error writing base64 data: Software caused connection abort [500, #103] As for these other error messages, I'm still not sure the reason but there's no pressing need to investigate at the moment. If I find a solution later I'll make sure to post it here for everyone. Best, Shaun
Re: Having a path name after specifying repository location
The other way you could do this, if you insist upon PartA PartB being separate repositories, is to have a different Location 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 management overhead as you add projects/repositories, and potentially more confusion. You mean something like this? Location /svn DAV svn SVNParentPath /var/lib/svn/projectA SVNListParentPath On AuthBasicProvider ldap AuthType Basic AuthzLDAPAuthoritative off AuthName Subversion Repositories .. .. require valid-user /Location Location /svn DAV svn SVNParentPath /var/lib/svn/projectB SVNListParentPath On AuthBasicProvider ldap AuthType Basic AuthzLDAPAuthoritative off AuthName Subversion Repositories .. .. require valid-user /Location and so on Would be nice if someone already has a script (that excepts the name of the repository) that does the job of entering the Locaiton block in the apache configuration file. Also why svn does not support nesting paths (logical empty folder) under repository location. I am sure many people might have encountered simialar issues especially if they have existing projects before they started using subversion. Thanks for the help.
Re: Having a path name after specifying repository location
On Wed, Oct 20, 2010 at 15:10, Tech Geek techgeek12...@gmail.com wrote: The other way you could do this, if you insist upon PartA PartB being separate repositories, is to have a different Location 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 management overhead as you add projects/repositories, and potentially more confusion. You mean something like this? Location /svn DAV svn SVNParentPath /var/lib/svn/projectA SVNListParentPath On AuthBasicProvider ldap AuthType Basic AuthzLDAPAuthoritative off AuthName Subversion Repositories .. .. require valid-user /Location Location /svn DAV svn SVNParentPath /var/lib/svn/projectB SVNListParentPath On AuthBasicProvider ldap AuthType Basic AuthzLDAPAuthoritative off AuthName Subversion Repositories .. .. require valid-user /Location No, you would need Location /svnA Location/svnB Would be nice if someone already has a script (that excepts the name of the repository) that does the job of entering the Locaiton block in the apache configuration file. Also why svn does not support nesting paths (logical empty folder) under repository location. I am sure many people might have encountered simialar issues especially if they have existing projects before they started using subversion. I think you're getting confused about the relationships between projects and repositories, and introducing many more layers than needed. 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?
Re: Having a path name after specifying repository location
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. This is how the stakeholders want it. You know how it is in organizations...
German console output
Hello! I would be interested in why the Windows binaries from CollabNet and WANdisco aren't able to print messages from svn commands in German language to the console. (Whereas the binaries from Win32Svn at http://alagazam.net are able to do so!) The internationalization module seems to be missing in CollabNet's and WANdisco's compilation, isn't it? Example with Win32Svn binaries: C:svn ci -m Hinzufügen blah Thanks Regards, Paul
Re: German console output
On Wed, Oct 20, 2010 at 6:07 PM, Paul Maier svn-u...@web.de wrote: I can answer for the CollabNet binaries. We do not compile it with the internationalization support included so you will only see English messages. I would be interested in the reasons for this decision. I would guess it was an oversight at first (I was not around when CollabNet first started providing binaries). I did not notice they were not included until around the time 1.5 was coming out and at the time we had higher priority changes we were making. Eventually, I just dropped it because no one ever asked for them. I have heard users in this forum indicate they prefer to just see the messages in English and ask how to turn them off -- maybe that is why? They also add considerable amount of size to the download. -- Thanks Mark Phippard http://markphip.blogspot.com/
Re: svn Farm
On Mon, Oct 18, 2010 at 12:56 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: It would be trivial to fork svn to lie and report that it only stored passwords encrypted, stick that forked client on my machine and hey presto, away I go storing my password in plaintext. If someone is *that* determined to shoot themselves in the foot, and willing to go to that much effort to do it, I don't think there's much you can do. They probably have their password on a sticky note on the bottom of their keyboard, too. ;) -- David Brodbeck System Administrator, Linguistics University of Washington
Re: svn Farm
On Fri, Oct 15, 2010 at 7:01 PM, Nico Kadel-Garcia nka...@gmail.com wrote: No. system_auth is still the NFS standard for internal use in both academic and professional environments. auth_dh has uses, but it doesn't help against any machine with allocated or cracked local root access. This isn't your local machine, it's the network wide home directory system, and there are plenty of them out there without even this step. I don't doubt that, but my point is in this particular scenario there are far bigger issues that render anything SVN does entirely moot. If I have root access to the filesystem, it doesn't matter what SSH does to try to encrypt the password, because I have full access to your account. I can just change your PATH to point to my trojaned SVN binary and grab your password that way, for example. There simply isn't any level of precaution sufficient to protect you from a rogue root user on a UNIX system. I'm not saying there aren't situations where it's a good idea to have SVN encrypt passwords, just that this isn't a very good example of one. If people can boot a LiveCD and get root access to your NFS shares, they already have the keys to the castle. -- David Brodbeck System Administrator, Linguistics University of Washington
Re: svn Farm
On Wed, Oct 20, 2010 at 4:30 PM, David Brodbeck bro...@uw.edu wrote: If I have root access to the filesystem, it doesn't matter what SSH does to try to encrypt the password... Typo. s/SSH/SVN/ -- David Brodbeck System Administrator, Linguistics University of Washington
AW: German console output
Hi Mark, So I want to post to the list, that I am a user who IS looking for German output. That was quite an installation procedure, first to install then deinstall CollabNet's binaries (because not internationalized) then the same for WANdisco's binaries. Also both, CollabNet and Wandisco, don't include the BDB module. Finally I found the full compilation including German support and BDB at Win32Svn at http://alagazam.net. These are the binaries I am now working with. I was just wondering why CollabNet doesn't also offer a full compilation will all modules and internationalized. (Since Svn origined at CollabNet.) I understand the issue with the download size. Just a proposal: Why not offering two kinds of binary packages at CollabNet?: One small size package as now (without language support and without BDB) and a full package with all available modules. Paul -Ursprüngliche Nachricht- Von: Mark Phippard [mailto:markp...@gmail.com] Gesendet: Donnerstag, 21. Oktober 2010 00:12 An: Paul Maier Cc: users@subversion.apache.org Betreff: Re: German console output On Wed, Oct 20, 2010 at 6:07 PM, Paul Maier svn-u...@web.de wrote: I can answer for the CollabNet binaries. We do not compile it with the internationalization support included so you will only see English messages. I would be interested in the reasons for this decision. I would guess it was an oversight at first (I was not around when CollabNet first started providing binaries). I did not notice they were not included until around the time 1.5 was coming out and at the time we had higher priority changes we were making. Eventually, I just dropped it because no one ever asked for them. I have heard users in this forum indicate they prefer to just see the messages in English and ask how to turn them off -- maybe that is why? They also add considerable amount of size to the download. -- Thanks Mark Phippard http://markphip.blogspot.com/
