Ryan Schmidt ryandesign.com> writes:
>
> I'm forwarding your response back to the list so that hopefully
someone can help you. Remember to use Reply
> All so that the discussion stays on the list.
>
> Begin forwarded message:
>
> > From: Jon-Erik TYVAND
> > To: Ryan Schmidt
> > Subject: SV: P
I am trying to commit a change to a repository on codeplex, but I am unable to
do so:
D:\Projects\openwaves\OpenWaves.EPiServer\trunk\src>"C:\Program
Files\TortoiseSVN\bin\svn.exe" commit -m " - add OpenWaves.EPiServer6 on trunk
branch"
SendingOpenWaves.EPiServer.sln
Adding Open
Hi,
In this case I would start by checking your 'Subversion' server.
Are you using a true subversion server, or some kind of proxy over a
different system (GitHub, Codeplex, SvnProxy?)
The error you see implies that the server says that your commit created a
negative rev
Martin Wam writes:
> We are also experiencing the same issues on AIX 7.1 (having tried all
> versions from 1.8.5 to 1.8.10). A backtrace from the coredump shows:
>
> Core was generated by `svn'.
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0 0xd82f169c in apr_palloc () from
Thanks for information.
I don't have access to the server - it is codeplex server. Not sure what they
are using there. I already posted a question on codeplex forum
(https://codeplex.codeplex.com/discussions/578215) and will see what they have
to say about it.
Tomek
From: Bert Huijben [mailto:
Tomasz Grobelny writes:
> I am trying to commit a change to a repository on codeplex, but I am unable
> to do so:
>
> D:\Projects\openwaves\OpenWaves.EPiServer\trunk\src>"C:\Program
> Files\TortoiseSVN\bin\svn.exe" commit -m " - add OpenWaves.EPiServer6 on
> trunk branch"
> SendingOpen
> That's failed in the code that runs on the client after the commit has
> succeeded. It appears that the the client is acting as if the commit worked
> on the server but it
> has not got the newly committed revision.
> If you look at the server/repository did the commit succeed?
>
No it didn'
(See attached file: svn-crash-log20150121123717.log)(See attached file:
svn-crash-log20150121123717.dmp)
svn-crash-log20150121123717.log
Description: Binary data
svn-crash-log20150121123717.dmp
Description: Binary data
Tomasz Grobelny writes:
>> That's failed in the code that runs on the client after the commit
>> has succeeded. It appears that the the client is acting as if the
>> commit worked on the server but it has not got the newly committed
>> revision. If you look at the server/repository did the comm
Hi,
Your log contains a username and a password. I would recommend changing
these if these are actual credentials.
Can you provide more context on what happened?
CollabNet support should be able to process the .dmp file, as they have the
matching .pdb files.
For us h
Philip Martin writes:
> The client may have broken the working copy when it tried to apply the
> missing revision number. You may have to check out a second working
> copy, compare to the first and manually transfer the changes to the
> second working copy.
Bert pointed out that the client may
Thanks Philip,
Your solution worked fine.
It reverted to using mktemp on the HPUX platform so we changed the libapr
source as suggested which indeed fixed the issue and used the internal
mkstemp..
The fix was as below if anybody else comes access this issue on HPUX.
file_io/unix/mktem
On Wed, Jan 21, 2015 at 03:14:52PM +, Bailey, Mark wrote:
> Thanks Philip,
>
> Your solution worked fine.
>
> It reverted to using mktemp on the HPUX platform so we changed the libapr
> source as suggested which indeed fixed the issue and used the internal
> mkstemp..
>
> The fix was a
On 1/20/2015 9:32 AM, Cory Riddell wrote:
> I'm trying to use hotcopy to create a backup of my repositories on a
> network drive. When I run the hotcopy command, most of the repository
> copies, then I get an error:
>
> E:\>svnadmin hotcopy E:\MyRepo \\Diskstation\svn\MyRepo
> svnadmin: E720002: C
Dear Mr/Ms,
I meet the problem with svn as the following:
"In file
'D:\Development\SVN\Releases\TortoiseSVN-1.8.6\ext\subversion\subversion\libsvn_wc\wc_db_update_move.c'
line 1039: assertion failed (move_dst_revision == expected_move_dst_revision
|| status == svn_wc__db_status_not_present)"
Cory Riddell writes:
> On 1/20/2015 9:32 AM, Cory Riddell wrote:
>> I'm trying to use hotcopy to create a backup of my repositories on a
>> network drive. When I run the hotcopy command, most of the repository
>> copies, then I get an error:
>>
>> E:\>svnadmin hotcopy E:\MyRepo \\Diskstation\svn\
I am afraid that this may no longer be possible as I took a workaround and
committed my changes using TFS interface to codeplex repo.
I can roughly describe what the commit involved:
1. I copied one directory from openwaves\branches\0.1\src\OpenWaves.EPiServer
to openwaves\OpenWaves.EPiServer\tru
Philip Martin writes:
>> In the line "SVN_ERR(svn_io_remove_file2(shm_name, TRUE, pool));", the
>> TRUE parameter is supposed to suppress file not found errors yet that's
>> the error I'm getting, isn't it?
>
> Yes, it should. It's failing because it's getting error 720002 and that
> is not an e
On 1/21/2015 11:44 AM, Cory Riddell wrote:
> On 1/21/2015 10:41 AM, Philip Martin wrote:
>> Cory Riddell writes:
>>
>>> On 1/20/2015 9:32 AM, Cory Riddell wrote:
I'm trying to use hotcopy to create a backup of my repositories on a
network drive. When I run the hotcopy command, most of th
On 1/21/2015 10:41 AM, Philip Martin wrote:
> Cory Riddell writes:
>
>> On 1/20/2015 9:32 AM, Cory Riddell wrote:
>>> I'm trying to use hotcopy to create a backup of my repositories on a
>>> network drive. When I run the hotcopy command, most of the repository
>>> copies, then I get an error:
>>>
Hi Andreas, thanks for your reply.
Your details (replicating hooks, httpd config, etc) are too vague for
someone like me who knows very very little SVN server internals. Would it
be possible to have the procedure in written form?
OTOH, another mail said that if replication for VisualSVN does not
On 17 January 2015 at 08:10, Pavel Lyalyakin
wrote:
> Hello,
>
> > On 17 January 2015 at 00:47, STF SVN wrote:
> >>
> >> I know this mailing-list has nothing to do with VisualSVN server, but I
> >> really need some help.
> >>
> >> I need to set up SVN replication on the fly, aka write-through pr
22 matches
Mail list logo
