See also
http://subversion.apache.org/docs/release-notes/1.7.html#per-repos-authz
Bert
Sent from Mail for Windows 10
From: Thorsten Schöning
Sent: woensdag 5 augustus 2015 21:34
To: users@subversion.apache.org
Subject: Re: Can the Apache front end and svnserve service run on the
sameserver
, and it is not clear which part you call
succeeded?
The number of regression test of this operation was increased significantly for
1.9, as the behavior was made more consistent over the different ra layers and
atomicity was improved.
Bert
Sent from Mail for Windows 10
From: Gustavo
editing the revisions in this format; as is sometimes done
on migrations)
Bert
From: Eric Johnson
Sent: dinsdag 15 september 2015 07:16
To: users@subversion.apache.org
Subject: Incomplete SVN dump files
I'm in a situation where I'm dumping Subversion repositories from remote
locati
I don’t have this known
broken set of commandline binaries installed on my system. (I had to track a
few similar cases earlier this week, all caused by this CRT linkage problem)
Bert
From: Fredrik Klasson
Sent: vrijdag 18 september 2015 11:34
To: users@subversion.apache.org
Subject: Redirection
.
They reverted to using a shared CRT in the latest builds which fixes these
problems.
Bert
From: Fredrik Klasson
Sent: vrijdag 18 september 2015 13:36
To: b...@qqmail.nl
Cc: users@subversion.apache.org
Subject: Re: Redirection "svn info -r HEAD"
Ok thanks for the input :) Sounds
by the xml inventers was a safe decision.
Your files are just not 'generic xml', and should have a more specific type.
Bert
From: Ivan Zhakov
Sent: zondag 4 oktober 2015 11:35
To: Edward d'Auvergne
Cc: users@subversion.apache.org
Subject: Re: Bug report: The auto-props se
would just use a simple commit filter if necessary, to avoid users
accidentally committing DVD images.
Bert
Sent from Mail for Windows 10
From: Siva
Sent: woensdag 13 juli 2016 16:07
To: subversion-users
Subject: Commit Size Restriction
Hi All,
My Subversion Edge is installed in Windows Server
Does the file have any specific properties, such as svn:eol-style or
svn:keywords?
Bert
From: Thorsten Schöning
Sent: Tuesday, October 22, 2013 8:05 AM
To: users@subversion.apache.org
Guten Tag Branko Čibej,
am Dienstag, 22. Oktober 2013 um 07:13 schrieben Sie:
>
eported issue in sliksvn:
> http://svn.haxx.se/users/archive-2010-09/0065.shtml
The 1.6.13 binaries with a fix for this error should be on the site soon. (I
provided the binaries, but they have to be placed on the public site)
Bert
> hth,
>
> Lieven
modules and internationalized.
> (Since Svn origined at CollabNet.)
The binaries from the Slik Subversion client
(http://www.sliksvn.com/en/download) also support localization (and BDB +
Sasl), but they only support the client parts of Subversion; not the server.
Bert
quest:
> "svn cat file" should also work with Codepage 850.
>
> Who agrees, that this feature request is worth a prio P4 issue?
>
> (I have to use Codepage 850, because Cygwin needs it.)
'svn cat file' doesn't perform any translation at all. It just writes what
is in 'file' to the standard output device.
(Subversion doesn't know which character encoding is used in 'file')
Bert
I don't think %VISUALSVN_SERVER% is set in your lock script. Subversion
explicitly clears most environment variables before calling hook scripts.
Most likely your script can't find svnlook.exe
Bert
From: Waseem Bokhari [mailto:waseem.bokh...@netsoltech.
sn't receive all checksums in
all places. Serf receives a few more, because it uses a request per file.
For trunk I fixed the missing checksums for 1.7, so a trunk server with a
trunk client gets all the checksums editor v1 supports.
But using an older server or an older client will not. In that case you just
get the calculated checksums in your working copy.
I think this server is pre 1.5, but it is certainly possible to get invalid
checksums in a checkout when you encounter the problems mentioned in issue
#3711. But you don't encounter these problems with trunk clients.
Bert
ttpd to
> authenticate against AD.
But currently this doesn't support NTLM/SSPI yet where you don't have to
use/cache your credentials. Using mod_auth_sspi in Apache on Windows (or
VisualSVN server, which does the same thing + adds their own extensions)
does support that.
Bert
lder, they should be completely removed from
your working copy, leaving a marker that they shouldn't be updated. (You can
bring them back by --set-depth infinity on a parent or an explicit update of
PATH itself).
This option is available for directories since Subversion 1.6. (In 1.7 you
can also use it to exclude a specific file)
Bert
elf to do
> this, hence my suggestion to use third-party tools.
The problem is: We just know it isn't utf-8. But that doesn't tell us how to
fix it.
But which encoding does it have, if it isn't utf-8 as expected?
Without telling Subversion could choose from hundreds of different encodings
(iso-8859-1?, etc., etc.), which might just contain the one you would like.
(Or maybe your filesystem used format 101).
Subversion defines that it must be utf-8, so it can't answer this question
for you.
Bert
;
> BTW: In case you wonder if that is a bug or feature, I have used this feature
> to switch a file to a directory.
The current Subversion 1.7 development snapshot warns you when you do this and
requires that you pass --ignore-ancestry if you really want to switch to
something unrelated.
Bert
ust be canonical,
we shouldn't see this problem.
But as I found out (and fixed in r1137927) our uri canonicalization for user
provided uris didn't check port numbers at all.
Bert
', wc_dir)
# So we run update
run_and_verify_svn(None, None, [],
'up', wc_dir)
# And now we can commit
run_and_verify_svn(None, None, [],
'ci', '-m', '', wc_dir)
(It is actually part of
http://svn.apac
D8A18' and not like
''C:\svn-451D8A18'?
(Can you copy an exact error message?)
This is an export from a url to a directory and not an export from a
directory to a directory?
Bert
update to the requested revision (or in this case HEAD)
This was originally designed so you could create restartable scripts that
perform a checkout. So if the checkout fails you can just rerun checkout and
it continues where it stopped the last time.
(For scripts this might be easier than running 'svn update $targetdir)
Bert
en on a commit? :-)
No, you can't switch a subtree to a different repository.
You can exclude a directory and perform a new checkout in its place though.
But this starts a new working copy.
Bert
e files in the same second when the filesystem has less than or exactly
1 second timestamp precision)
A clock skew between tool and filesystem might introduce this problem if you
have a script that updates files directly after update.
But personally I would guess that Ryan's answer is far more likely as
usually at least some file sizes change.
Bert
nbridge.codeplex.com ).
Their documentation says that they created svnbridge by reverse engineering
the wire protocol of TortoiseSVN (somewhere around Subversion 1.5)
Bert
ly I'm wrong, since you say that user 'andy' has to run svnserve
> himself. If we do this for 'andy' and "bill' does this mean we're
> running two copies of svnserve at the same time, one as user 'andy' and
> the other as user 'bill'?
Svnserve can be used in two different modes.
If you use svnserve via svn:// things work as you assumed.
But if you use svn+ssh:// svnserver is started as the user who creates the ssh
tunnel (as described in this mail).
Bert
sites. I will let you know otherwise.
Codeplex is a reimplementation of the svn server by reverse engineering
(instead of looking at the developer documentation), so it might be
different in ways not detected by the standard libraries. (And they have
quite a list of 'known' issues that a
the new
working copy store. The next 'svn update' will apply the changes even if the
directory on which they are defined was never committed.
Bert
re case sensitive to
> the WC folder name.
>
> The following test case shows the steps to reproduce the problem using a
> public server:
Thanks for reporting (and the nice reproduction recipe).
I just fixed the issue in r1154165.
(This patch won't make beta 3, but I'll nominate it for backport for 1.7.0)
Bert
this issue in our test suite and fixed it on trunk in
r1156098.
(The fix is nominated for backport to 1.7)
Bert
same site.
The version you are looking at was written for Subversion 1.0 and a lot has
changed since then.
(I think svn lock wasn't introduced until 1.1 or 1.2)
Bert
our Subversion client is compiled against a recent openssl and neon/serf
version it supports SNI.
(I think most binary distributions fall in this category)
Bert
>
> Cheers
> Mario
enable them in Subversion.
(Or maybe neon can just enable the safe protocols all the time?)
@serf developers: This should probably be handled in serf too.
Bert
le:///d:/temp/test/repo.svn with three slashes
after file:.
file://server/share/ would translate to \\server\share, so your path points
to \\d:\temp\test\repo.svn.
Bert
database at
all, while we used to allow reading the entries for things like status.
What kind of error do you get?
(The SharpSvn stacktrace isn't really interesting for the users on this
list, but the message that is part from the trace matches exactly what you
would get from svn)
Bert
server.
Bert
From: Gavin Baumanis [mailto:gav...@thespidernet.com]
Sent: vrijdag 30 september 2011 5:14
To: Subversion Users
Subject: Authentication realm
Hi Everyone,
We recently created a DNS entry for our subversion repository.
Prior to this we just use the
no return
possible', but you get a boolean in the handler to see in which variant you
are.
Another option is to throw a C++ exception and catch it when the call stack
is back in your code. If you then clean the pool you passed to the function
your own code should work reliable again. (You can't be sure that calling
into Subversion is safe, but from what I hear from AnkhSVN users it appears
to just work even though I do recommend them to restart Visual Studio if
this problem occurs)
Bert
ictedDir, etc.
I can see some problems, which might need fixing but I'm still not sure what
your specific problem is.
(I'm not sure if the problems I currently see are regressions. Still looking
into that)
The error you see would only make sense if the working copy doesn't know
about RestrictedDir, except that it is a locally added file or directory.
When the server then tells that there should be a restricted path there you
get this error.
But giving a working copy with a single user, that is +- impossible to read
in your mail.
Bert
found.
Ok, this one is easy to reproduce with this clean reproduction script.
(Confirming this as an issue)
I will look into this.
Bert
> -Original Message-
> From: Andrey [mailto:and...@online-solutions.ru]
> Sent: dinsdag 18 oktober 2011 15:53
> To: Johan Corveleyn
> Cc: Stefan Sperling; Bert Huijben; users@subversion.apache.org
> Subject: Re[4]: Very big problems with access rights (authz file usin
> -Original Message-
> From: Bert Huijben [mailto:b...@qqmail.nl]
> Sent: dinsdag 18 oktober 2011 19:43
> To: 'Andrey'; 'Johan Corveleyn'
> Cc: 'Stefan Sperling'; users@subversion.apache.org
> Subject: RE: Re[4]: Very big problems with
> -Original Message-
> From: Johan Corveleyn [mailto:jcor...@gmail.com]
> Sent: woensdag 19 oktober 2011 0:32
> To: Bert Huijben
> Cc: Andrey; Stefan Sperling; users@subversion.apache.org
> Subject: Re: Re[4]: Very big problems with access rights (authz file
usin
> -Original Message-
> From: Johan Corveleyn [mailto:jcor...@gmail.com]
> Sent: woensdag 19 oktober 2011 9:26
> To: Bert Huijben
> Cc: Andrey; Stefan Sperling; users@subversion.apache.org
> Subject: Re: Re[4]: Very big problems with access rights (authz file
using) in
&g
#x27;aNYcASE' to 'TrueCase'. But this is currently
only implemented on Windows and some tests still fail on OS/X.
Some problems are fixed on OS/x by moving to SHA1 based pristines, but the
APR api fix is needed to detect naming collisions properly.
Bert
namespace there are no binary properties.
Svnsync doesn't transform other properties.
Bert
s atomic initialization call failed: the
callback function failed and returned an error. This result is then ignored
in some code paths.
It is most likely not caused by the atomic operations failing itself, but
more likely by an initialization error in a third party library.
Bert
this worked ok for some
operations although it was documented as *don't do this* since well before
1.0. Since Subversion 1.7 it will create this crash.
Googling for kdevelop and Subversion got me:
https://bugs.kde.org/show_bug.cgi?id=284061
Which validates my guess, and says it has been fixed since October 2011. So
you should probably upgrade your kdevelop.
Bert
settings are under:
HKEY_LOCAL_MACHINE\Software\Tigris.org\Subversion\Config
(add WOW6432 when necessary for Win64)
You can also use a configuration file in the all users appdata, just like
you can use setting files in /etc/ on unix.
Bert
From: Timothy Astle
re failure status.
> ]]]
I don't think the code should be conditional for Windows. On other platforms we
should also close databases that we are about to move as our references to it
(via abspath) are no longer valid anyway. (And who knows what sqlite does with
the path intern
certificates as accepted for explicit errors
like out of date or authority untrusted.
When the certificate processing in the serf library is fixed Subversion will
automatically work as expected.
Bert
>
> Regards,
> Joel
Hi,
If you are using Subversion 1.7.3 for your test, please upgrade to 1.7.4.
Subversion 1.7.3 always tries to build with apache httpd. This issue was
fixed in 1.7.4.
Bert
From: Brad Lemings [mailto:b...@rebit.com]
Sent: vrijdag 9 maart 2012 19:21
y and assume this magically cleans up)
When running from Visual Studio it appears that there are leftovers, but
this is mostly because the Intellisense uses the same infrastructure to get
its information.
If you do find places where the common tasks leave files behind please
report them as Microsoft is still taking bug reports for Visual Studio 11.
And if these are Subversion and/or AnkhSVN specific problems please also
send me a mail so I might be able to reach out via a few other channels.
Bert
>
> [[[
> $ sqlite3 .svn/wc.db "delete from work_queue"
>
> $ sqlite3 .svn/wc.db "select * from work_queue"
>
>
> C:\Work\WC-root>svn-1.7 up -r0 the/file/with/missing/pristine.java
> svn: E155004: Working copy 'C:\Work\WC-root\the\file\with\missing' locked.
> svn: E155004: 'C:\Work\WC-root' is already locked.
> svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for
details)
>
> C:\Work\WC-root>svn-1.7 cleanup
>
>
>
> C:\Work\WC-root>svn-1.7 up -r0 the/file/with/missing/pristine.java
> Updating 'the\file\with\missing\pristine.java':
> svn: E720002: Can't open file
> 'C:\Work\WC-
> root\.svn\pristine\6d\6d6e0892990e945b03a15b8e518dbef26848dc75.svn-
> base':
> The system cannot find the file specified.
>
>
>
> $ sqlite3 .svn/wc.db "select * from work_queue"
> 2|(file-install the/file/with/missing/pristine.java 1 0 1 1)
>
> ]]]
>
> Any other suggestions?
Maybe 'svn up --set-depth exclude X' instead of -r0.
And then a 'svn up X'
Bert
> -Original Message-
> From: Johan Corveleyn [mailto:jcor...@gmail.com]
> Sent: woensdag 28 maart 2012 17:25
> To: Daniel Shahaf
> Cc: Bert Huijben; Philip Martin; users@subversion.apache.org
> Subject: Re: svn 1.7: how to recover from a lost pristine file
>
> O
update performs a single operation with network
initiation for every selected item. Usually that is orders of magnitude
slower than performing a recursive operation on the root. (Subversion is
fully optimized for recursive operations; not for single item operations)
Bert
From
.
In 1.6 you should have resolved the tree conflict in the same way, but the
recovering process from missing data was about the same thing.
In 1.7 we can usually also recover from the missing conflicted data, so you
get the conflicted data back.
Bert
; M alpha
> > M epsilon/zeta
> > $ svn status | grep '^[A-Z]' | sed 's/^. \(.*\)$/\1/'
>
> $ svn status | sed -n 's/^[A-Z] \(.*\)$/\1/p' # From memory,
untested
This filters property changes and tree conflicts (column 2
out --depth empty URL
> svn ls (view items that could be here)
> for each item of interest:
> svn checkout --set-depth infinity item_of_interest
Replace this 'checkout' with 'update', or you get just many separate working
copies. In this case you can also drop the '--set-depth infinity' as that is
the default for new nodes that come in from the repository this way.
Bert
or. I will try to do some testing
in this direction later this week)
If you just did a checkout and then an update, this should never happen. My
guess would be that you have other problems, but it is hard to tell without
a reproduction.
Some information on the authorization settings of the repository would help
us get further in diagnosing your problem.
Bert
>
> I'm using svn-1.7.4 on the client and the server is running 1.4.2.
>
> Cheers
>
> Adam
design the feature welcome on
dev{_AT_}subversion.apache.org :-)
Bert
sources... but they aren't as easy to use as they should be, and
> come with some bizarre (non-intuitive) semantics.
>
> Is this bugworthy?
This was fixed in Subversion 1.7.0+, using the new working copy database.
We now keep track of exactly what externals were installed during update to
allow removing them later, even when they were only referenced from
uncommitted svn:externals properties.
Bert
using 'svn
checkout' or 'svn update'.
Bert
From: Matthias Meixner [mailto:matthias.meix...@verifone.com]
Sent: vrijdag 1 juni 2012 10:37
To: users@subversion.apache.org
Subject: svn status leaves out changes in externals
Hello!
In all versions u
cific Sqlite
versions. (This would be a known issue and upgrading Sqlite to 3.7.9 or
later the recommended action)
Some specific builds of Sqlite may enable foreign key constraints by
default; this may also cause this issue. But in that case I would call it a
bug in Subversion.
Bert
n), then a compare is performed. But if the file is (temporarily) not
readable, because some other process blocks that the file is marked as
'modified'.
This other process could be a file indexer, a virusscanner, a disk status
monitor, etc.
What you see later is probably that the file was closed and the status
succeeds again.
Bert
id you use?
I think this issue was fixed in Subversion 1.7.2:
(From http://svn.apache.org/repos/asf/subversion/tags/1.7.2/CHANGES)
* properly define WIN64 on Windows x64 builds (r1188609)
Not by a code change here in this piece of the code, but by making sure that
the pointer size is defined correctly in apr.
So that would fix this issue and maybe several others.
Bert
> -Original Message-
> From: Bert Huijben [mailto:b...@qqmail.nl]
> Sent: donderdag 7 juni 2012 11:34
> To: 'Daniel Widenfalk'; d...@subversion.apache.org;
> users@subversion.apache.org
> Subject: RE: Potential issue in
libsvn_diff:diff_
some ideas on how we can provide a limited set of the AnkhSVN
features to other MSSCCI based tools, but some of the tools we really would
loved to have support for, have yet another SCC implementation)
Bert
>
> ~ mark c
d that the exclusive locking patch in issue 4176
> helps: http://subversion.tigris.org/issues/show_bug.cgi?id=4176
This sounds like the scalability problem that was fixed by upgrading Sqlite
3.7.9 or later.
(Without that we perform a full table scan, which in this case would be 2
million times (the number of nodes) slower than deleting with the proper
index usage)
Bert
>
> --
> Philip
n syntax. What is so
difficult
> to allow -rHEAD on svn:externals?
We don't have forward history searching in Subversions filesystems. So
allowing this option requires extending the filesystem layer.
And given that usually -r follows copies, there could be multiple answers,
which makes designing this option in the filesystem hard and the result
inconclusive.
Bert
The nested status is a TortoiseSVN specific status that tells you that there
is a working copy below the parent working copy (a ‘nested’ working copy).
This is exactly how externals are implemented in Subversion, so I would
recommend leaving it at this.
Bert
From: 許阿光
a
> single file (or a set of files) in history. By configuring an authz
> policy that denies access to that file, one can svnsync to a new
> repository, which is then free of corruption (without the corrupted
> file of course).
>
> > Any reason svnsync couldn't grow a "--fail-on-access-error" option?
>
> Sure, I think that could be useful (as long as it's not the default
> (backwards compat)).
The problem here is that we don't get an access denied error. Svnsync just
notes an empty revision, which is somehow valid. (We try not to create empty
revisions, but there are quite a few repositories that have them via
different tricks or bugs).
So we should have a way to detect that this happens.
Bert
>
> --
> Johan
directory and everything
below that ignoring the case that with proper ignore handling. The --force
allows calling it on an already versioned directory.
Bert
From: Alan McGovern [mailto:a...@xamarin.com]
Sent: zaterdag 30 juni 2012 01:34
To: users@subversion.apache.org
Subject:
low). More than a few
users asked similar and related questions there over the years.
SharpSvn is a thin layer over the client api, so most questions equally
apply to direct users of the libsvn_client api.
Bert
From: Alan McGovern [mailto:a...@xamarin.com]
Sent: zaterd
vn_repository\vpl_slave Rev: 0 User: "", """
>
> Looks to me your username somewhere is changed to "", because this is
> logged as %userName% and %3. If %3 would be an empty string, it
> wouldn't get replace to "" in my opinion. If username is "" somehow,
> your if fails, of course.
Are you sure the target repository doesn't allow anonymous access?
If it allows anonymous access the client will only upgrade to authentication
when it needs to.
Bert
Every svn_wc API that changes the working copy requires its caller to
obtain a write lock. In the past that was done via the access batons
and now it requires another call.
But the most common ones are still private.
Bert Huijben (Cell phone)
From: Daniel Shahaf
Sent: 7-7-2012 1:02
To: lfdon
h it won't be if the file
is already moved, but some later operation (like obtaining the timestamp)
fails.
Bert
.
But then, I don’t know how that affects the current comment syntax.
We should really check the source before making a decision.
Bert
From: Jason Heeris [mailto:jason.hee...@gmail.com]
Sent: donderdag 12 juli 2012 11:37
To: Johan Corveleyn
Cc: Matthew Pounsett
> -Original Message-
> From: Bert Huijben [mailto:b...@qqmail.nl]
> Sent: dinsdag 10 juli 2012 16:52
> To: 'Philip Martin'; 'Johan Corveleyn'
> Cc: 'Dave Huang'; users@subversion.apache.org
> Subject: RE: "svn cleanup" fails be
ured specifically,
while DNS was invented to avoid that.
Bert
the fix will be part of Subversion 1.7.6.
(The fix is of course that we normalize this url on import)
If possible I would recommend marking the tree conflict as resolved using an
old client and then upgrading again.
Bert
e same operation. Until the operation is
completed on some subtree the directory is marked incomplete and this will
make the next update (after interruption) load missing children.
(This 'incomplete' behavior was implemented far before 1.0)
Bert
recommend going to a very
recent 3.7 version as there are relevant optimizer fixes that may speed up
several operations.
Bert
From: Ferreira, Matthew [mailto:mferre...@navisite.com]
Sent: woensdag 22 augustus 2012 14:15
To: users@subversion.apache.org
Subject: RE: E200030 error
; does not access the repository (well, maybe
> except for upgraded 1.0 working copies or something like that, Bert
> would know :)), so it doesn't need these arguments.
svn upgrade needs access to the repository for 1.0 working copies, but svn
cleanup never.
(Very early in 1.7 developmen
$ svn ci -m "comment"
Is a common way for documentation to tell that you should type exactly what
is behind the $. The '$' itself is a placeholder for your prompt which could
be something like 'C:\Windows>' on Windows or something like '~/svn-site
(ber
scenarios where Eclipse/Subclipse/Subversion retries for
you, but that is not something we can fix with a single generic solution in
Subversion itself.
In my case my mail client and VPN access were more likely to get me locked
out.
Bert
>
> Does this sound familiar?
> Thanks Wendell Nichols
to Windows Error
reporting and I would guess that it is optional as well.
Bert
From: Hawkins, John [mailto:john.hawk...@transcore.com]
Sent: vrijdag 21 september 2012 09:54
To: Hawkins, John; Mark Phippard
Cc: users@subversion.apache.org; TCORE-CM
Subject: RE: Apache won
ching to the new working copy backend.
The result in the repository will be identical to what it was before 1.7,
but status explains better what really happens. And now it can also report
'M +' when the file is scheduled to be added via its parent, but is itself
modified.
Bert
re not trivial and upgrading the project files
should just work. (Backport patch welcome of course)
When you upgrade using Visual Studio, make sure you also update the
referenced toolchain from v100 to v110 when upgrading from 2010 to 2012.
(Should be available in the right click menu on the project and solution
levels)
Bert
>
> --Phil
.
So maybe it is easier to test if svnrdump works for your specific task, before
(or next to) reporting the problem to the author of rsvndump.
Bert
From: tom.malfr...@telenet.be [mailto:tom.malfr...@telenet.be]
Sent: dinsdag 4 december 2012 13:26
To: users
on are you using? I've published,
> SRPM tools at https://github.com/nkadel/subversion-1.6.18-srpm which
> you may find useful to build a fully equipped Subveriosn 1.6.18,
> compatible with Red Hat's, but with all the latest features such as
> gnome-keyring support as much as can be activated with RHEL 5.
Nico, when the user uses svn+ssh:// the Subversion authentication handling
isn't used. I don't think your binaries add gnome keyring support to the
system default ssh?
Bert
arent directory.
Most likely caused by moving a single working copy directory.
This state (added to a parent that does not exist) is not supported by the
new working copy database introduced in 1.7. The database always requires
the root of the working copy to exist in the repository.
Bert
es, as the data to do the right
thing is just not stored in the working copy in 1.6.
Bert
From: Roman Kellner [mailto:muzu...@gmx.net]
Sent: vrijdag 11 januari 2013 09:02
To: Daniel Shahaf; users@subversion.apache.org
Subject: Re: branching WC folder fails with files mar
le
> system.
>
> Or perhaps again if you checked out or updated using a third-party svn
client
> that did not transform line endings in response to svn:eol-style native,
then
> you might later have a problem.
A lot of users have SvnKit in their Jenkins installation. Are you sure that
you aren't mixing a normal svn with some svnkit version?
Bert
tly explain this problem.
(Just like it explained a similar problem in our testsuite yesterday. Python
appears to have a similar problem in its file timestamps)
Bert
ortoiseSVN.
Bert
From: Maxwell Ballenger [mailto:maxwell.ballen...@spacex.com]
Sent: zaterdag 19 januari 2013 00:44
To: users@subversion.apache.org
Subject: Working copy corrupted by branch deletion
Hi Subversion Users,
We're experiencing some new behavior after
en it encounters a delete of a switched path it will now
place a similar hidden marker as you would get when you update a path to r0
(or commit a file delete). The next update will now bring in the missing
node.
I will nominate the fix for backporting to a future 1.7 release.
ing at this error it might be that you try to commit while the hook is
invoked as part of another commit)
Bert
From: Ramachandran Raghavendran
[mailto:ramachandran.raghavend...@flsmidth.com]
Sent: maandag 4 februari 2013 11:55
To: users@subversion.apache.org
Subject: URL based c
ns, but it
shouldn't' break the normal cases where 'svn diff *' would do one thing
completely differently if it happens to match exactly two files, where one
is versioned and one is not, or both are unversioned.
If we want something like that we should support that with a flag like
--unversioned (better name suggestions welcome)
I really like the url vs path diff changes though.
Bert
y as LDAP server with almost every
Subversion server package. (Wandisco, CollabNet, etc.)
And if you setup Apache httpd yourself you can avoid typing passwords by
setting up mod_authz_sspi.
(I think VisualSVN uses a combination of these systems)
Bert
Hi,
I would like to set the conflict presentation style to
svn_diff_conflict_display_modified_original_latest. How do I do this?
Thanks.
Regards,
Bert Wesarg
the password is stored in
there as plain text if there is no specific store available.
Since Subversion 1.6 you get a warning from svn when the password will be
stored as plain text.
Bert
1 - 100 of 401 matches
Mail list logo
