Martin Rupp wrote on Sun, 03 Jan 2021 03:27 +00:00:
> What is the "filesystem '75510a91-dada-4f23-b575-03fe34008164'"?
>
> It seems it is the id for the svnserver (svnserve).
>
It's the repository UUID. The error message gives the repository UUID
becaus
gt;
> Martin Rupp
>
>
> Am 03.01.2021 um 09:53 schrieb Daniel Sahlberg:
>
> Den sön 3 jan. 2021 kl 06:37 skrev Martin Rupp :
>
>> Hi,
>>
>> If a file is locked I get an error message like:
>>
>> Lock failed: C:\test\svn\TestSvn\Test-o1.fodt
>&
Den sön 3 jan. 2021 kl 16:43 skrev Martin Rupp :
> Dear Mr. Sahlberg,
>
> thank you for your answer.
>
> I have played with the client hook pre-lock script of Tortoise SVN. The
> idea is very good.
> The first argument is a temporary file. It should contain the paths to the
> files which should be
't want to add
also each working copy to the username
Best regards
Martin Rupp
Am 03.01.2021 um 09:53 schrieb Daniel Sahlberg:
Den sön 3 jan. 2021 kl 06:37 skrev Martin Rupp <mailto:martin.r...@nefkom.net>>:
Hi,
If a file is locked I get an error message like:
Lock f
Den sön 3 jan. 2021 kl 06:37 skrev Martin Rupp :
> Hi,
>
> If a file is locked I get an error message like:
>
> Lock failed: C:\test\svn\TestSvn\Test-o1.fodt
> Error: Path '/Martin/Test-o1.fodt' is already locked by user 'martin' in
> filesystem
>
Hi,
If a file is locked I get an error message like:
Lock failed: C:\test\svn\TestSvn\Test-o1.fodt
Error: Path '/Martin/Test-o1.fodt' is already locked by user 'martin' in
filesystem
Error: '75510a91-dada-4f23-b575-03fe34008164'
(TortoiseSVN 1.14.0, Build 28885
On Dec 13, 2017, at 09:09, Sal Palumbo wrote:
> Error message when attempting to update subversion on local machine.
> Any help would be much appreciated,
> Thanks,
> Sal
>
> ---
> Subversion Exception!
> ---
> Subve
Error message when attempting to update subversion on local machine.
Any help would be much appreciated,
Thanks,
Sal
---
Subversion Exception!
---
Subversion encountered a serious problem.
Please take the time to report this on the Subversion
; > The issue is when create copy/branch/tag from a local working copy
> > path using "svn copy", if the parent path of the copying target
> > does not exist, the "svn copy" command fails with a misleading error
> > message saying that the copy sourc
ent path of the copying target
> > does not exist, the "svn copy" command fails with a misleading error
> > message saying that the copy source (working copy directory) "is out
> > of date" while that is not the case.
> >
> > The reproduce case
On Wed, Aug 3, 2016 at 7:23 PM, Doug Robinson
wrote:
>
> Folks:
>
> The issue is when create copy/branch/tag from a local working copy
> path using "svn copy", if the parent path of the copying target
> does not exist, the "svn copy" command fails with a misl
Folks:
The issue is when create copy/branch/tag from a local working copy
path using "svn copy", if the parent path of the copying target
does not exist, the "svn copy" command fails with a misleading error
message saying that the copy source (working copy directory) "i
ratch_pool),
svn_dirent_local_style(def_dir_abspath,
scratch_pool),
svn_dirent_local_style(wcroot_abspath,
]]]
I don't have time to check if it passes tests, though. I'd be glad if
someone else could pick it up...
Cheers,
Daniel
(Finding the cod
nal
involved so that troubleshooting is easier?
Thanks
You might wanna upgrade your SVN version to the latest 1.8 build (which
is 1.8.16 at the time of writing this).
There are multiple client fixes impacting the handling of externals. For
instance 1.8.13:
"better error message if an exte
On 11 May 2016 2:40 p.m., "Cosmere Infahm" wrote:
>
> Hello,
>
> I am using svn version 1.8.9 on Centos and I get the following warnings
>
> svn: warning: W155022: Cannot insert a file external defined on
'/home/cosm/svn/parser/packages' into the working copy
'/home/cosm/svn/parser/packages/src'.
Hello,
I am using svn version 1.8.9 on Centos and I get the following warnings
svn: warning: W155022: Cannot insert a file external defined on
'/home/cosm/svn/parser/packages' into the working copy
'/home/cosm/svn/parser/packages/src'.
svn: warning: W155022: Cannot insert a file external defined
ome data already, created some empty
> folders it couldn't know about without access to the repo and such.
> Therefore there must have been at least some communication already
> until the error occurred and that's why I wrongly ruled out the
> firewall early.
>
> So, do
e communication already
until the error occurred and that's why I wrongly ruled out the
firewall early.
So, do you see any chance to improve this generic error message and
mention something around certificate verification or that resolving
some domain failed or such? This would have made fi
Hi Paul,
I was doing a 'clean up' with Tortoise when this error message came up:
---
Subversion Exception!
---
Subversion encountered a serious problem.
Please take the time to report this on the Subversion mailing list
with as much info
I was doing a 'clean up' with Tortoise when this error message came up:
---
Subversion Exception!
---
Subversion encountered a serious problem.
Please take the time to report this on the Subversion mailing list
with as much information a
Benoit de Biolley writes:
> Do you will create an "improvement" in the issue tracker ?
It is now fixed on trunk.
--
Philip Martin | Subversion Committer
WANdisco // *Non-Stop Data*
> From: philip.mar...@wandisco.com
> To: lepirlo...@hotmail.com
> CC: users@subversion.apache.org
> Subject: Re: Possible bug in error message E160020
> Date: Mon, 15 Dec 2014 11:10:59 +
>
> Benoit de Biolley writes:
>
> > this bugs is on the eror message tha
.commit --revision 6237
> http://svn.xxx.be/xxx-svn/pow/trunk/
> http://svn.xxx.be/xxx-svn/pow/tags/R4.10.1t";
>
> error message is :
> svn: E160020: Path 'trunk' already exists
>
> error message should be :
> svn: E160020: Path 'R4.10.1t' already exi
unk/
http://svn.xxx.be/xxx-svn/pow/tags/R4.10.1t";
error message is :
svn: E160020: Path 'trunk' already exists
error message should be :
svn: E160020: Path 'R4.10.1t' already exists
Hi,
> I don't suppose this would be possible without hacking the
> code, right?
> Reason I'm asking is simplicity and clearness in the message.
> eg. is when an attempt to lock fails for file is already
> locked by other user
> why bother users with the path to file on a remote resource?
> they
On Tue, Aug 12, 2014 at 09:44:03AM +0100, lejeczek wrote:
> hi users
> I don't suppose this would be possible without hacking the code, right?
> Reason I'm asking is simplicity and clearness in the message.
> eg. is when an attempt to lock fails for file is already locked by other
> user
> why both
hi users
I don't suppose this would be possible without hacking the
code, right?
Reason I'm asking is simplicity and clearness in the message.
eg. is when an attempt to lock fails for file is already
locked by other user
why bother users with the path to file on a remote resource?
they usually
>
>
> --parents is implemented by the client. The client first builds up a
> transaction on the server and then tells the server to attempt to commit
> the transaction. Without --parents the copy fails while building the
> transaction so no attempt is made to commit the transaction. With
> --par
Dan Ellis writes:
> I don't quite follow what the different checks would be as in this case the
> only difference is --parents vs no --parents. Both I imagine do a path
> existence check and in both cases the path doesn't exist. In the end, it
> really doesn't matter - its a general curiosity o
On May 22, 2014, at 10:16, Dan Ellis wrote:
>> The pre-commit hook script is only called if Subversion's internal checks
>> already passed; if the internal checks fail, there's no reason to call the
>> pre-commit hook script since the commit will fail regardless of the hook
>> script's outcome.
h cases the path doesn't exist. In the end, it
really doesn't matter - its a general curiosity on my part.
I agree the error message could be improved, as I said above. I can
> reproduce it with a simple script:
>
I agree, it lead me astray for a little bit.
I don't under
it). Why didn't case 1 trigger the pre-commit check? Granted, the script in
> question may be out of scope of this list.
The pre-commit hook script is only called if Subversion's internal checks
already passed; if the internal checks fail, there's no reason to call the
pre-comm
On Wed, May 21, 2014 at 3:22 AM, Ryan Schmidt <
subversion-2...@ryandesign.com> wrote:
>
> On May 20, 2014, at 17:02, Dan Ellis wrote:
>
> > I'm attempting to copy a file from a working copy to the server, but
> using an incorrect case for one of the folders in the path. The paths all
> exist and
On May 20, 2014, at 17:02, Dan Ellis wrote:
> I'm wondering if I'm getting an incorrect error message...
>
> I'm attempting to copy a file from a working copy to the server, but using an
> incorrect case for one of the folders in the path. The paths all exist a
Hi,
I'm wondering if I'm getting an incorrect error message...
I'm attempting to copy a file from a working copy to the server, but using
an incorrect case for one of the folders in the path. The paths all exist
and everything works fine using correct case. In the example belo
On Tue, Jun 18, 2013 at 10:57:28AM -0500, Les Mikesell wrote:
> Would it have made a difference in the subversion processing if the
> empty trunk had been copied to create the branch before the initial
> import? That is, would having a common ancestor as the parent
> directory have made the 'adds'
On Tue, Jun 18, 2013 at 9:47 AM, Stefan Sperling wrote:
> On Tue, Jun 18, 2013 at 09:33:25AM -0500, Les Mikesell wrote:
>> On Tue, Jun 18, 2013 at 4:31 AM, Stefan Sperling wrote:
>>
>> > In your case, the latter isn't true. You have a new directory /trunk,
>> > which is empty, and you are trying
On Tue, Jun 18, 2013 at 09:33:25AM -0500, Les Mikesell wrote:
> On Tue, Jun 18, 2013 at 4:31 AM, Stefan Sperling wrote:
>
> > In your case, the latter isn't true. You have a new directory /trunk,
> > which is empty, and you are trying to merge changes into it.
>
> Is there any advantage in mergi
On Tue, Jun 18, 2013 at 4:31 AM, Stefan Sperling wrote:
> In your case, the latter isn't true. You have a new directory /trunk,
> which is empty, and you are trying to merge changes into it.
Is there any advantage in merging changes to an empty path as compared
to just copying to it?
--
Les
On Mon, Jun 17, 2013 at 04:01:43PM -0500, C M wrote:
> Well, for what its worth, I was able to complete the "merge" following
> steps 3 -6 in this article.
>
> http://kirenpillay.blogspot.com/2012/07/svn-merge-tree-conflict-resolution.html
>
> I don't understand why SVN behaved the way it did and
Well, for what its worth, I was able to complete the "merge" following
steps 3 -6 in this article.
http://kirenpillay.blogspot.com/2012/07/svn-merge-tree-conflict-resolution.html
I don't understand why SVN behaved the way it did and prevented the branch
to trunk merge as expected..
On Mon, J
On Mon, Jun 17, 2013 at 12:59 PM, C M wrote:
> We are on SVN 1.7.6.
>
> Trunk is empty because this is/was a new development effort. The code was
> directly imported into the developer's branch.
>
> I ran these two commans in the working copy and get the messages you
> mentioned. What does that me
incoming edit upon merge
Summary of conflicts:
Tree conflicts: 8
On Mon, Jun 17, 2013 at 12:40 PM, Andrew Reedick wrote:
>
>
> > From: C M [mailto:cmanalys...@gmail.com]
> > Sent: Monday, June 17, 2013 12:39 PM
> > To: C. Michael Pilato
> > Cc: Subversion
> > Su
> From: C M [mailto:cmanalys...@gmail.com]
> Sent: Monday, June 17, 2013 12:39 PM
> To: C. Michael Pilato
> Cc: Subversion
> Subject: Re: Ancestrally Related Error Message
>
> I think my earlier mistake might have been that I was using the --reintegrate
> option.
&
Running without the dry-run option doesn't do anything different (it still
reports the conflicts). Yes, the diff shows the content I am expecting (at
least for the text files).
I ran "svn diff -r1190:1245 --summarize https://path_to_branch/SCR_BR/"; and
see output like:
M path_to_file
M path_to_f
On 06/17/2013 12:39 PM, C M wrote:
> I think my earlier mistake might have been that I was using the
> --reintegrate option.
> Without it, I make some progress, but still not quite what I am expecting.
>
> Again, given that trunk is empty, why the "C" (tree conflicts)? I would
> expect all of then
13 12:39 PM
To: C. Michael Pilato
Cc: Subversion
Subject: Re: Ancestrally Related Error Message
I think my earlier mistake might have been that I was using the --reintegrate
option.
Without it, I make some progress, but still not quite what I am expecting.
Again, given that trunk is empty, why t
it knows there isn't. Hence
> the
> message. The error was introduced to prevent a common mistake folks make
> when they misalign their merge sources and targets:
>
>$ svn merge ^/trunk branches
>^C^C^Cdangit i meant to type "branches/my-branch"^C^Cag
Rather, it knows there isn't. Hence the
message. The error was introduced to prevent a common mistake folks make
when they misalign their merge sources and targets:
$ svn merge ^/trunk branches
^C^C^Cdangit i meant to type "branches/my-branch"^C^Cagh!
> Two, how
lly related..." message.I also tried the
> "ignore ancestry" option via the GUI.
> One, I don't understand why SVN thinks there is even an ancestral relationship
> betweeen the two locations?
> Two, how can I do to get around this error message?
>
>From your m
the
"ignore ancestry" option via the GUI.
One, I don't understand why SVN thinks there is even an ancestral
relationship betweeen the two locations?
Two, how can I do to get around this error message?
Amad
Daniel Widenfalk writes:
> One of my colleagues got a hard-to-decipher error message after
> trying to do a merge (trunk -> branch):
>
> svn: E27: Can't add '{some-path}\svntest\C\B' with URL
> '{repo-path}/svn-test/A/B', but with the data fr
Hi,
One of my colleagues got a hard-to-decipher error message after
trying to do a merge (trunk -> branch):
svn: E27: Can't add '{some-path}\svntest\C\B' with URL
'{repo-path}/svn-test/A/B', but with the data from
'{repo-path}/tools/trunk/makecd'
svn:
teArray has the value
"C:/Users/Thuan/Desktop/Test_Project/NewProject/NewProject.mixer and in the
err pointer returned, I am getting the error message "Can't open
'7D.folder)Wo\svn-2A518358': Invalid argument" which doesnt make sense to
me. Without stepping into the
2011 at 5:13 PM
> Subject: svn miss to checkout one or more subdirectories and no error
> message
> To: users@subversion.apache.org
>
>
> hi folks,
>
> Recently, we encountered a problem when checking out directories
> frequently. But I am not sure whether is an issue or
Any progress on this problem?
-- Forwarded message --
From: qifa zhao
Date: Sat, Dec 31, 2011 at 5:13 PM
Subject: svn miss to checkout one or more subdirectories and no error
message
To: users@subversion.apache.org
hi folks,
Recently, we encountered a problem when checking out
azing is that the 'svn co' operation returned 0 and no
error message prompted, like that the subdirectories missing did not
exist.
I write a script to reproduce this problem, it happened about one or
two times in 1000 times.
*OS information:*
[work@cm-perf03 test2]$ lsb_release -a
LSB V
...and I don't remember anymore now.
Will be for next time, then...
Christophe Doumenc
-Original Message-
From: Ulrich Eckhardt [mailto:ulrich.eckha...@dominolaser.com]
Sent: Tuesday, November 15, 2011 9:10 AM
To: users@subversion.apache.org
Cc: Christophe Doumenc
Subject: Re:
Am 15.11.2011 08:49, schrieb Christophe Doumenc:
Please take the time to report this on the Subversion mailing list
with as much information as possible about what you were trying to
do.
Please consider this part of the message, you don't provide any
information about what you did, making your
archives for the error message
to avoid reporting the same problem repeatedly.
You can find the mailing list archives at
http://subversion.apache.org/mailing-lists.html
Subversion reported the following
(you can copy the content of this dialog
to the clipboard using Ctrl-C):
In file
&#
On Fri, Oct 21, 2011 at 01:05:19PM +0100, Stewart MacKenzie wrote:
> ---
> Subversion Exception!
> ---
>
>
> In file
>
> 'D:\Development\SVN\Releases\TortoiseSVN-1.7.0\ext\subversion\subversion\libsvn_wc\workqueue.c'
> line 672: assertion failed
---
Subversion Exception!
---
In file
'D:\Development\SVN\Releases\TortoiseSVN-1.7.0\ext\subversion\subversion\libsvn_wc\workqueue.c'
line 672: assertion failed (checksum != NULL)
---
OK
---
There
On Mon, Aug 15, 2011 at 02:02:31PM +, Budlong, Sean (Contractor) wrote:
> Stefan,
>
> Thank you very much for your suggestion. Here are the results for svn info.
Hi,
please make sure your replies reach the users@ list.
I am re-adding it to Cc.
Please copy-paste svn output into email instead
ld not open requested SVN filesystem
>
> Other dev servers continue to work with the Subversion server normally.
>
> Is there some way I can reset the working directories on this one dev server
> so that they can communicate with the Subversion server again? I've Googled
> t
there some way I can reset the working directories on this one dev server so
that they can communicate with the Subversion server again? I've Googled the
error message and read many of the hits I got, but none of them are relevant to
this case.
The dev server is running Windows Server 20
Daniel Shahaf wrote on Tue, Aug 02, 2011 at 13:25:18 +0300:
> Though, there is a standing backport for svn_fs_verify() which would
> break that... I'll follow up on dev@.
Actually, a quick test tells me that it's possible to read an SQLite
database that lives on a read-only mount.
Naturally, tha
Stefan Sperling wrote on Tue, Aug 02, 2011 at 10:22:23 +0200:
> On Tue, Aug 02, 2011 at 10:09:06AM +0200, Markus Schaber wrote:
> > > stsp: (re: users@) read only operations on a fsfs repository
> > don't
> > > obtain a lock (and don't need write access). Only commit and revprop
> > > changes shou
On Tue, Aug 02, 2011 at 10:09:06AM +0200, Markus Schaber wrote:
> > stsp: (re: users@) read only operations on a fsfs repository
> don't
> > obtain a lock (and don't need write access). Only commit and revprop
> > changes should need write access. (I don't know what is required for
> bdb).
> > We
Hi,
Von: Stefan Sperling [mailto:s...@elego.de]
> > It is written in SVN book that repository that uses FSFS should work
> > on read-only media.
> > Is it something that was broken recently?
> >
> > - see "Usable from a read-only mount" row in the table in the middle
> > of
> >
> > http://svnbook
On Monday 01 August 2011, Les Mikesell wrote:
> On 8/1/11 8:30 AM, Ulrich Eckhardt wrote:
>> Are you really serious?
>
> No,
Thanks, that confirms it.
Sorry, but this discussion is pointless.
Uli
**
Domino Laser
On Mon, Aug 01, 2011 at 10:16:53PM +0400, Konstantin Kolinko wrote:
> 2011/8/1 Stefan Sperling :
> > On Mon, Aug 01, 2011 at 04:38:46PM +0200, Markus Schaber wrote:
> >>
> >> Hi,
> >>
> >> Von: Stefan Sperling [mailto:s...@elego.de]
> >> > On Mon, Aug 01, 2011 at 04:12:41PM +0200, Markus Schaber wr
2011/8/1 Stefan Sperling :
> On Mon, Aug 01, 2011 at 04:38:46PM +0200, Markus Schaber wrote:
>>
>> Hi,
>>
>> Von: Stefan Sperling [mailto:s...@elego.de]
>> > On Mon, Aug 01, 2011 at 04:12:41PM +0200, Markus Schaber wrote:
>> > > Can subversion cope with repositories and working-copies on
>> read-on
On Mon, Aug 01, 2011 at 04:38:46PM +0200, Markus Schaber wrote:
>
> Hi,
>
> Von: Stefan Sperling [mailto:s...@elego.de]
> > On Mon, Aug 01, 2011 at 04:12:41PM +0200, Markus Schaber wrote:
> > > Can subversion cope with repositories and working-copies on
> read-only
> > media?
> > >
> > > Maybe so
Hi,
Von: Stefan Sperling [mailto:s...@elego.de]
> On Mon, Aug 01, 2011 at 04:12:41PM +0200, Markus Schaber wrote:
> > Can subversion cope with repositories and working-copies on
read-only
> media?
> >
> > Maybe some Live-Demo CD bringing an example SVN repository?
>
> No.
So subversion needs wr
On Mon, Aug 01, 2011 at 04:12:41PM +0200, Markus Schaber wrote:
> Can subversion cope with repositories and working-copies on read-only media?
>
> Maybe some Live-Demo CD bringing an example SVN repository?
No.
If you want to make a live CD, put the repository and working copies
on a ramdisk or
Hi,
Von: Ulrich Eckhardt [mailto:ulrich.eckha...@dominolaser.com]
> Consider something is inherently read-only (e.g. a
> CDROM) or the server just failed to fulfill my request because it ran out
> of diskspace.
Just out of curiosity:
Can subversion cope with repositories and working-copies on
as reasonable from a
security perspective, which could be argued still. From a user
perspective though, they definitely suck, because they don't help you
solve the problem.
This wasn't an error message, it was an 'access denied' message and it was
displayed because of the way the
early MS Windows systems? You are advocating them as reasonable from a
>> security perspective, which could be argued still. From a user
>> perspective though, they definitely suck, because they don't help you
>> solve the problem.
>
> This wasn't an error message, it was an
pective though, they
definitely suck, because they don't help you solve the problem.
This wasn't an error message, it was an 'access denied' message and it was
displayed because of the way the administrator had configured the system. If
the admin needs help understanding that he
On Saturday 30 July 2011, Les Mikesell wrote:
> From a security perspective it is a bad idea to tell a network client that
> is doing something you have explicitly denied any of the details of how
> the system is configured to prevent it. Working correctly is usually a
> yes or no question and thi
so ANY client can read it and the client will understant it.
> As you can read on this website:
> http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html you can see in the
> section 10.4.4 that the error 403 is the error message when an authorization
> is necessary.
And that's all
ad on this website: h
ttp://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html<http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html>
you
can see in the section 10.4.4 that the error 403 is the error message when
an authorization is necessary.
So, as you can see, there is an organization calle
On 7/31/11 3:24 PM, Jeremy Pereira wrote:
Telling somebody that they only have read access to a repository is not giving them a hint about
how to work around it. "403 forbidden" is not telling somebody that they only have read
access to a repository (or part of a repository). It's telling t
On 31 Jul 2011, at 17:46, Rafael Heise wrote:
> In my opinion, as a network administrator, I don't want to show to my end
> users why the user shouldn't commit anything in the repository.
In my opinion as a Subversion user, that sucks. I think I'll switch to
Mercurial. Oh, no wait, the Subve
e
>>> who shouldn't know internal details anyway.
>>
>> Seriously? You think an HTTP response code (which *is* an internal detail)
>> is an acceptable error message. You think it makes sense? Why is 403
>> forbidden? Oh, right, that's just a code. Ok what is fo
>>> someone who shouldn't know internal details anyway.
> >>
> >> Seriously? You think an HTTP response code (which *is* an internal
> >> detail) is an acceptable error message. You think it makes sense? Why
> is
> >> 403 forbidden? Oh, right,
gt;> someone who shouldn't know internal details anyway.
>>
>> Seriously? You think an HTTP response code (which *is* an internal
>> detail) is an acceptable error message. You think it makes sense? Why is
>> 403 forbidden? Oh, right, that's just a code. Ok what is f
rnal detail) is
an acceptable error message. You think it makes sense? Why is 403 forbidden?
Oh, right, that's just a code. Ok what is forbidden? Is it me? the
repository? writing to the repository? writing to a particular file? Why is
it forbidden? Is it because it is Tuesday? WHY???
On 30 Jul 2011, at 18:17, Les Mikesell wrote:
>
> '403 forbidden' makes reasonable sense for a client-side message to someone
> who shouldn't know internal details anyway.
Seriously? You think an HTTP response code (which *is* an internal detail) is
an acceptable e
On 7/30/11 9:15 AM, Andy Canfield wrote:
I just spent all day working on a bug. I could create a repository, and could do
"svn checkout ..." but when I did "svn commit" I got this error message:
svn: Commit failed (details follow):
svn: Server sent unexpected return valu
On 07/30/2011 09:31 PM, Stefan Sperling wrote:
On Sat, Jul 30, 2011 at 09:15:18PM +0700, Andy Canfield wrote:
I just spent all day working on a bug. I could create a repository,
and could do "svn checkout ..." but when I did "svn commit" I got
this error message:
On Sat, Jul 30, 2011 at 09:15:18PM +0700, Andy Canfield wrote:
> I just spent all day working on a bug. I could create a repository,
> and could do "svn checkout ..." but when I did "svn commit" I got
> this error message:
> svn: Commit failed (details
On Sat, 30 Jul 2011, Andy Canfield wrote:
> I just spent all day working on a bug. I could create a repository, and could
> do "svn checkout ..." but when I did "svn commit" I got this error message:
> svn: Commit failed (details follow):
> svn: Server s
I just spent all day working on a bug. I could create a repository, and
could do "svn checkout ..." but when I did "svn commit" I got this error
message:
svn: Commit failed (details follow):
svn: Server sent unexpected return value (403 Forbidden)
in re
> i have problem in seting up variable or installing the
> subvision can u help
> with the steps i have attache the arror massage
1) Never send attachments to this list (or any other lists which does not
explicetedly allow this in their charter).
2) You sent an image inside a proprietary format.
HI THERE
i have problem in seting up variable or installing the subvision can u help
with the steps i have attache the arror massage
South Africas premier free email service - www.webmail.co.za
For super low premiums, click here http:
I am using the SVN plugin in MyEclipse 6.6. The details of my SVN version are
as below
SVNKit (Pure Java) SVNkit v1.2.3.5521
javaHL(JNI) 1.5.7(r36142)
I got an error message while trying to import "Existing Projects into
Workspace".
The error is as below. I am not sure whether thi
Hello!
I have a problem with using the relative syntax for svn:externals.
I get error message "...is not the same repository as..."
Note that I have 3 externals (all referencing the same file)
and only the first of them (with absolute URL) works.
It seems that svn skips the port n
ate my local copy. In the end I found out that the ssh key
>> verification failed for the server. I would vote for a more specific
>> error message that clearly states what is going wrong. Is this worth a
>> bug report?
>
> Which version of Subversion are you using?
> The e
ound out that the ssh key
> verification failed for the server. I would vote for a more specific
> error message that clearly states what is going wrong. Is this worth a
> bug report?
Which version of Subversion are you using?
The error message has already been improved in 1.6.11, rele
1 - 100 of 102 matches
Mail list logo
